1c66ec88fSEmmanuel Vadot# SPDX-License-Identifier: GPL-2.0 2c66ec88fSEmmanuel Vadot%YAML 1.2 3c66ec88fSEmmanuel Vadot--- 4c66ec88fSEmmanuel Vadot$id: http://devicetree.org/schemas/arm/pmu.yaml# 5c66ec88fSEmmanuel Vadot$schema: http://devicetree.org/meta-schemas/core.yaml# 6c66ec88fSEmmanuel Vadot 7c66ec88fSEmmanuel Vadottitle: ARM Performance Monitor Units 8c66ec88fSEmmanuel Vadot 9c66ec88fSEmmanuel Vadotmaintainers: 10c66ec88fSEmmanuel Vadot - Mark Rutland <mark.rutland@arm.com> 11c66ec88fSEmmanuel Vadot - Will Deacon <will.deacon@arm.com> 12c66ec88fSEmmanuel Vadot 13c66ec88fSEmmanuel Vadotdescription: |+ 14c66ec88fSEmmanuel Vadot ARM cores often have a PMU for counting cpu and cache events like cache misses 15c66ec88fSEmmanuel Vadot and hits. The interface to the PMU is part of the ARM ARM. The ARM PMU 16c66ec88fSEmmanuel Vadot representation in the device tree should be done as under:- 17c66ec88fSEmmanuel Vadot 18c66ec88fSEmmanuel Vadotproperties: 19c66ec88fSEmmanuel Vadot compatible: 20c66ec88fSEmmanuel Vadot items: 21c66ec88fSEmmanuel Vadot - enum: 22c66ec88fSEmmanuel Vadot - apm,potenza-pmu 23c66ec88fSEmmanuel Vadot - arm,armv8-pmuv3 # Only for s/w models 24c66ec88fSEmmanuel Vadot - arm,arm1136-pmu 25c66ec88fSEmmanuel Vadot - arm,arm1176-pmu 26c66ec88fSEmmanuel Vadot - arm,arm11mpcore-pmu 27c66ec88fSEmmanuel Vadot - arm,cortex-a5-pmu 28c66ec88fSEmmanuel Vadot - arm,cortex-a7-pmu 29c66ec88fSEmmanuel Vadot - arm,cortex-a8-pmu 30c66ec88fSEmmanuel Vadot - arm,cortex-a9-pmu 31c66ec88fSEmmanuel Vadot - arm,cortex-a12-pmu 32c66ec88fSEmmanuel Vadot - arm,cortex-a15-pmu 33c66ec88fSEmmanuel Vadot - arm,cortex-a17-pmu 34c66ec88fSEmmanuel Vadot - arm,cortex-a32-pmu 35c66ec88fSEmmanuel Vadot - arm,cortex-a34-pmu 36c66ec88fSEmmanuel Vadot - arm,cortex-a35-pmu 37c66ec88fSEmmanuel Vadot - arm,cortex-a53-pmu 38c66ec88fSEmmanuel Vadot - arm,cortex-a55-pmu 39c66ec88fSEmmanuel Vadot - arm,cortex-a57-pmu 40c66ec88fSEmmanuel Vadot - arm,cortex-a65-pmu 41c66ec88fSEmmanuel Vadot - arm,cortex-a72-pmu 42c66ec88fSEmmanuel Vadot - arm,cortex-a73-pmu 43c66ec88fSEmmanuel Vadot - arm,cortex-a75-pmu 44c66ec88fSEmmanuel Vadot - arm,cortex-a76-pmu 45c66ec88fSEmmanuel Vadot - arm,cortex-a77-pmu 46*5def4c47SEmmanuel Vadot - arm,cortex-a78-pmu 47c66ec88fSEmmanuel Vadot - arm,neoverse-e1-pmu 48c66ec88fSEmmanuel Vadot - arm,neoverse-n1-pmu 49c66ec88fSEmmanuel Vadot - brcm,vulcan-pmu 50c66ec88fSEmmanuel Vadot - cavium,thunder-pmu 51c66ec88fSEmmanuel Vadot - qcom,krait-pmu 52c66ec88fSEmmanuel Vadot - qcom,scorpion-pmu 53c66ec88fSEmmanuel Vadot - qcom,scorpion-mp-pmu 54c66ec88fSEmmanuel Vadot 55c66ec88fSEmmanuel Vadot interrupts: 56c66ec88fSEmmanuel Vadot # Don't know how many CPUs, so no constraints to specify 57c66ec88fSEmmanuel Vadot description: 1 per-cpu interrupt (PPI) or 1 interrupt per core. 58c66ec88fSEmmanuel Vadot 59c66ec88fSEmmanuel Vadot interrupt-affinity: 60c66ec88fSEmmanuel Vadot $ref: /schemas/types.yaml#/definitions/phandle-array 61c66ec88fSEmmanuel Vadot description: 62c66ec88fSEmmanuel Vadot When using SPIs, specifies a list of phandles to CPU 63c66ec88fSEmmanuel Vadot nodes corresponding directly to the affinity of 64c66ec88fSEmmanuel Vadot the SPIs listed in the interrupts property. 65c66ec88fSEmmanuel Vadot 66c66ec88fSEmmanuel Vadot When using a PPI, specifies a list of phandles to CPU 67c66ec88fSEmmanuel Vadot nodes corresponding to the set of CPUs which have 68c66ec88fSEmmanuel Vadot a PMU of this type signalling the PPI listed in the 69c66ec88fSEmmanuel Vadot interrupts property, unless this is already specified 70c66ec88fSEmmanuel Vadot by the PPI interrupt specifier itself (in which case 71c66ec88fSEmmanuel Vadot the interrupt-affinity property shouldn't be present). 72c66ec88fSEmmanuel Vadot 73c66ec88fSEmmanuel Vadot This property should be present when there is more than 74c66ec88fSEmmanuel Vadot a single SPI. 75c66ec88fSEmmanuel Vadot 76c66ec88fSEmmanuel Vadot qcom,no-pc-write: 77c66ec88fSEmmanuel Vadot type: boolean 78c66ec88fSEmmanuel Vadot description: 79c66ec88fSEmmanuel Vadot Indicates that this PMU doesn't support the 0xc and 0xd events. 80c66ec88fSEmmanuel Vadot 81c66ec88fSEmmanuel Vadot secure-reg-access: 82c66ec88fSEmmanuel Vadot type: boolean 83c66ec88fSEmmanuel Vadot description: 84c66ec88fSEmmanuel Vadot Indicates that the ARMv7 Secure Debug Enable Register 85c66ec88fSEmmanuel Vadot (SDER) is accessible. This will cause the driver to do 86c66ec88fSEmmanuel Vadot any setup required that is only possible in ARMv7 secure 87c66ec88fSEmmanuel Vadot state. If not present the ARMv7 SDER will not be touched, 88c66ec88fSEmmanuel Vadot which means the PMU may fail to operate unless external 89c66ec88fSEmmanuel Vadot code (bootloader or security monitor) has performed the 90c66ec88fSEmmanuel Vadot appropriate initialisation. Note that this property is 91c66ec88fSEmmanuel Vadot not valid for non-ARMv7 CPUs or ARMv7 CPUs booting Linux 92c66ec88fSEmmanuel Vadot in Non-secure state. 93c66ec88fSEmmanuel Vadot 94c66ec88fSEmmanuel Vadotrequired: 95c66ec88fSEmmanuel Vadot - compatible 96c66ec88fSEmmanuel Vadot 976be33864SEmmanuel VadotadditionalProperties: false 986be33864SEmmanuel Vadot 99c66ec88fSEmmanuel Vadot... 100