diff mbox series

[1/2] dt-bindings: opp: operating-points-v2-ti-cpu: Describe opp-supported-hw

Message ID 20240903-b4-opp-dt-binding-fix-v1-1-f7e186456d9f@ti.com (mailing list archive)
State Handled Elsewhere, archived
Headers show
Series dt-bindings: opp: operating-points-v2-ti-cpu: Describe opp-supported-hw | expand

Commit Message

Dhruva Gole Sept. 3, 2024, 10:30 a.m. UTC
It seems like we missed migrating the complete information from the old
DT binding where we had described what the opp-supported-hw is supposed
to describe. Hence, bring back the exact description from the previous
binding to the current one.

Fixes: e576a9a8603f ("dt-bindings: cpufreq: Convert ti-cpufreq to json schema")
Signed-off-by: Dhruva Gole <d-gole@ti.com>
---
 .../devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml         | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

Comments

Rob Herring Sept. 3, 2024, 3:27 p.m. UTC | #1
On Tue, Sep 03, 2024 at 04:00:07PM +0530, Dhruva Gole wrote:
> It seems like we missed migrating the complete information from the old
> DT binding where we had described what the opp-supported-hw is supposed
> to describe. Hence, bring back the exact description from the previous
> binding to the current one.
> 
> Fixes: e576a9a8603f ("dt-bindings: cpufreq: Convert ti-cpufreq to json schema")
> Signed-off-by: Dhruva Gole <d-gole@ti.com>
> ---
>  .../devicetree/bindings/opp/operating-points-v2-ti-cpu.yaml         | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> 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 02d1d2c17129..90855009cb81 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,11 @@ patternProperties:
>        clock-latency-ns: true
>        opp-hz: true
>        opp-microvolt: true
> -      opp-supported-hw: true
> +      opp-supported-hw:
> +        description: |
> +          Two bitfields indicating:
> +            1. Which revision of the SoC the OPP is supported by
> +            2. Which eFuse bits indicate this OPP is available

This does nothing to tell me how to populate the property.

>        opp-suspend: true
>        turbo-mode: true
>  
> 
> -- 
> 2.34.1
>
diff mbox series

Patch

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 02d1d2c17129..90855009cb81 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,11 @@  patternProperties:
       clock-latency-ns: true
       opp-hz: true
       opp-microvolt: true
-      opp-supported-hw: true
+      opp-supported-hw:
+        description: |
+          Two bitfields indicating:
+            1. Which revision of the SoC the OPP is supported by
+            2. Which eFuse bits indicate this OPP is available
       opp-suspend: true
       turbo-mode: true