[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <41781640ceee45e763bb0f3d6c765fea76826fa5.camel@mediatek.com>
Date: Wed, 6 Apr 2022 11:32:18 +0800
From: Jia-Wei Chang <jia-wei.chang@...iatek.com>
To: Krzysztof Kozlowski <krzk@...nel.org>,
MyungJoo Ham <myungjoo.ham@...sung.com>,
Kyungmin Park <kyungmin.park@...sung.com>,
Chanwoo Choi <cw00.choi@...sung.com>,
Rob Herring <robh+dt@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Liam Girdwood <lgirdwood@...il.com>,
Mark Brown <broonie@...nel.org>
CC: <linux-pm@...r.kernel.org>, <devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>, <fan.chen@...iatek.com>,
<louis.yu@...iatek.com>, <roger.lu@...iatek.com>,
<Allen-yy.Lin@...iatek.com>,
<Project_Global_Chrome_Upstream_Group@...iatek.com>,
<hsinyi@...gle.com>,
Jia-Wei Chang <jia-wei.chang@...iatek.corp-partner.google.com>
Subject: Re: [PATCH 1/3] dt-bindings: devfreq: mediatek: add mtk cci devfreq
dt-bindings
On Sat, 2022-04-02 at 13:31 +0200, Krzysztof Kozlowski wrote:
> On 01/04/2022 15:39, Jia-Wei Chang wrote:
> > > > >
> > > > > > +
> > > > > > + operating-points-v2:
> > > > > > + description:
> > > > > > + For details, please refer to
> > > > > > + Documentation/devicetree/bindings/opp/opp-v2.yaml
> > > > > > +
> > > > > > + opp-table: true
> > > > >
> > > > > Same comments as your CPU freq bindings apply.
> > > >
> > > > mtk-cci-devfreq is a new driver and its arch is same as
> > > > mediatek-
> > > > cpufreq so that the properties of mtk-cci are refer to
> > > > mediatek-
> > > > cpufreq
> > > > bindings.
> > > > operating-point-v2 is used to determine the voltage and
> > > > frequency
> > > > of
> > > > dvfs which is further utilized by mtk-cci-devfreq.
> > >
> > > "operating-point-v2" is understood, but the same as in cpufreq
> > > bindings,
> > > I am questioning why do you have "opp-table: true". It's a bit
> > > confusing, so maybe I miss something?
> >
> > Yes, you're correct.
> > "opp-table: true" should be removed.
> > I messed it up.
>
> No, I think I was wrong. The opp-table pretty frequently is embedded
> in
> the the device node itself. The operating-points-v2 references it.
>
> You don't use it in the example, but it might be a valid usage, so it
> can stay. Sorry for the confusion, it passed some time since I looked
> at
> OPP bindings.
You remind me of "opp-table: true" and the reason why I use it here is
exactly as you mentioned. Sorry I was not familiar enough with this to
respond it clearly and confidently.
I think it is proper to keep "opp-table: true" and add a complete opp
table information in dts example here as well.
Thanks for your comments.
>
>
> Best regards,
> Krzysztof
Powered by blists - more mailing lists