From: Mason Huo <mason.huo@starfivetech.com>
To: Shengyu Qu <wiagn233@outlook.com>,
Conor Dooley <conor.dooley@microchip.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Viresh Kumar <viresh.kumar@linaro.org>,
Emil Renner Berthing <kernel@esmil.dk>,
"Rob Herring" <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, <linux-pm@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-riscv@lists.infradead.org>
Subject: Re: [PATCH v1 1/3] riscv: dts: starfive: Enable axp15060 pmic for cpufreq
Date: Wed, 12 Apr 2023 10:36:21 +0800 [thread overview]
Message-ID: <e0f27ed2-9144-ff91-fe11-92e19eaf6013@starfivetech.com> (raw)
In-Reply-To: <TY3P286MB261181FB1FDAF6B14CDB266B989A9@TY3P286MB2611.JPNP286.PROD.OUTLOOK.COM>
On 2023/4/11 22:49, Shengyu Qu wrote:
>> On Tue, Apr 11, 2023 at 04:32:55PM +0800, Mason Huo wrote:
>>> The VisionFive 2 board has an embedded pmic axp15060,
>>> which supports the cpu DVFS through the dcdc2 regulator.
>>> This patch enables axp15060 pmic and configs the dcdc2.
>>>
>>> Signed-off-by: Mason Huo <mason.huo@starfivetech.com>
>>> ---
>>> .../starfive/jh7110-starfive-visionfive-2.dtsi | 15 +++++++++++++++
>>> 1 file changed, 15 insertions(+)
>>>
>>> diff --git a/arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2.dtsi b/arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2.dtsi
>>> index 2a6d81609284..df582bddae4b 100644
>>> --- a/arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2.dtsi
>>> +++ b/arch/riscv/boot/dts/starfive/jh7110-starfive-visionfive-2.dtsi
>>> @@ -114,6 +114,21 @@ &i2c5 {
>>> pinctrl-names = "default";
>>> pinctrl-0 = <&i2c5_pins>;
>>> status = "okay";
>>> +
>>> + pmic: axp15060_reg@36 {
>> No underscores in node names please & "pmic" is the generic node name
>> for pmics.
>>
>> Cheers,
>> Conor.
>>
>>> + compatible = "x-powers,axp15060";
>>> + reg = <0x36>;
>>> +
>>> + regulators {
>>> + reg_dcdc2: dcdc2 {
>
> reg_dcdc2 seems not a good name, too generic for identification. In most
>
> cases, it's same as regulator-name but using "_" rather than "-".
>
Hi Shengyu,
Thanks for your review.
Will change to "vdd_cpu".
>>> + regulator-boot-on;
>
> It should not be used, in Documentation/devicetree/bindings/regulator
>
> /regulator.yaml, it is described as follows:
>
> "This property is intended to only be used for regulators where software
>
> cannot read the state of the regulator."
>
> In this case, regulator state is completely able to be read by driver.
>
> Best regards,
>
> Shengyu
>Will remove it.
Thanks
Mason
next prev parent reply other threads:[~2023-04-12 2:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-11 8:32 [PATCH v1 0/3] Add JH7110 cpufreq support Mason Huo
2023-04-11 8:32 ` [PATCH v1 1/3] riscv: dts: starfive: Enable axp15060 pmic for cpufreq Mason Huo
2023-04-11 9:13 ` Conor Dooley
2023-04-11 14:49 ` Shengyu Qu
2023-04-12 2:36 ` Mason Huo [this message]
2023-04-12 2:36 ` Mason Huo
2023-04-11 8:32 ` [PATCH v1 2/3] cpufreq: dt-platdev: Add JH7110 SOC to the allowlist Mason Huo
2023-04-11 9:20 ` Conor Dooley
2023-04-12 2:36 ` Mason Huo
2023-04-11 8:32 ` [PATCH v1 3/3] riscv: dts: starfive: Add cpu scaling for JH7110 SoC Mason Huo
2023-04-11 9:06 ` Conor Dooley
2023-04-12 2:35 ` Mason Huo
2023-04-11 15:58 ` [PATCH v1 0/3] Add JH7110 cpufreq support Rafael J. Wysocki
2023-04-21 7:47 ` Viresh Kumar
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=e0f27ed2-9144-ff91-fe11-92e19eaf6013@starfivetech.com \
--to=mason.huo@starfivetech.com \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@esmil.dk \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=viresh.kumar@linaro.org \
--cc=wiagn233@outlook.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