On Thu, May 27, 2021 at 9:23 AM Rob Herring <robh@xxxxxxxxxx> wrote: > > On Thu, 27 May 2021 11:42:27 +0530, Rajendra Nayak wrote: > > While most devices within power-domains which support performance states, > > scale the performance state dynamically, some devices might want to > > set a static/default performance state while the device is active. > > These devices typically would also run off a fixed clock and not support > > dynamically scaling the device's performance, also known as DVFS techniques. > > Add a property 'assigned-performance-states' which client devices can > > use to set this default performance state on their power-domains. > > > > Signed-off-by: Rajendra Nayak <rnayak@xxxxxxxxxxxxxx> > > --- > > .../devicetree/bindings/power/power-domain.yaml | 50 ++++++++++++++++++++++ > > 1 file changed, 50 insertions(+) > > > > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' > on your patch (DT_CHECKER_FLAGS is new in v5.13): > > yamllint warnings/errors: > ./Documentation/devicetree/bindings/power/power-domain.yaml:72:8: [warning] wrong indentation: expected 6 but found 7 (indentation) > > dtschema/dtc warnings/errors: > Documentation/devicetree/bindings/power/power-domain.example.dt.yaml:0:0: /example-3/power-controller@43210000/opp-table: failed to match any schema with compatible: ['operating-points-v2'] You don't really need to worry about this one as it is already a warning (but patches welcome if someone wants to convert the OPP binding). Rob
