From: Zhipeng.wang_1@oss.nxp.com
To: robh@kernel.org, saravanak@kernel.org, ulfh@kernel.org,
Frank.Li@nxp.com, s.hauer@pengutronix.de
Cc: kernel@pengutronix.de, festevam@gmail.com, peng.fan@nxp.com,
aisheng.dong@nxp.com, jindong.yue@nxp.com, xuegang.liu@nxp.com,
devicetree@vger.kernel.org, linux-pm@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org
Subject: [PATCH v4 0/3] pmdomain: imx: build the SCU power domain driver as a module
Date: Wed, 22 Jul 2026 17:25:19 +0900 [thread overview]
Message-ID: <20260722082522.3747962-1-Zhipeng.wang_1@oss.nxp.com> (raw)
From: Zhipeng Wang <zhipeng.wang_1@nxp.com>
This series makes the i.MX SCU power domain driver buildable as a
loadable module, which is required for Android devices using the
Generic Kernel Image (GKI) where SoC-specific drivers must be modules.
Patch 1 exports of_stdout (which the driver references to find the
console's power domain) from the OF core with EXPORT_SYMBOL_GPL().
Patch 2 converts CONFIG_IMX_SCU_PD from bool to tristate and adds
MODULE_DEVICE_TABLE() for autoloading. subsys_initcall() is used so
that when built-in the provider probes before its consumers (e.g. the
SCU clock driver at device_initcall level). No module_exit() is
provided since the provider cannot be safely removed at runtime.
Patch 3 adds MODULE_SOFTDEP("pre: imx_scu_pd") to the i.MX8QXP clock
driver so that modprobe loads the power domain module first when both
are built as modules.
Because of the cross-subsystem dependency (patches touch drivers/of,
drivers/pmdomain, and drivers/clk), I would suggest taking the whole
series through one tree.
Changes in v4:
- Add patch 3: MODULE_SOFTDEP in clk-imx8qxp to guarantee module load
order when both drivers are modules. (Sashiko bot)
Changes in v3:
- Use subsys_initcall() instead of module_init() to fix probe ordering
between the power domain provider and the SCU clock consumer when
both are built-in. (Sashiko bot)
Changes in v2:
- Drop module_platform_driver() which provides module_exit() and could
lead to use-after-free on module unload. Use module_init() only, so
the module cannot be unloaded. (Sashiko bot)
Zhipeng Wang (3):
of: export of_stdout symbol
pmdomain: imx: scu-pd: allow building as a module
clk: imx: imx8qxp: add soft dependency on SCU power domain driver
drivers/clk/imx/clk-imx8qxp.c | 1 +
drivers/of/base.c | 1 +
drivers/pmdomain/imx/Kconfig | 2 +-
drivers/pmdomain/imx/scu-pd.c | 8 +++++++-
4 files changed, 10 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2026-07-22 8:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-22 8:25 Zhipeng.wang_1 [this message]
2026-07-22 8:25 ` [PATCH v4 1/3] of: export of_stdout symbol Zhipeng.wang_1
2026-07-22 13:20 ` Rob Herring (Arm)
2026-07-22 8:25 ` [PATCH v4 2/3] pmdomain: imx: scu-pd: allow building as a module Zhipeng.wang_1
2026-07-22 8:25 ` [PATCH v4 3/3] clk: imx: imx8qxp: add soft dependency on SCU power domain driver Zhipeng.wang_1
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=20260722082522.3747962-1-Zhipeng.wang_1@oss.nxp.com \
--to=zhipeng.wang_1@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=jindong.yue@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=saravanak@kernel.org \
--cc=ulfh@kernel.org \
--cc=xuegang.liu@nxp.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®