pmu.txt 2.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869
  1. * ARM Performance Monitor Units
  2. ARM cores often have a PMU for counting cpu and cache events like cache misses
  3. and hits. The interface to the PMU is part of the ARM ARM. The ARM PMU
  4. representation in the device tree should be done as under:-
  5. Required properties:
  6. - compatible : should be one of
  7. "apm,potenza-pmu"
  8. "arm,armv8-pmuv3"
  9. "arm,cortex-a72-pmu"
  10. "arm,cortex-a57-pmu"
  11. "arm,cortex-a53-pmu"
  12. "arm,cortex-a17-pmu"
  13. "arm,cortex-a15-pmu"
  14. "arm,cortex-a12-pmu"
  15. "arm,cortex-a9-pmu"
  16. "arm,cortex-a8-pmu"
  17. "arm,cortex-a7-pmu"
  18. "arm,cortex-a5-pmu"
  19. "arm,arm11mpcore-pmu"
  20. "arm,arm1176-pmu"
  21. "arm,arm1136-pmu"
  22. "brcm,vulcan-pmu"
  23. "cavium,thunder-pmu"
  24. "qcom,scorpion-pmu"
  25. "qcom,scorpion-mp-pmu"
  26. "qcom,krait-pmu"
  27. - interrupts : 1 combined interrupt or 1 per core. If the interrupt is a per-cpu
  28. interrupt (PPI) then 1 interrupt should be specified.
  29. Optional properties:
  30. - interrupt-affinity : When using SPIs, specifies a list of phandles to CPU
  31. nodes corresponding directly to the affinity of
  32. the SPIs listed in the interrupts property.
  33. When using a PPI, specifies a list of phandles to CPU
  34. nodes corresponding to the set of CPUs which have
  35. a PMU of this type signalling the PPI listed in the
  36. interrupts property, unless this is already specified
  37. by the PPI interrupt specifier itself (in which case
  38. the interrupt-affinity property shouldn't be present).
  39. This property should be present when there is more than
  40. a single SPI.
  41. - qcom,no-pc-write : Indicates that this PMU doesn't support the 0xc and 0xd
  42. events.
  43. - secure-reg-access : Indicates that the ARMv7 Secure Debug Enable Register
  44. (SDER) is accessible. This will cause the driver to do
  45. any setup required that is only possible in ARMv7 secure
  46. state. If not present the ARMv7 SDER will not be touched,
  47. which means the PMU may fail to operate unless external
  48. code (bootloader or security monitor) has performed the
  49. appropriate initialisation. Note that this property is
  50. not valid for non-ARMv7 CPUs or ARMv7 CPUs booting Linux
  51. in Non-secure state.
  52. Example:
  53. pmu {
  54. compatible = "arm,cortex-a9-pmu";
  55. interrupts = <100 101>;
  56. };