diff options
author | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2024-11-27 18:41:48 +0100 |
---|---|---|
committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2024-11-27 18:41:48 +0100 |
commit | 07d66acad26bad33defbf26516d0a84261ae6adc (patch) | |
tree | e13425163a553439ebef4d00b5e7ac4bd171ef67 /Documentation | |
parent | f3e66e78f2ecb18a55374f7d58030556b751dd79 (diff) | |
parent | 1a93226619dc5798dacee0734a5f1f886b358953 (diff) |
Merge branch 'pm-opp'
Merge OPP (Operating Performance Points) changes for 6.13-rc1:
- Describe opp-supported-hw property for ti-cpu (Dhruva Gole).
- Remove unused declarations from the OPP header file (Zhang Zekun).
* pm-opp:
dt-bindings: opp: operating-points-v2-ti-cpu: Describe opp-supported-hw
OPP: Remove unused declarations in header file
Diffstat (limited to 'Documentation')
-rw-r--r-- | Documentation/devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml | 20 |
1 files changed, 19 insertions, 1 deletions
diff --git a/Documentation/devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml b/Documentation/devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml index fd0c8d5c5f3e..624d1f3f1382 100644 --- a/Documentation/devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml +++ b/Documentation/devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml @@ -45,7 +45,25 @@ patternProperties: clock-latency-ns: true opp-hz: true opp-microvolt: true - opp-supported-hw: true + opp-supported-hw: + items: + items: + - description: + The revision of the SoC the OPP is supported by. + This can be easily obtained from the datasheet of the + part being ordered/used. For example, it will be 0x01 for SR1.0 + + - description: + The eFuse bits that indicate the particular OPP is available. + The device datasheet has a table talking about Device Speed Grades. + This table is to be sorted with only the unique elements of the + MAXIMUM OPERATING FREQUENCY starting from the first row which + tells the lowest OPP, to the highest. The corresponding bits + need to be set based on N elements of speed grade the device supports. + So, if there are 3 possible unique MAXIMUM OPERATING FREQUENCY + in the table, then BIT(0) | (1) | (2) will be set, which means + the value shall be 0x7. + opp-suspend: true turbo-mode: true |