Linux GPIO subsystem development
 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 v4 29/32] pinctrl: mediatek: mt6397: Enable module build support
Date: Fri, 26 Jun 2026 12:00:58 +0800	[thread overview]
Message-ID: <20260626040112.2436185-30-justin.yeh@mediatek.com> (raw)
In-Reply-To: <20260626040112.2436185-1-justin.yeh@mediatek.com>

Add MODULE_LICENSE("GPL v2") 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: fc59e66c4284 ("pinctrl: mediatek: Add Pinctrl/GPIO driver for mt6397.")
Signed-off-by: Justin Yeh <justin.yeh@mediatek.com>
---
 drivers/pinctrl/mediatek/Kconfig          | 2 +-
 drivers/pinctrl/mediatek/pinctrl-mt6397.c | 3 +++
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/drivers/pinctrl/mediatek/Kconfig b/drivers/pinctrl/mediatek/Kconfig
index eb4bb7408f8d..a73febf867ec 100644
--- a/drivers/pinctrl/mediatek/Kconfig
+++ b/drivers/pinctrl/mediatek/Kconfig
@@ -308,7 +308,7 @@ config PINCTRL_MT8516
 
 # For PMIC
 config PINCTRL_MT6397
-	bool "MediaTek MT6397 pin control"
+	tristate "MediaTek MT6397 pin control"
 	depends on MFD_MT6397 || COMPILE_TEST
 	depends on OF
 	default MFD_MT6397
diff --git a/drivers/pinctrl/mediatek/pinctrl-mt6397.c b/drivers/pinctrl/mediatek/pinctrl-mt6397.c
index 03d0f65d7bcc..9ff479e7459a 100644
--- a/drivers/pinctrl/mediatek/pinctrl-mt6397.c
+++ b/drivers/pinctrl/mediatek/pinctrl-mt6397.c
@@ -59,3 +59,6 @@ static struct platform_driver mtk_pinctrl_driver = {
 };
 
 builtin_platform_driver(mtk_pinctrl_driver);
+
+MODULE_DESCRIPTION("MediaTek MT6397 Pinctrl Driver");
+MODULE_LICENSE("GPL v2");
-- 
2.45.2


  parent reply	other threads:[~2026-06-26  4:01 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-26  4:00 [PATCH v4 00/32] pinctrl: mediatek: Enable module build support for all drivers Justin Yeh
2026-06-26  4:00 ` [PATCH v4 01/32] pinctrl: mediatek: mt8189: Enable module build support Justin Yeh
2026-06-26  4:00 ` [PATCH v4 02/32] pinctrl: mediatek: mt6878: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 03/32] pinctrl: mediatek: mt6893: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 04/32] pinctrl: mediatek: mt7622: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 05/32] pinctrl: mediatek: mt7981: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 06/32] pinctrl: mediatek: mt7986: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 07/32] pinctrl: mediatek: mt7988: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 08/32] pinctrl: mediatek: mt8167: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 09/32] pinctrl: mediatek: mt8173: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 10/32] pinctrl: mediatek: mt8183: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 11/32] pinctrl: mediatek: mt8186: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 12/32] pinctrl: mediatek: mt8188: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 13/32] pinctrl: mediatek: mt8192: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 14/32] pinctrl: mediatek: mt8195: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 15/32] pinctrl: mediatek: mt8196: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 16/32] pinctrl: mediatek: mt8365: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 17/32] pinctrl: mediatek: mt8516: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 18/32] pinctrl: mediatek: mt2701: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 19/32] pinctrl: mediatek: mt7623: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 20/32] pinctrl: mediatek: mt7629: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 21/32] pinctrl: mediatek: mt8135: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 22/32] pinctrl: mediatek: mt8127: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 23/32] pinctrl: mediatek: mt7620: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 24/32] pinctrl: mediatek: mt7621: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 25/32] pinctrl: mediatek: mt76x8: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 26/32] pinctrl: mediatek: rt2880: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 27/32] pinctrl: mediatek: rt305x: " Justin Yeh
2026-06-26  4:00 ` [PATCH v4 28/32] pinctrl: mediatek: rt3883: " Justin Yeh
2026-06-26  4:00 ` Justin Yeh [this message]
2026-06-26  4:00 ` [PATCH v4 30/32] pinctrl: mediatek: mt2712: " Justin Yeh
2026-06-26  4:01 ` [PATCH v4 31/32] pinctrl: mediatek: mt6795: " Justin Yeh
2026-06-26  4:01 ` [PATCH v4 32/32] pinctrl: mediatek: mt6797: " Justin Yeh
2026-06-26 10:04 ` [PATCH v4 00/32] pinctrl: mediatek: Enable module build support for all drivers AngeloGioacchino Del Regno
2026-06-26 13:17 ` Linus Walleij

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=20260626040112.2436185-30-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