From: Justin Yeh <justin.yeh@mediatek.com>
To: Liam Girdwood <lgirdwood@gmail.com>,
Mark Brown <broonie@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>
Cc: <Project_Global_Chrome_Upstream_Group@mediatek.com>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>,
Justin Yeh <justin.yeh@mediatek.com>
Subject: [PATCH 2/2] soc: mediatek: mtk-regulator-coupler: Allow building as a module
Date: Thu, 3 Sep 2026 14:20:47 +0800 [thread overview]
Message-ID: <20260903062056.1024263-3-justin.yeh@mediatek.com> (raw)
In-Reply-To: <20260903062056.1024263-1-justin.yeh@mediatek.com>
MTK_REGULATOR_COUPLER is a bool whose prompt is only visible when
COMPILE_TEST is set, so on real MediaTek configurations the symbol has
no prompt at all and is forced to its default: it can only ever be
built in.
Turn it into a visible tristate so that the coupler can also be built
as a loadable module, which is what kernels shipping most of their
drivers as modules need. The "default ARCH_MEDIATEK" is kept, so
existing configurations keep building it in.
While at it, add the help text that the now user-visible prompt was
missing.
Signed-off-by: Justin Yeh <justin.yeh@mediatek.com>
---
drivers/soc/mediatek/Kconfig | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/soc/mediatek/Kconfig b/drivers/soc/mediatek/Kconfig
index d7293977f06e..4a2f2bccc213 100644
--- a/drivers/soc/mediatek/Kconfig
+++ b/drivers/soc/mediatek/Kconfig
@@ -56,9 +56,13 @@ config MTK_PMIC_WRAP
hardware to connect the PMIC.
config MTK_REGULATOR_COUPLER
- bool "MediaTek SoC Regulator Coupler" if COMPILE_TEST
+ tristate "MediaTek SoC Regulator Coupler"
default ARCH_MEDIATEK
depends on REGULATOR
+ help
+ Say yes here to add support for the MediaTek regulator coupler,
+ which keeps the GPU supply and its coupled GPU SRAM supply
+ voltage-balanced on the MediaTek SoCs that need it.
config MTK_MMSYS
tristate "MediaTek MMSYS Support"
--
2.45.2
next prev parent reply other threads:[~2026-09-03 6:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-03 6:20 [PATCH 0/2] Allow mtk-regulator-coupler to be built " Justin Yeh
2026-09-03 6:20 ` [PATCH 1/2] regulator: core: Export helpers used by regulator couplers Justin Yeh
2026-09-03 23:07 ` Mark Brown
2026-09-03 6:20 ` Justin Yeh [this message]
2026-09-18 0:37 ` [PATCH 0/2] Allow mtk-regulator-coupler to be built as a module Justin Yeh
2026-09-18 9:26 ` Mark Brown
2026-09-25 17:45 ` (subset) " Mark Brown
2026-09-25 22:15 ` Mark Brown
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=20260903062056.1024263-3-justin.yeh@mediatek.com \
--to=justin.yeh@mediatek.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--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
all inboxes | Powered by JetHome®