On Wed, Oct 28, 2020 at 02:08:44PM +0000, Lukasz Luba wrote: > Add opp-sustainable as an additional property in the OPP node to describe > the sustainable performance level of the device. This will help to > estimate the sustainable performance of the whole system. > > Signed-off-by: Lukasz Luba <lukasz.luba@xxxxxxx> > --- > Documentation/devicetree/bindings/opp/opp.txt | 4 ++++ > 1 file changed, 4 insertions(+) > > diff --git a/Documentation/devicetree/bindings/opp/opp.txt b/Documentation/devicetree/bindings/opp/opp.txt > index 9847dfeeffcb..cd01028de305 100644 > --- a/Documentation/devicetree/bindings/opp/opp.txt > +++ b/Documentation/devicetree/bindings/opp/opp.txt > @@ -154,6 +154,10 @@ Optional properties: > - opp-suspend: Marks the OPP to be used during device suspend. If multiple OPPs > in the table have this, the OPP with highest opp-hz will be used. > > +- opp-sustainable: Marks the OPP as sustainable. This property can be used for > + estimating sustainable performance of the whole system. If multiple OPPs in > + the table have this, the OPP with highest opp-hz will be used. > + Isn't this just the inverse of the turbo? or boost? flag we already have? Couldn't this be learned? I ran at this frequency and then overheated. That could be dependent on ambient temperatures or dust build up on fans/heatsink. Rob