From: Chen-Yu Tsai <wenst@chromium.org>
To: Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: Chen-Yu Tsai <wenst@chromium.org>,
linux-mediatek@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 10/16] arm64: dts: mediatek: mt8195-cherry: Add MT6315 PMIC supplies
Date: Tue, 5 May 2026 18:14:00 +0800 [thread overview]
Message-ID: <20260505101408.1796563-11-wenst@chromium.org> (raw)
In-Reply-To: <20260505101408.1796563-1-wenst@chromium.org>
The MT8195 Cherry design has two MT6315 PMICs. One has 4 outputs ganged
together; the other has 2 outputs ganged together, and the other two
unused.
Add supplies for these two PMICs. Since the outputs are ganged together,
just add the supply for the first one.
Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
---
Changes since v1:
- Moved supplies to PMIC top level node
- Added all supplies
All supplies are connected, but since the regulators are ganged
together, only one regulator node is present.
---
arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi b/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi
index 0b9fedac842c..cf9855618494 100644
--- a/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi
+++ b/arch/arm64/boot/dts/mediatek/mt8195-cherry.dtsi
@@ -1472,6 +1472,10 @@ &spmi {
mt6315@6 {
compatible = "mediatek,mt6315-regulator";
reg = <0x6 SPMI_USID>;
+ pvdd1-supply = <&pp4200_z2>;
+ pvdd2-supply = <&pp4200_z2>;
+ pvdd3-supply = <&pp4200_z2>;
+ pvdd4-supply = <&pp4200_z2>;
regulators {
mt6315_6_vbuck1: vbuck1 {
@@ -1489,6 +1493,10 @@ mt6315_6_vbuck1: vbuck1 {
mt6315@7 {
compatible = "mediatek,mt6315-regulator";
reg = <0x7 SPMI_USID>;
+ pvdd1-supply = <&pp4200_z2>;
+ pvdd2-supply = <&pp4200_z2>;
+ pvdd3-supply = <&pp4200_z2>;
+ pvdd4-supply = <&pp4200_z2>;
regulators {
mt6315_7_vbuck1: vbuck1 {
--
2.54.0.545.g6539524ca2-goog
next prev parent reply other threads:[~2026-05-05 10:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 10:13 [PATCH v2 00/16] arm64: dts: mediatek: Regulator cleanup for Chromebooks Chen-Yu Tsai
2026-05-05 10:13 ` [PATCH v2 01/16] arm64: dts: mediatek: mt8186-corsola-voltorb: Add MT6315 PMIC supplies Chen-Yu Tsai
2026-05-05 10:13 ` [PATCH v2 02/16] arm64: dts: mediatek: mt6359: Switch to proper ldo_vcn33_[12] regulators Chen-Yu Tsai
2026-05-05 10:13 ` [PATCH v2 03/16] arm64: dts: mediatek: mt8192-asurada: Add MT6359 PMIC supplies Chen-Yu Tsai
2026-05-05 10:13 ` [PATCH v2 04/16] arm64: dts: mediatek: mt8192-asurada: Add MT6315 " Chen-Yu Tsai
2026-05-05 10:13 ` [PATCH v2 05/16] arm64: dts: mediatek: mt8192-asurada: Add supplies for ChromeOS EC regulators Chen-Yu Tsai
2026-05-05 10:13 ` [PATCH v2 06/16] arm64: dts: mediatek: mt8192-asurada: Add CPU power supplies Chen-Yu Tsai
2026-05-05 10:13 ` [PATCH v2 07/16] arm64: dts: mediatek: mt8192-asurada: Add SPI NOR flash power supply Chen-Yu Tsai
2026-05-05 10:13 ` [PATCH v2 08/16] arm64: dts: mediatek: mt8192-asurada: Fix WiFi regulator description Chen-Yu Tsai
2026-05-05 10:13 ` [PATCH v2 09/16] arm64: dts: mediatek: mt8195-cherry: Add MT6359 PMIC supplies Chen-Yu Tsai
2026-05-05 10:14 ` Chen-Yu Tsai [this message]
2026-05-05 10:14 ` [PATCH v2 11/16] arm64: dts: mediatek: mt8195-cherry: Add supplies for ChromeOS EC regulators Chen-Yu Tsai
2026-05-05 10:14 ` [PATCH v2 12/16] arm64: dts: mediatek: mt8195-cherry: Fix VBUS regulator description Chen-Yu Tsai
2026-05-05 10:14 ` [PATCH v2 13/16] arm64: dts: mediatek: mt8195-cherry: Add supply for SPI NOR flash Chen-Yu Tsai
2026-05-05 10:14 ` [PATCH v2 14/16] arm64: dts: mediatek: mt8195-cherry: Add vusb33 supplies for XHCI controllers Chen-Yu Tsai
2026-05-05 10:14 ` [PATCH v2 15/16] arm64: dts: mediatek: mt8188-geralt: Add MT6359 PMIC supplies Chen-Yu Tsai
2026-05-05 10:14 ` [PATCH v2 16/16] arm64: dts: mediatek: mt8188-geralt: Add little core CPU power supplies 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=20260505101408.1796563-11-wenst@chromium.org \
--to=wenst@chromium.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=devicetree@vger.kernel.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 \
/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