From: Jakob Hauser <jahau@rocketmail.com>
To: Stephan Gerhold <stephan@gerhold.net>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Sebastian Reichel <sre@kernel.org>, Lee Jones <lee@kernel.org>,
Raymond Hackley <raymondhackley@protonmail.com>,
Henrik Grimler <henrik@grimler.se>,
linux-arm-msm@vger.kernel.org, linux-kernel@vger.kernel.org,
phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht
Subject: Re: [PATCH RESEND] arm64: dts: qcom: msm8916-samsung-serranove: Add RT5033 PMIC with charger
Date: Sun, 18 Jun 2023 18:49:16 +0200 [thread overview]
Message-ID: <ab3e475f-27ae-e718-60bd-cb22f5070942@rocketmail.com> (raw)
In-Reply-To: <ZI2_565RFDtR3Sa-@gerhold.net>
Hi Stephan,
On 17.06.23 16:15, Stephan Gerhold wrote:
> On Sat, Jun 17, 2023 at 02:29:34AM +0200, Jakob Hauser wrote:
...
>> + regulators {
>> + safe_ldo_reg: SAFE_LDO {
>> + regulator-name = "SAFE_LDO";
>> + regulator-min-microvolt = <4900000>;
>> + regulator-max-microvolt = <4900000>;
>> + regulator-always-on;
>> + };
>> + ldo_reg: LDO {
>> + regulator-name = "LDO";
>> + regulator-min-microvolt = <2800000>;
>> + regulator-max-microvolt = <2800000>;
>> + };
>> + buck_reg: BUCK {
>> + regulator-name = "BUCK";
>> + regulator-min-microvolt = <1200000>;
>> + regulator-max-microvolt = <1200000>;
>> + };
>
> The "regulator-name"s here don't really seem useful, since they're just
> the same as the ones already declared in the driver. Can you drop them?
> Alternatively you could assign more useful board-specific names, such as
> the CAM_SENSOR_A2.8V that was used downstream.
>
> Also, I think it would be slightly clearer to prefix the regulator
> labels (safe_ldo_reg, ldo_reg etc) with rt5033_. Perhaps
> "rt5033_ldo_reg" or "rt5033_reg_ldo"?
...
About the "regulator-name"s I wasn't really aware. I don't have a strong
opinion on this.
With the downstream names, it would look like this:
regulators {
rt5033_reg_safe_ldo: SAFE_LDO {
regulator-name = "RT5033SafeLDO";
regulator-min-microvolt = <4900000>;
regulator-max-microvolt = <4900000>;
regulator-always-on;
};
rt5033_reg_ldo: LDO {
regulator-name = "CAM_SENSOR_A2.8V";
regulator-min-microvolt = <2800000>;
regulator-max-microvolt = <2800000>;
};
rt5033_reg_buck: BUCK {
regulator-name = "CAM_SENSOR_CORE_1.25V";
regulator-min-microvolt = <1200000>;
regulator-max-microvolt = <1200000>;
};
Dropping them would look like this:
regulators {
rt5033_reg_safe_ldo: SAFE_LDO {
regulator-min-microvolt = <4900000>;
regulator-max-microvolt = <4900000>;
regulator-always-on;
};
rt5033_reg_ldo: LDO {
regulator-min-microvolt = <2800000>;
regulator-max-microvolt = <2800000>;
};
rt5033_reg_buck: BUCK {
regulator-min-microvolt = <1200000>;
regulator-max-microvolt = <1200000>;
};
I would rather drop them. The first name "RT5033SafeLDO" doesn't add
much information. The other two I'm not fully sure if they provide the
cam sensor only or if there might be other users as well. Also it add an
additional set of names. When dropping them, the generic names SAFE_LDO,
LDO and BUCK are taken from the rt5033-regulator driver.
Unfortunately, I added the example in the dt-bindings with the generic
names. So this question might come up again when someone else adds
rt5033-regulators to another device.
For the phandle labels I'd go for rt5033_reg_..., I already changed them
in the examples above.
Kind regards,
Jakob
next prev parent reply other threads:[~2023-06-18 16:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230617002934.39408-1-jahau.ref@rocketmail.com>
2023-06-17 0:29 ` [PATCH RESEND] arm64: dts: qcom: msm8916-samsung-serranove: Add RT5033 PMIC with charger Jakob Hauser
2023-06-17 14:15 ` Stephan Gerhold
2023-06-18 16:49 ` Jakob Hauser [this message]
2023-06-18 19:11 ` Stephan Gerhold
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=ab3e475f-27ae-e718-60bd-cb22f5070942@rocketmail.com \
--to=jahau@rocketmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=henrik@grimler.se \
--cc=konrad.dybcio@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=raymondhackley@protonmail.com \
--cc=sre@kernel.org \
--cc=stephan@gerhold.net \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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