Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 01/13] arm64: dts: mediatek: mt6359: Drop ldo_vcn33_[12]_wifi regulators
Date: Fri, 20 Mar 2026 16:43:33 +0800	[thread overview]
Message-ID: <20260320084351.2461060-2-wenst@chromium.org> (raw)
In-Reply-To: <20260320084351.2461060-1-wenst@chromium.org>

The ldo_vcn33_[12]_wifi and ldo_vcn33_[12]_bt are just two regulator
outputs instead of four. The wifi and bt parts refer to separate enable
bits that are OR-ed together to affect the actual regulator output. The
separate bits allow the wifi and bt stacks to enable their power without
coordination between them.

Drop the ldo_vcn33_[12]_wifi regulators. ldo_vcn33_[12]_bt are kept with
the "_bt" suffix due to DT binding backward compatibility.

Signed-off-by: Chen-Yu Tsai <wenst@chromium.org>
---
 arch/arm64/boot/dts/mediatek/mt6359.dtsi | 10 ----------
 1 file changed, 10 deletions(-)

diff --git a/arch/arm64/boot/dts/mediatek/mt6359.dtsi b/arch/arm64/boot/dts/mediatek/mt6359.dtsi
index 45ad69ee49ed..1c41c4701319 100644
--- a/arch/arm64/boot/dts/mediatek/mt6359.dtsi
+++ b/arch/arm64/boot/dts/mediatek/mt6359.dtsi
@@ -169,11 +169,6 @@ mt6359_vcn33_1_bt_ldo_reg: ldo_vcn33_1_bt {
 				regulator-min-microvolt = <2800000>;
 				regulator-max-microvolt = <3500000>;
 			};
-			mt6359_vcn33_1_wifi_ldo_reg: ldo_vcn33_1_wifi {
-				regulator-name = "vcn33_1_wifi";
-				regulator-min-microvolt = <2800000>;
-				regulator-max-microvolt = <3500000>;
-			};
 			mt6359_vaux18_ldo_reg: ldo_vaux18 {
 				regulator-name = "vaux18";
 				regulator-min-microvolt = <1800000>;
@@ -236,11 +231,6 @@ mt6359_vcn33_2_bt_ldo_reg: ldo_vcn33_2_bt {
 				regulator-min-microvolt = <2800000>;
 				regulator-max-microvolt = <3500000>;
 			};
-			mt6359_vcn33_2_wifi_ldo_reg: ldo_vcn33_2_wifi {
-				regulator-name = "vcn33_2_wifi";
-				regulator-min-microvolt = <2800000>;
-				regulator-max-microvolt = <3500000>;
-			};
 			mt6359_va12_ldo_reg: ldo_va12 {
 				regulator-name = "va12";
 				regulator-min-microvolt = <1200000>;
-- 
2.53.0.959.g497ff81fa9-goog



  reply	other threads:[~2026-03-20  8:44 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-20  8:43 arm64: dts: mediatek: Regulator cleanup for Chromebooks Chen-Yu Tsai
2026-03-20  8:43 ` Chen-Yu Tsai [this message]
2026-03-20  8:43 ` [PATCH 02/13] arm64: dts: mediatek: mt6359: Add label for regulator sub-node Chen-Yu Tsai
2026-03-20  8:43 ` [PATCH 03/13] arm64: dts: mediatek: mt8192-asurada: Add MT6359 PMIC supplies Chen-Yu Tsai
2026-03-20  8:43 ` [PATCH 04/13] arm64: dts: mediatek: mt8192-asurada: Add MT6315 " Chen-Yu Tsai
2026-03-20 15:24   ` Fei Shao
2026-03-20  8:43 ` [PATCH 05/13] arm64: dts: mediatek: mt8192-asurada: Add supplies for ChromeOS EC regulators Chen-Yu Tsai
2026-03-20  8:43 ` [PATCH 06/13] arm64: dts: mediatek: mt8192-asurada: Add CPU power supplies Chen-Yu Tsai
2026-03-20  8:43 ` [PATCH 07/13] arm64: dts: mediatek: mt8192-asurada: Add SPI NOR flash power supply Chen-Yu Tsai
2026-03-20  8:43 ` [PATCH 08/13] arm64: dts: mediatek: mt8192-asurada: Fix WiFi regulator description Chen-Yu Tsai
2026-03-20  8:43 ` [PATCH 09/13] arm64: dts: mediatek: mt8195-cherry: Add MT6359 PMIC supplies Chen-Yu Tsai
2026-03-20  8:43 ` [PATCH 10/13] arm64: dts: mediatek: mt8195-cherry: Add MT6315 " Chen-Yu Tsai
2026-03-20  8:43 ` [PATCH 11/13] arm64: dts: mediatek: mt8195-cherry: Fix VBUS regulator description Chen-Yu Tsai
2026-03-20  8:43 ` [PATCH 12/13] arm64: dts: mediatek: mt8188-geralt: Add MT6359 PMIC supplies Chen-Yu Tsai
2026-03-24  8:08   ` Fei Shao
2026-03-20  8:43 ` [PATCH 13/13] arm64: dts: mediatek: mt8188-geralt: Add little core CPU power supplies Chen-Yu Tsai
2026-03-24  8:09   ` Fei Shao

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=20260320084351.2461060-2-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