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: Thu, 24 Mar 2022 13:44:59 +0100 [thread overview]
Message-ID: <aa34eccf-ef08-4a8f-7a6c-7fbd05bd54b6@kernel.org> (raw)
In-Reply-To: <13482b1b4244df5c0c0a4d6a60cdb2a7ba88500a.camel@mediatek.com>
On 24/03/2022 13:11, Jia-Wei Chang wrote:
>>
>> Remove "driver Device Tree Bindings". "Devfreq" is Linuxism, so this
>> maybe "bus frequency scaling"? Although later you call the device
>> node
>> as cci.
>
> Should I use "Binding for MediaTek's Cache Coherent Interconnect (CCI)
> frequency and voltage scaling" as new title?
I just suggested to remove word "bindings" so do not add it again. This
should be a title for hardware.
Now what exactly is it - you should know better than me. :)
"MediaTek's Cache Coherent Interconnect (CCI) frequency and voltage
scaling" sounds good to me, assuming that this is the hardware we talk
here about. :)
>
>>
>>> +
>>> +maintainers:
>>> + - Jia-Wei Chang <jia-wei.chang@mediatek.com>
>>> +
>>> +description: |
>>> + This module is used to create CCI DEVFREQ.
>>> + The performance will depend on both CCI frequency and CPU
>>> frequency.
>>> + For MT8186, CCI co-buck with Little core.
>>> + Contain CCI opp table for voltage and frequency scaling.
>>
>> Half of this description (first and last sentence) does not describe
>> the
>> actual hardware. Please describe hardware, not driver.
>
> Sure, I will fix it in the next version.
>
>>
>>> +
>>> +properties:
>>> + compatible:
>>> + const: "mediatek,mt8186-cci"
>>
>> No need for quotes.
>
> Sure, I will fix it in the next version.
>
>>
>>> +
>>> + clocks:
>>> + items:
>>> + - description:
>>> + The first one is the multiplexer for clock input of CPU
>>> cluster.
>>> + - description:
>>> + The other is used as an intermediate clock source when
>>> the original
>>> + CPU is under transition and not stable yet.
>>> +
>>> + clock-names:
>>> + items:
>>> + - const: "cci"
>>> + - const: "intermediate"
>>
>> No need for quotes.
>
> Sure, I will fix it in the next version.
>
>>
>>> +
>>> + 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?
>
>>
>>> +
>>> + proc-supply:
>>> + description:
>>> + Phandle of the regulator for CCI that provides the supply
>>> voltage.
>>> +
>>> + sram-supply:
>>> + description:
>>> + Phandle of the regulator for sram of CCI that provides the
>>> supply
>>> + voltage. When present, the cci devfreq driver needs to do
>>> + "voltage tracking" to step by step scale up/down Vproc and
>>> Vsram to fit
>>> + SoC specific needs. When absent, the voltage scaling flow is
>>> handled by
>>> + hardware, hence no software "voltage tracking" is needed.
>>> +
>>> +required:
>>> + - compatible
>>> + - clocks
>>> + - clock-names
>>> + - operating-points-v2
>>> + - proc-supply
>>> +
>>> +additionalProperties: false
>>> +
>>> +examples:
>>> + - |
>>> + #include <dt-bindings/clock/mt8186-clk.h>
>>> + cci: cci {
>>
>> Node names should be generic and describe type of device. Are you
>> sure
>> this is a CCI? Maybe "interconnect" suits it better?
>
> Yes, this is a CCI and it is generic type of device like CPU in my
> opinion.
> If my understanding is correct, CCI is more suitable.
OK.
>
>>
>>> + compatible = "mediatek,mt8186-cci";
>>> + clocks = <&mcusys CLK_MCU_ARMPLL_BUS_SEL>, <&apmixedsys
>>> CLK_APMIXED_MAINPLL>;
>>> + clock-names = "cci", "intermediate";
>>> + operating-points-v2 = <&cci_opp>;
>>> + proc-supply = <&mt6358_vproc12_reg>;
>>> + sram-supply = <&mt6358_vsram_proc12_reg>;
>>> + };
>>
>>
>> Best regards,
>> Krzysztof
>
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-03-24 12:47 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 [this message]
2022-04-01 13:39 ` Jia-Wei Chang
2022-04-02 11:31 ` Krzysztof Kozlowski
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=aa34eccf-ef08-4a8f-7a6c-7fbd05bd54b6@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).