[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1f387cb5-2ed7-5001-d846-d059499b1347@linaro.org>
Date: Mon, 13 Feb 2023 11:26:52 +0100
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Christian Marangi <ansuelsmth@...il.com>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konrad.dybcio@...aro.org>,
Ilia Lin <ilia.lin@...nel.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
Viresh Kumar <viresh.kumar@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Nishanth Menon <nm@...com>, Stephen Boyd <sboyd@...nel.org>,
linux-arm-msm@...r.kernel.org, linux-pm@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v6 2/3] dt-bindings: cpufreq: qcom-cpufreq-nvmem: make cpr
bindings optional
On 08/02/2023 16:39, Christian Marangi wrote:
> The qcom-cpufreq-nvmem driver supports 2 kind of devices:
> - pre-cpr that doesn't have power-domains and base everything on nvmem
> cells and multiple named microvolt bindings.
> Doesn't need required-opp binding in the opp nodes as they are only
> used for genpd based devices.
> - cpr-based that require power-domain in the cpu nodes and use various
> source to decide the correct voltage and freq
> Require required-opp binding since they need to be linked to the
> related opp-level.
>
> When the schema was introduced, it was wrongly set to always require these
> binding but this is not the case for pre-cpr devices.
>
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
Best regards,
Krzysztof
Powered by blists - more mailing lists