# SPDX-License-Identifier: GPL-2.0 %YAML 1.2 --- $id: http://devicetree.org/schemas/arm/pmu.yaml# $schema: http://devicetree.org/meta-schemas/core.yaml# title: ARM Performance Monitor Units maintainers: - Mark Rutland - Will Deacon description: |+ ARM cores often have a PMU for counting cpu and cache events like cache misses and hits. The interface to the PMU is part of the ARM ARM. The ARM PMU representation in the device tree should be done as under:- properties: compatible: items: - enum: - apm,potenza-pmu - arm,armv8-pmuv3 - arm,cortex-a73-pmu - arm,cortex-a72-pmu - arm,cortex-a57-pmu - arm,cortex-a53-pmu - arm,cortex-a35-pmu - arm,cortex-a17-pmu - arm,cortex-a15-pmu - arm,cortex-a12-pmu - arm,cortex-a9-pmu - arm,cortex-a8-pmu - arm,cortex-a7-pmu - arm,cortex-a5-pmu - arm,arm11mpcore-pmu - arm,arm1176-pmu - arm,arm1136-pmu - brcm,vulcan-pmu - cavium,thunder-pmu - qcom,scorpion-pmu - qcom,scorpion-mp-pmu - qcom,krait-pmu interrupts: # Don't know how many CPUs, so no constraints to specify description: 1 per-cpu interrupt (PPI) or 1 interrupt per core. interrupt-affinity: $ref: /schemas/types.yaml#/definitions/phandle-array description: When using SPIs, specifies a list of phandles to CPU nodes corresponding directly to the affinity of the SPIs listed in the interrupts property. When using a PPI, specifies a list of phandles to CPU nodes corresponding to the set of CPUs which have a PMU of this type signalling the PPI listed in the interrupts property, unless this is already specified by the PPI interrupt specifier itself (in which case the interrupt-affinity property shouldn't be present). This property should be present when there is more than a single SPI. qcom,no-pc-write: type: boolean description: Indicates that this PMU doesn't support the 0xc and 0xd events. secure-reg-access: type: boolean description: Indicates that the ARMv7 Secure Debug Enable Register (SDER) is accessible. This will cause the driver to do any setup required that is only possible in ARMv7 secure state. If not present the ARMv7 SDER will not be touched, which means the PMU may fail to operate unless external code (bootloader or security monitor) has performed the appropriate initialisation. Note that this property is not valid for non-ARMv7 CPUs or ARMv7 CPUs booting Linux in Non-secure state. required: - compatible ...