operating-points-v2-ti-cpu.yaml 3.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110
  1. # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
  2. %YAML 1.2
  3. ---
  4. $id: http://devicetree.org/schemas/opp/operating-points-v2-ti-cpu.yaml#
  5. $schema: http://devicetree.org/meta-schemas/core.yaml#
  6. title: TI CPU OPP (Operating Performance Points)
  7. description:
  8. TI SoCs, like those in the AM335x, AM437x, AM57xx, AM62x, and DRA7xx
  9. families, the CPU frequencies subset and the voltage value of each
  10. OPP vary based on the silicon variant used. The data sheet sections
  11. corresponding to "Operating Performance Points" describe the frequency
  12. and voltage values based on device type and speed bin information
  13. blown in corresponding eFuse bits as referred to by the Technical
  14. Reference Manual.
  15. This document extends the operating-points-v2 binding by providing
  16. the hardware description for the scheme mentioned above.
  17. maintainers:
  18. - Dhruva Gole <d-gole@ti.com>
  19. allOf:
  20. - $ref: opp-v2-base.yaml#
  21. properties:
  22. compatible:
  23. const: operating-points-v2-ti-cpu
  24. syscon:
  25. $ref: /schemas/types.yaml#/definitions/phandle
  26. description: |
  27. points to syscon node representing the control module
  28. register space of the SoC.
  29. opp-shared: true
  30. patternProperties:
  31. '^opp(-?[0-9]+)*$':
  32. type: object
  33. additionalProperties: false
  34. properties:
  35. clock-latency-ns: true
  36. opp-hz: true
  37. opp-microvolt: true
  38. opp-supported-hw:
  39. items:
  40. items:
  41. - description:
  42. The revision of the SoC the OPP is supported by.
  43. This can be easily obtained from the datasheet of the
  44. part being ordered/used. For example, it will be 0x01 for SR1.0
  45. - description:
  46. The eFuse bits that indicate the particular OPP is available.
  47. The device datasheet has a table talking about Device Speed Grades.
  48. This table is to be sorted with only the unique elements of the
  49. MAXIMUM OPERATING FREQUENCY starting from the first row which
  50. tells the lowest OPP, to the highest. The corresponding bits
  51. need to be set based on N elements of speed grade the device supports.
  52. So, if there are 3 possible unique MAXIMUM OPERATING FREQUENCY
  53. in the table, then BIT(0) | (1) | (2) will be set, which means
  54. the value shall be 0x7.
  55. opp-suspend: true
  56. turbo-mode: true
  57. required:
  58. - opp-hz
  59. - opp-supported-hw
  60. required:
  61. - compatible
  62. - syscon
  63. additionalProperties: false
  64. examples:
  65. - |
  66. opp-table {
  67. compatible = "operating-points-v2-ti-cpu";
  68. syscon = <&scm_conf>;
  69. opp-300000000 {
  70. opp-hz = /bits/ 64 <300000000>;
  71. opp-microvolt = <1100000 1078000 1122000>;
  72. opp-supported-hw = <0x06 0x0020>;
  73. opp-suspend;
  74. };
  75. opp-500000000 {
  76. opp-hz = /bits/ 64 <500000000>;
  77. opp-microvolt = <1100000 1078000 1122000>;
  78. opp-supported-hw = <0x01 0xFFFF>;
  79. };
  80. opp-600000000 {
  81. opp-hz = /bits/ 64 <600000000>;
  82. opp-microvolt = <1100000 1078000 1122000>;
  83. opp-supported-hw = <0x06 0x0040>;
  84. };
  85. opp-1000000000 {
  86. opp-hz = /bits/ 64 <1000000000>;
  87. opp-microvolt = <1325000 1298500 1351500>;
  88. opp-supported-hw = <0x04 0x0200>;
  89. };
  90. };