Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
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 v2 01/32] pinctrl: mediatek: mt8189: Enable module build support
Date: Fri, 26 Jun 2026 09:31:27 +0800	[thread overview]
Message-ID: <20260626013217.2373808-2-justin.yeh@mediatek.com> (raw)
In-Reply-To: <20260626013217.2373808-1-justin.yeh@mediatek.com>

Add MODULE_LICENSE("GPL") macro and change Kconfig option from
bool to tristate to allow building as a loadable kernel module.

This is required for Android GKI + vendor_dlkm deployments where
vendor-specific drivers must be kept separate from the GKI vmlinux.

Fixes: a3fe1324c3c5 ("pinctrl: mediatek: Add pinctrl driver for mt8189")

Signed-off-by: Justin Yeh <justin.yeh@mediatek.com>
---
 drivers/pinctrl/mediatek/Kconfig          | 2 +-
 drivers/pinctrl/mediatek/pinctrl-mt8189.c | 1 +
 2 files changed, 2 insertions(+), 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
diff --git a/drivers/pinctrl/mediatek/pinctrl-mt8189.c b/drivers/pinctrl/mediatek/pinctrl-mt8189.c
index cd4cdff309a1..67ae7170670c 100644
--- a/drivers/pinctrl/mediatek/pinctrl-mt8189.c
+++ b/drivers/pinctrl/mediatek/pinctrl-mt8189.c
@@ -1696,3 +1696,4 @@ static int __init mt8189_pinctrl_init(void)
 arch_initcall(mt8189_pinctrl_init);
 
 MODULE_DESCRIPTION("MediaTek MT8189 Pinctrl Driver");
+MODULE_LICENSE("GPL");
-- 
2.45.2



  reply	other threads:[~2026-06-26  1:33 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26  1:31 [PATCH v2 00/32] pinctrl: mediatek: Enable module build support for all drivers Justin Yeh
2026-06-26  1:31 ` Justin Yeh [this message]
2026-06-26  1:31 ` [PATCH v2 02/32] pinctrl: mediatek: mt6878: Enable module build support Justin Yeh
2026-06-26  1:31 ` [PATCH v2 03/32] pinctrl: mediatek: mt6893: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 04/32] pinctrl: mediatek: mt7622: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 05/32] pinctrl: mediatek: mt7981: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 06/32] pinctrl: mediatek: mt7986: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 07/32] pinctrl: mediatek: mt7988: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 08/32] pinctrl: mediatek: mt8167: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 09/32] pinctrl: mediatek: mt8173: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 10/32] pinctrl: mediatek: mt8183: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 11/32] pinctrl: mediatek: mt8186: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 12/32] pinctrl: mediatek: mt8188: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 13/32] pinctrl: mediatek: mt8192: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 14/32] pinctrl: mediatek: mt8195: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 15/32] pinctrl: mediatek: mt8196: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 16/32] pinctrl: mediatek: mt8365: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 17/32] pinctrl: mediatek: mt8516: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 18/32] pinctrl: mediatek: mt2701: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 19/32] pinctrl: mediatek: mt7623: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 20/32] pinctrl: mediatek: mt7629: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 21/32] pinctrl: mediatek: mt8135: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 22/32] pinctrl: mediatek: mt8127: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 23/32] pinctrl: mediatek: mt7620: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 24/32] pinctrl: mediatek: mt7621: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 25/32] pinctrl: mediatek: mt76x8: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 26/32] pinctrl: mediatek: rt2880: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 27/32] pinctrl: mediatek: rt305x: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 28/32] pinctrl: mediatek: rt3883: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 29/32] pinctrl: mediatek: mt6397: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 30/32] pinctrl: mediatek: mt2712: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 31/32] pinctrl: mediatek: mt6795: " Justin Yeh
2026-06-26  1:31 ` [PATCH v2 32/32] pinctrl: mediatek: mt6797: " 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=20260626013217.2373808-2-justin.yeh@mediatek.com \
    --to=justin.yeh@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=linusw@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=sean.wang@kernel.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