On Tue, Oct 10, 2017 at 11:33:02AM +0100, Suzuki K Poulose wrote:
> This patch documents the devicetree bindings for ARM DSU PMU.
>
> Cc: Mark Rutland <mark.rutland@xxxxxxx>
> Cc: Will Deacon <will.deacon@xxxxxxx>
> Cc: devicetree@xxxxxxxxxxxxxxx
> Cc: frowand.list@xxxxxxxxx
> Acked-by: Rob Herring <robh@xxxxxxxxxx>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@xxxxxxx>
Acked-by: Mark Rutland <mark.rutland@xxxxxxx>
Thanks,
Mark.
> ---
> Changes since V3:
> - Fixed node name in the example, suggested by Rob
> ---
> .../devicetree/bindings/arm/arm-dsu-pmu.txt | 27 ++++++++++++++++++++++
> 1 file changed, 27 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/arm-dsu-pmu.txt
>
> diff --git a/Documentation/devicetree/bindings/arm/arm-dsu-pmu.txt b/Documentation/devicetree/bindings/arm/arm-dsu-pmu.txt
> new file mode 100644
> index 000000000000..6efabba530f1
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/arm-dsu-pmu.txt
> @@ -0,0 +1,27 @@
> +* ARM DynamIQ Shared Unit (DSU) Performance Monitor Unit (PMU)
> +
> +ARM DyanmIQ Shared Unit (DSU) integrates one or more CPU cores
> +with a shared L3 memory system, control logic and external interfaces to
> +form a multicore cluster. The PMU enables to gather various statistics on
> +the operations of the DSU. The PMU provides independent 32bit counters that
> +can count any of the supported events, along with a 64bit cycle counter.
> +The PMU is accessed via CPU system registers and has no MMIO component.
> +
> +** DSU PMU required properties:
> +
> +- compatible : should be one of :
> +
> + "arm,dsu-pmu"
> +
> +- interrupts : Exactly 1 SPI must be listed.
> +
> +- cpus : List of phandles for the CPUs connected to this DSU instance.
> +
> +
> +** Example:
> +
> +dsu-pmu-0 {
> + compatible = "arm,dsu-pmu";
> + interrupts = <GIC_SPI 02 IRQ_TYPE_LEVEL_HIGH>;
> + cpus = <&cpu_0>, <&cpu_1>;
> +};
> --
> 2.13.6
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
