1 # SPDX-License-Identifier: GPL-2.0
4 $id: http://devicetree.org/schemas/arm/pmu.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ARM Performance Monitor Units
10 - Mark Rutland <mark.rutland@arm.com>
11 - Will Deacon <will.deacon@arm.com>
14 ARM cores often have a PMU for counting cpu and cache events like cache misses
15 and hits. The interface to the PMU is part of the ARM ARM. The ARM PMU
16 representation in the device tree should be done as under:-
42 - qcom,scorpion-mp-pmu
46 # Don't know how many CPUs, so no constraints to specify
47 description: 1 per-cpu interrupt (PPI) or 1 interrupt per core.
50 $ref: /schemas/types.yaml#/definitions/phandle-array
52 When using SPIs, specifies a list of phandles to CPU
53 nodes corresponding directly to the affinity of
54 the SPIs listed in the interrupts property.
56 When using a PPI, specifies a list of phandles to CPU
57 nodes corresponding to the set of CPUs which have
58 a PMU of this type signalling the PPI listed in the
59 interrupts property, unless this is already specified
60 by the PPI interrupt specifier itself (in which case
61 the interrupt-affinity property shouldn't be present).
63 This property should be present when there is more than
69 Indicates that this PMU doesn't support the 0xc and 0xd events.
74 Indicates that the ARMv7 Secure Debug Enable Register
75 (SDER) is accessible. This will cause the driver to do
76 any setup required that is only possible in ARMv7 secure
77 state. If not present the ARMv7 SDER will not be touched,
78 which means the PMU may fail to operate unless external
79 code (bootloader or security monitor) has performed the
80 appropriate initialisation. Note that this property is
81 not valid for non-ARMv7 CPUs or ARMv7 CPUs booting Linux