devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jason-ch Chen (陳建豪)" <Jason-ch.Chen@mediatek.com>
To: "amergnat@baylibre.com" <amergnat@baylibre.com>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"krzysztof.kozlowski+dt@linaro.org"
	<krzysztof.kozlowski+dt@linaro.org>,
	"angelogioacchino.delregno@collabora.com"
	<angelogioacchino.delregno@collabora.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"wenst@chromium.org" <wenst@chromium.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"nfraprado@collabora.com" <nfraprado@collabora.com>,
	"linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	Project_Global_Chrome_Upstream_Group
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [RESEND PATCH v4 4/4] arm64: dts: Add MediaTek MT8188 dts and evaluation board and Makefile
Date: Tue, 17 Oct 2023 07:48:44 +0000	[thread overview]
Message-ID: <7b2ab315d10e0e62fdf5597d0ca91346aa3db1df.camel@mediatek.com> (raw)
In-Reply-To: <3de3e2ad-382d-4e2f-8943-1cd284604ab7@baylibre.com>

Hi Alexandre,

On Mon, 2023-10-16 at 11:36 +0200, Alexandre Mergnat wrote:
>  	 
> 
..snip..
> > +&mt6359_vbbck_ldo_reg {
> > +regulator-always-on;
> > +};
> > +
> > +&mt6359_vcn33_2_bt_ldo_reg {
> > +regulator-always-on;
> > +};
> > +
> > +&mt6359_vcore_buck_reg {
> > +regulator-always-on;
> > +};
> > +
> > +&mt6359_vgpu11_buck_reg {
> > +regulator-always-on;
> > +};
> > +
> > +&mt6359_vpu_buck_reg {
> > +regulator-always-on;
> > +};
> > +
> > +&mt6359_vrf12_ldo_reg {
> > +regulator-always-on;
> > +};
> > +
> > +&mt6359_vufs_ldo_reg {
> > +regulator-always-on;
> > +};
> > +
> 
> This is a lot of always-on regulator.
> Is it possible to justify them? Maybe some of them should be just 
> included into a relevent node ? For example,
> "mt6359_vcn33_2_bt_ldo_reg" 
> could be into the bluetooth node right ?
> 
> Angelo already wrote me a feedback about that in the MT8365 serie:
> 
https://lore.kernel.org/all/ff7292f0-9055-1787-2543-e219fe30dddf@collabora.com/

Thank you for pointing out the problem.

The mt6359_vbbck_ldo_reg and mt6359_vcn33_2_bt_ldo_reg are not
necessary in the evb. The mt6359_vufs_ldo_reg is already included in
the mmc0 node. These nodes will be removed in the next version.

The remain power rails do not have specific users in linux kernel, but
they are powered by CPU/CORE/analog and are registered in the regulator
framework. The regulator framework has a power mechanism that shuts
down power rails with use count is 0 after 30 seconds of startup, and
then CPU/The power of CORE/analog cannot be turned off, so the
regulator-always-on property is added to the dts node.

> 
> > +&nor_flash {
> > +status = "okay";
> > +pinctrl-names = "default";
> > +pinctrl-0 = <&nor_pins_default>;
> > +#address-cells = <1>;
> > +#size-cells = <0>;
> 
..snip..
> 
> -- 
> Regards,
> Alexandre

Regards,
Jason

  reply	other threads:[~2023-10-17  7:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-21  6:02 [RESEND PATCH v4 0/4] Add basic node support for MediaTek MT8188 SoC Jason-ch Chen
2023-09-21  6:02 ` [RESEND PATCH v4 1/4] dt-bindings: arm: Add compatible for MediaTek MT8188 Jason-ch Chen
2023-09-21  6:02 ` [RESEND PATCH v4 2/4] dt-bindings: arm: mediatek: Add mt8188 pericfg compatible Jason-ch Chen
2023-09-21  6:02 ` [RESEND PATCH v4 3/4] dt-bindings: soc: mediatek: pwrap: Modify compatible for MT8188 Jason-ch Chen
2023-09-21  6:02 ` [RESEND PATCH v4 4/4] arm64: dts: Add MediaTek MT8188 dts and evaluation board and Makefile Jason-ch Chen
2023-10-16  9:36   ` Alexandre Mergnat
2023-10-17  7:48     ` Jason-ch Chen (陳建豪) [this message]
2023-10-17  8:38   ` Eugen Hristev
2023-10-17  9:00     ` Jason-ch Chen (陳建豪)

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=7b2ab315d10e0e62fdf5597d0ca91346aa3db1df.camel@mediatek.com \
    --to=jason-ch.chen@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=amergnat@baylibre.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --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=nfraprado@collabora.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;
as well as URLs for NNTP newsgroup(s).