From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jia-Wei Chang <jia-wei.chang@mediatek.com>,
MyungJoo Ham <myungjoo.ham@samsung.com>,
Kyungmin Park <kyungmin.park@samsung.com>,
Chanwoo Choi <cw00.choi@samsung.com>,
Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>
Cc: linux-pm@vger.kernel.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org,
fan.chen@mediatek.com, louis.yu@mediatek.com,
roger.lu@mediatek.com, Allen-yy.Lin@mediatek.com,
Project_Global_Chrome_Upstream_Group@mediatek.com,
hsinyi@google.com,
Jia-Wei Chang <jia-wei.chang@mediatek.corp-partner.google.com>
Subject: Re: [PATCH 1/3] dt-bindings: devfreq: mediatek: add mtk cci devfreq dt-bindings
Date: Sat, 2 Apr 2022 13:31:22 +0200 [thread overview]
Message-ID: <ac0e3336-f9eb-def9-68ea-ab49e2c467a1@kernel.org> (raw)
In-Reply-To: <126e0905c2eb9f22a0be46dd7aa8ac891622346d.camel@mediatek.com>
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.
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-02 11:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-07 12:25 [PATCH 0/3] devfreq: mediatek: introduce MTK cci devfreq Tim Chang
2022-03-07 12:25 ` [PATCH 1/3] dt-bindings: devfreq: mediatek: add mtk cci devfreq dt-bindings Tim Chang
2022-03-07 21:42 ` Krzysztof Kozlowski
2022-03-24 12:11 ` Jia-Wei Chang
2022-03-24 12:44 ` Krzysztof Kozlowski
2022-04-01 13:39 ` Jia-Wei Chang
2022-04-02 11:31 ` Krzysztof Kozlowski [this message]
2022-04-06 3:32 ` Jia-Wei Chang
2022-03-07 12:25 ` [PATCH 2/3] devfreq: mediatek: add mt8183 cci devfreq driver Tim Chang
2022-03-07 16:44 ` Hsin-Yi Wang
2022-04-07 21:52 ` Kevin Hilman
2022-04-08 2:53 ` Johnson Wang
2022-03-07 21:51 ` Krzysztof Kozlowski
2022-03-24 12:17 ` Jia-Wei Chang
2022-04-07 3:20 ` Chanwoo Choi
2022-04-07 11:45 ` Jia-Wei Chang
2022-03-07 12:25 ` [PATCH 3/3] devfreq: mediatek: add platform data to support mt8186 Tim Chang
2022-03-07 21:52 ` Krzysztof Kozlowski
2022-03-24 12:19 ` Jia-Wei Chang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ac0e3336-f9eb-def9-68ea-ab49e2c467a1@kernel.org \
--to=krzk@kernel.org \
--cc=Allen-yy.Lin@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=broonie@kernel.org \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=fan.chen@mediatek.com \
--cc=hsinyi@google.com \
--cc=jia-wei.chang@mediatek.com \
--cc=jia-wei.chang@mediatek.corp-partner.google.com \
--cc=kyungmin.park@samsung.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=louis.yu@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=myungjoo.ham@samsung.com \
--cc=robh+dt@kernel.org \
--cc=roger.lu@mediatek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).