From: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
To: Chen-Yu Tsai <wenst@chromium.org>
Cc: Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
kernel@collabora.com,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/3] arm64: dts: mediatek: asurada: Add display regulators
Date: Tue, 27 Sep 2022 17:13:37 -0400 [thread overview]
Message-ID: <20220927211337.idgcuawo7xsiexah@notapiano> (raw)
In-Reply-To: <CAGXv+5FErSBT-t6vz_2naApuPoC4PympWft-9Gd_MMPUTN+CsQ@mail.gmail.com>
Hi Chen-Yu,
thank you for the insights on the power supply hierarchy. Just a couple further
questions below.
On Wed, Sep 21, 2022 at 10:20:43PM +0800, Chen-Yu Tsai wrote:
> Hi,
>
> On Fri, Sep 9, 2022 at 1:12 AM Nícolas F. R. A. Prado
> <nfraprado@collabora.com> wrote:
> >
> > Add the regulators present on the Asurada platform that are used to
> > power the internal and external displays.
> >
> > Signed-off-by: Nícolas F. R. A. Prado <nfraprado@collabora.com>
> >
> > ---
> >
> > .../boot/dts/mediatek/mt8192-asurada.dtsi | 114 ++++++++++++++++++
> > 1 file changed, 114 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi b/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi
> > index 4b314435f8fd..1d99e470ea1a 100644
> > --- a/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi
> > +++ b/arch/arm64/boot/dts/mediatek/mt8192-asurada.dtsi
> > @@ -23,6 +23,42 @@ memory@40000000 {
> > reg = <0 0x40000000 0 0x80000000>;
> > };
> >
> > + pp1000_dpbrdg: regulator-1v0-dpbrdg {
> > + compatible = "regulator-fixed";
> > + regulator-name = "pp1000_dpbrdg";
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pp1000_dpbrdg_en_pins>;
> > + regulator-min-microvolt = <1000000>;
> > + regulator-max-microvolt = <1000000>;
>
> This is fed by a rail called PP1350_VS2, which is from the MT6359 PMIC.
> And this regulator is a proper LDO.
So, we should have an additional regulator node here called pp1350_vs2 which
will feed into pp1000_dpbrdg and that is itself fed in from mt6359_vs2_buck_reg
(from mt6359.dtsi). Is that right?
Also, is PP1350_VS2 just a simple switch or an LDO?
>
[..]
> > + pp1800_dpbrdg: regulator-1v8-dpbrdg {
> > + compatible = "regulator-fixed";
> > + regulator-name = "pp1800_dpbrdg";
> > + pinctrl-names = "default";
> > + pinctrl-0 = <&pp1800_dpbrdg_en_pins>;
> > + regulator-min-microvolt = <1800000>;
> > + regulator-max-microvolt = <1800000>;
>
> This regulator is only a power switch. Please drop the min/max properties.
> This is fed by a rail called PP1800_VIO18_U, which is from an LDO on the
> MT6359 PMIC.
Similarly, we should have a pp1800_vio18_u node that is fed in by
mt6359_vio18_ldo_reg, right? And is it a switch or an LDO?
Thanks,
Nícolas
>
> > + enable-active-high;
> > + regulator-boot-on;
> > + gpio = <&pio 126 GPIO_ACTIVE_HIGH>;
> > + };
> > +
[..]
_______________________________________________
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-09-27 21:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 17:11 [PATCH 0/3] arm64: dts: mediatek: asurada: Enable internal display Nícolas F. R. A. Prado
2022-09-08 17:11 ` [PATCH 1/3] arm64: dts: mediatek: asurada: Add display regulators Nícolas F. R. A. Prado
2022-09-09 7:46 ` AngeloGioacchino Del Regno
2022-09-21 13:48 ` Nícolas F. R. A. Prado
2022-09-21 13:58 ` AngeloGioacchino Del Regno
2022-09-21 14:20 ` Chen-Yu Tsai
2022-09-27 21:13 ` Nícolas F. R. A. Prado [this message]
2022-09-08 17:11 ` [PATCH 2/3] arm64: dts: mediatek: asurada: Add display backlight Nícolas F. R. A. Prado
2022-09-09 7:46 ` AngeloGioacchino Del Regno
2022-09-08 17:11 ` [PATCH 3/3] arm64: dts: mediatek: asurada: Enable internal display Nícolas F. R. A. Prado
2022-09-12 10:32 ` [PATCH 0/3] " Chen-Yu Tsai
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=20220927211337.idgcuawo7xsiexah@notapiano \
--to=nfraprado@collabora.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@collabora.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=robh+dt@kernel.org \
--cc=wenst@chromium.org \
/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