[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c83ae91b-6901-de2b-913e-b28af73c52fa@arm.com>
Date: Tue, 22 Feb 2022 10:03:38 +0000
From: Lukasz Luba <lukasz.luba@....com>
To: Viresh Kumar <viresh.kumar@...aro.org>
Cc: linux-kernel@...r.kernel.org, dietmar.eggemann@....com,
rafael@...nel.org, daniel.lezcano@...aro.org, nm@...com,
sboyd@...nel.org, mka@...omium.org, dianders@...omium.org,
robh+dt@...nel.org, devicetree@...r.kernel.org,
linux-pm@...r.kernel.org
Subject: Re: [RFC][PATCH 1/2] dt-bindings: power: add Energy Model bindings
On 2/22/22 09:45, Viresh Kumar wrote:
> On 22-02-22, 08:06, Lukasz Luba wrote:
>> I'm not sure if that would be flexible enough to meet the requirement:
>> power for each OPP might be different in one board vs. other board.
>
> Don't DT files overload values from board files all the time ? Why wouldn't the
> same apply for OPP table as well ?
In that SoC and family of the boards, there are no such examples.
It used to be popular in arm32 boards, but I'm not sure nowadays.
>
>> AFAIK the OPP definition is more SoC specific.
>
> This isn't about OPP definition as well, but just that if DT allows you to
> override or not. I think it will.
>
Redefining the whole OPP table, when the freq, voltage, interconnect,
and other old entries don't change isn't too messy?
As I said, I would prefer something lightweight, not redefining all
stuff from OPP in every board file.
Powered by blists - more mailing lists