On 16-01-23, 10:38, Konrad Dybcio wrote: > In some instances (particularly with CPRh) we might want to specifiy > more than one qcom,opp-fuse-level, as the same OPP subnodes may be > used by different "CPR threads". We need to make sure that > n = num_threads entries is legal and so far nobody seems to use more > than two, so let's allow that. > > Acked-by: Rob Herring <robh@xxxxxxxxxx> > Signed-off-by: Konrad Dybcio <konrad.dybcio@xxxxxxxxxx> > --- > Documentation/devicetree/bindings/opp/opp-v2-qcom-level.yaml | 4 +++- > 1 file changed, 3 insertions(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/opp/opp-v2-qcom-level.yaml b/Documentation/devicetree/bindings/opp/opp-v2-qcom-level.yaml > index b9ce2e099ce9..a30ef93213c0 100644 > --- a/Documentation/devicetree/bindings/opp/opp-v2-qcom-level.yaml > +++ b/Documentation/devicetree/bindings/opp/opp-v2-qcom-level.yaml > @@ -30,7 +30,9 @@ patternProperties: > this OPP node. Sometimes several corners/levels shares a certain fuse > corner/level. A fuse corner/level contains e.g. ref uV, min uV, > and max uV. > - $ref: /schemas/types.yaml#/definitions/uint32 > + $ref: /schemas/types.yaml#/definitions/uint32-array > + minItems: 1 > + maxItems: 2 > > required: > - opp-level Applied. Thanks. -- viresh
