From: Justin Yeh <justin.yeh@mediatek•com>
To: Sean Wang <sean.wang@kernel•org>,
Linus Walleij <linusw@kernel•org>,
Matthias Brugger <matthias.bgg@gmail•com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora•com>
Cc: <Project_Global_Chrome_Upstream_Group@mediatek•com>,
<linux-mediatek@lists•infradead.org>,
<linux-gpio@vger•kernel.org>, <linux-kernel@vger•kernel.org>,
<linux-arm-kernel@lists•infradead.org>,
Justin Yeh <justin.yeh@mediatek•com>
Subject: [PATCH 1/2] pinctrl: mediatek: Restore PINCTRL_MT8189 to tristate
Date: Fri, 29 May 2026 18:02:41 +0800 [thread overview]
Message-ID: <20260529100308.51271-2-justin.yeh@mediatek.com> (raw)
In-Reply-To: <20260529100308.51271-1-justin.yeh@mediatek.com>
Under the GKI + vendor_dlkm model, vendor-specific pinctrl cannot be
built into the GKI vmlinux. Upstream's recent switch of PINCTRL_MT8189
to bool prevents building as a loadable module, which breaks DDK module
usage. Restore tristate so MT8189 pinctrl can be packaged as a kernel
module in vendor_dlkm.
Signed-off-by: Justin Yeh <justin.yeh@mediatek•com>
---
drivers/pinctrl/mediatek/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/mediatek/Kconfig b/drivers/pinctrl/mediatek/Kconfig
index 4819617d9368..a75434e7e989 100644
--- a/drivers/pinctrl/mediatek/Kconfig
+++ b/drivers/pinctrl/mediatek/Kconfig
@@ -270,7 +270,7 @@ config PINCTRL_MT8188
map specific eint which doesn't have real gpio pin.
config PINCTRL_MT8189
- bool "MediaTek MT8189 pin control"
+ tristate "MediaTek MT8189 pin control"
depends on OF
depends on ARM64 || COMPILE_TEST
default ARM64 && ARCH_MEDIATEK
--
2.45.2
next prev parent reply other threads:[~2026-05-29 10:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-29 10:02 [PATCH 0/2] pinctrl: mediatek: Enable MT8189 as loadable module Justin Yeh
2026-05-29 10:02 ` Justin Yeh [this message]
2026-05-29 10:02 ` [PATCH 2/2] pinctrl: mediatek: mt8189: Add MODULE_LICENSE declaration Justin Yeh
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=20260529100308.51271-2-justin.yeh@mediatek.com \
--to=justin.yeh@mediatek$(echo .)com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek$(echo .)com \
--cc=angelogioacchino.delregno@collabora$(echo .)com \
--cc=linusw@kernel$(echo .)org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-gpio@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-mediatek@lists$(echo .)infradead.org \
--cc=matthias.bgg@gmail$(echo .)com \
--cc=sean.wang@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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