From: Rob Herring <robh@kernel.org>
To: Dhruva Gole <d-gole@ti.com>
Cc: Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Stephen Boyd <sboyd@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: opp: operating-points-v2-ti-cpu: Describe opp-supported-hw
Date: Tue, 3 Sep 2024 10:27:05 -0500 [thread overview]
Message-ID: <20240903152705.GA1044006-robh@kernel.org> (raw)
In-Reply-To: <20240903-b4-opp-dt-binding-fix-v1-1-f7e186456d9f@ti.com>
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
>
next prev parent reply other threads:[~2024-09-03 15:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 10:30 [PATCH 0/2] dt-bindings: opp: operating-points-v2-ti-cpu: Describe opp-supported-hw Dhruva Gole
2024-09-03 10:30 ` [PATCH 1/2] " Dhruva Gole
2024-09-03 15:27 ` Rob Herring [this message]
2024-09-03 10:30 ` [PATCH 2/2] dt-bindings: opp: operating-points-v2-ti-cpu: Update maintainers Dhruva Gole
2024-09-03 15:27 ` Rob Herring (Arm)
2024-09-04 6:50 ` Viresh Kumar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240903152705.GA1044006-robh@kernel.org \
--to=robh@kernel.org \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=nm@ti.com \
--cc=sboyd@kernel.org \
--cc=vigneshr@ti.com \
--cc=viresh.kumar@linaro.org \
--cc=vireshk@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.