From: Rob Herring <robh@kernel.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Viresh Kumar <vireshk@kernel.org>, Nishanth Menon <nm@ti.com>,
Alim Akhtar <alim.akhtar@samsung.com>,
Avri Altman <avri.altman@wdc.com>,
"James E.J. Bottomley" <jejb@linux.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Taniya Das <tdas@codeaurora.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
linux-clk <linux-clk@vger.kernel.org>,
devicetree@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:THERMAL" <linux-pm@vger.kernel.org>,
SCSI <linux-scsi@vger.kernel.org>
Subject: Re: [RFC PATCH v2 3/6] dt-bindings: ufs: common: add OPP table
Date: Thu, 14 Apr 2022 10:29:05 -0500 [thread overview]
Message-ID: <CAL_JsqKmr_4rQPMYMvUyr9PL9NBPS0sjUsg3Z7VuDguMx7NwqQ@mail.gmail.com> (raw)
In-Reply-To: <Ylg83Ub7wuElT+Bu@robh.at.kernel.org>
On Thu, Apr 14, 2022 at 10:25 AM Rob Herring <robh@kernel.org> wrote:
>
> On Mon, Apr 11, 2022 at 05:43:44PM +0200, Krzysztof Kozlowski wrote:
> > Except scaling UFS and bus clocks, it's necessary to scale also the
> > voltages of regulators or power domain performance state levels. Adding
> > Operating Performance Points table allows to adjust power domain
> > performance state, depending on the UFS clock speed.
> >
> > OPPv2 deprecates previous property limited to clock scaling:
> > freq-table-hz.
> >
> > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> >
> > ---
> >
> > Not adding Rob's review tag because patch changed significantly.
> > ---
> > .../devicetree/bindings/ufs/ufs-common.yaml | 34 +++++++++++++++++--
> > 1 file changed, 31 insertions(+), 3 deletions(-)
> >
> > diff --git a/Documentation/devicetree/bindings/ufs/ufs-common.yaml b/Documentation/devicetree/bindings/ufs/ufs-common.yaml
> > index 47a4e9e1a775..d7d2c8a136bb 100644
> > --- a/Documentation/devicetree/bindings/ufs/ufs-common.yaml
> > +++ b/Documentation/devicetree/bindings/ufs/ufs-common.yaml
> > @@ -20,11 +20,24 @@ properties:
> > items:
> > - description: Minimum frequency for given clock in Hz
> > - description: Maximum frequency for given clock in Hz
> > + deprecated: true
> > description: |
> > + Preferred is operating-points-v2.
> > +
> > Array of <min max> operating frequencies in Hz stored in the same order
> > - as the clocks property. If this property is not defined or a value in the
> > - array is "0" then it is assumed that the frequency is set by the parent
> > - clock or a fixed rate clock source.
> > + as the clocks property. If either this property or operating-points-v2 is
> > + not defined or a value in the array is "0" then it is assumed that the
> > + frequency is set by the parent clock or a fixed rate clock source.
> > +
> > + operating-points-v2:
> > + description:
> > + Preferred over freq-table-hz.
> > + If present, each OPP must contain array of frequencies stored in the same
> > + order for each clock. If clock frequency in the array is "0" then it is
> > + assumed that the frequency is set by the parent clock or a fixed rate
> > + clock source.
> > +
> > + opp-table: true
> >
> > interrupts:
> > maxItems: 1
> > @@ -75,8 +88,23 @@ properties:
> >
> > dependencies:
> > freq-table-hz: [ 'clocks' ]
> > + operating-points-v2: [ 'clocks', 'clock-names' ]
> >
> > required:
> > - interrupts
> >
> > +allOf:
> > + - if:
> > + required:
> > + - freq-table-hz
> > + then:
> > + properties:
> > + operating-points-v2: false
> > + - if:
> > + required:
> > + - operating-points-v2
> > + then:
> > + properties:
> > + freq-table-hz: false
>
> You could also express this as:
>
> oneOf:
> - required: [ freq-table-hz ]
> - required: [ operating-points-v2 ]
> - not:
> required: [ freq-table-hz, operating-points-v2 ]
Err, NM. That doesn't work...
Reviewed-by: Rob Herring <robh@kernel.org>
next prev parent reply other threads:[~2022-04-14 15:48 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 15:43 [RFC PATCH v2 0/6] ufs: set power domain performance state when scaling gears Krzysztof Kozlowski
2022-04-11 15:43 ` [RFC PATCH v2 1/6] dt-bindings: clock: qcom,gcc-sdm845: add parent power domain Krzysztof Kozlowski
2022-04-12 15:22 ` Bjorn Andersson
2022-04-14 15:20 ` Rob Herring
2022-04-11 15:43 ` [RFC PATCH v2 2/6] dt-bindings: opp: accept array of frequencies Krzysztof Kozlowski
2022-04-12 15:23 ` Bjorn Andersson
2022-04-19 16:48 ` Rob Herring
2022-04-11 15:43 ` [RFC PATCH v2 3/6] dt-bindings: ufs: common: add OPP table Krzysztof Kozlowski
2022-04-14 15:25 ` Rob Herring
2022-04-14 15:29 ` Rob Herring [this message]
2022-04-11 15:43 ` [RFC PATCH v2 4/6] PM: opp: allow control of multiple clocks Krzysztof Kozlowski
2022-04-12 17:15 ` Bjorn Andersson
2022-04-13 9:07 ` Krzysztof Kozlowski
2022-04-20 3:06 ` Bjorn Andersson
2022-04-25 7:27 ` Viresh Kumar
2022-05-09 10:38 ` Krzysztof Kozlowski
2022-05-10 4:40 ` Viresh Kumar
2022-05-10 13:09 ` Krzysztof Kozlowski
2022-05-11 5:06 ` Viresh Kumar
[not found] ` <20220518235708.1A04CC385A9@smtp.kernel.org>
2022-05-19 8:03 ` Krzysztof Kozlowski
[not found] ` <20220520005934.8AB1DC385AA@smtp.kernel.org>
2022-05-25 7:05 ` Viresh Kumar
[not found] ` <20220525160455.67E2BC385B8@smtp.kernel.org>
2022-05-26 10:27 ` Viresh Kumar
2022-05-31 10:30 ` Viresh Kumar
2022-06-01 11:23 ` Krzysztof Kozlowski
2022-06-10 8:22 ` Viresh Kumar
[not found] ` <20220422234402.B66DDC385A4@smtp.kernel.org>
2022-04-25 10:03 ` Krzysztof Kozlowski
2022-04-11 15:43 ` [RFC PATCH v2 5/6] ufs: use PM OPP when scaling gears Krzysztof Kozlowski
2022-04-12 18:15 ` Bjorn Andersson
2022-04-19 17:01 ` Manivannan Sadhasivam
2022-04-20 10:04 ` Krzysztof Kozlowski
2022-04-11 15:43 ` [RFC PATCH v2 6/6] arm64: dts: qcom: sdm845: control RPMHPD performance states with UFS Krzysztof Kozlowski
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=CAL_JsqKmr_4rQPMYMvUyr9PL9NBPS0sjUsg3Z7VuDguMx7NwqQ@mail.gmail.com \
--to=robh@kernel.org \
--cc=agross@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=avri.altman@wdc.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jejb@linux.ibm.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=mturquette@baylibre.com \
--cc=nm@ti.com \
--cc=rafael@kernel.org \
--cc=sboyd@kernel.org \
--cc=tdas@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).