Message ID | 20220411154347.491396-1-krzysztof.kozlowski@linaro.org |
---|---|
Headers | show |
Series | ufs: set power domain performance state when scaling gears | expand |
On Mon 11 Apr 08:43 PDT 2022, Krzysztof Kozlowski wrote: > Devices might need to control several clocks when scaling the frequency > and voltage. Allow passing array of clock frequencies, similarly to the > voltages. > > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org> > --- > Documentation/devicetree/bindings/opp/opp-v2-base.yaml | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/Documentation/devicetree/bindings/opp/opp-v2-base.yaml b/Documentation/devicetree/bindings/opp/opp-v2-base.yaml > index 76c8acd981b3..1d7216008f95 100644 > --- a/Documentation/devicetree/bindings/opp/opp-v2-base.yaml > +++ b/Documentation/devicetree/bindings/opp/opp-v2-base.yaml > @@ -50,6 +50,14 @@ patternProperties: > property to uniquely identify the OPP nodes exists. Devices like power > domains must have another (implementation dependent) property. > > + This can be also an array of frequencies for each clock provided to the > + device. In such case value of 0 means the clock frequency should not > + be configured for given clock. > + minItems: 1 > + maxItems: 16 > + items: > + maxItems: 1 > + > opp-microvolt: > description: | > Voltage for the OPP > -- > 2.32.0 >
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>
On Mon, 11 Apr 2022 17:43:43 +0200, Krzysztof Kozlowski wrote: > Devices might need to control several clocks when scaling the frequency > and voltage. Allow passing array of clock frequencies, similarly to the > voltages. > > Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > --- > Documentation/devicetree/bindings/opp/opp-v2-base.yaml | 8 ++++++++ > 1 file changed, 8 insertions(+) > Acked-by: Rob Herring <robh@kernel.org>