Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Yeh <justin.yeh@mediatek.com>
To: Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>
Cc: <Project_Global_Chrome_Upstream_Group@mediatek.com>,
	<linux-kernel@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-mediatek@lists.infradead.org>,
	Justin Yeh <justin.yeh@mediatek.com>
Subject: [PATCH 1/2] soc: mediatek: Allow MTK_INFRACFG to be built as module
Date: Fri, 29 May 2026 18:16:02 +0800	[thread overview]
Message-ID: <20260529101613.55697-2-justin.yeh@mediatek.com> (raw)
In-Reply-To: <20260529101613.55697-1-justin.yeh@mediatek.com>

Change MTK_INFRACFG from bool to tristate to support building it as
a loadable kernel module (.ko) instead of being built into the kernel.
This is required for DDK (Driver Development Kit) module build, where
mtk-infracfg needs to be loaded dynamically along with other SoC
infrastructure modules.

Signed-off-by: Justin Yeh <justin.yeh@mediatek.com>
---
 drivers/soc/mediatek/Kconfig | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/drivers/soc/mediatek/Kconfig b/drivers/soc/mediatek/Kconfig
index d7293977f06e..d28b0817ce51 100644
--- a/drivers/soc/mediatek/Kconfig
+++ b/drivers/soc/mediatek/Kconfig
@@ -38,7 +38,7 @@ config MTK_DVFSRC
 	  best achievable performance-per-watt.
 
 config MTK_INFRACFG
-	bool "MediaTek INFRACFG Support"
+	tristate "MediaTek INFRACFG Support"
 	select REGMAP
 	help
 	  Say yes here to add support for the MediaTek INFRACFG controller. The
-- 
2.45.2



  reply	other threads:[~2026-05-29 10:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-29 10:16 [PATCH 0/2] soc: mediatek: Make mtk-infracfg modular Justin Yeh
2026-05-29 10:16 ` Justin Yeh [this message]
2026-05-29 10:16 ` [PATCH 2/2] soc: mediatek: mtk-infracfg: Export symbols for DDK modules Justin Yeh
2026-06-23  8:06   ` AngeloGioacchino Del Regno

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=20260529101613.55697-2-justin.yeh@mediatek.com \
    --to=justin.yeh@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.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