All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Fan <peng.fan@oss.nxp.com>
To: Zhipeng.wang_1@oss.nxp.com
Cc: robh@kernel.org, saravanak@kernel.org, ulfh@kernel.org,
	Frank.Li@nxp.com, s.hauer@pengutronix.de, 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: Re: [PATCH v5 2/3] pmdomain: imx: scu-pd: allow building as a module
Date: Mon, 27 Jul 2026 15:45:56 +0800	[thread overview]
Message-ID: <amcMtNFqcfb40Oe+@shlinux89> (raw)
In-Reply-To: <20260723020524.1886806-3-Zhipeng.wang_1@oss.nxp.com>

On Thu, Jul 23, 2026 at 11:05:23AM +0900, Zhipeng.wang_1@oss.nxp.com wrote:
>From: Zhipeng Wang <zhipeng.wang_1@nxp.com>
>
>Convert CONFIG_IMX_SCU_PD from bool to tristate to allow building as a
>loadable module. This is needed on Android devices using the Generic
>Kernel Image (GKI), where SoC-specific drivers must be built as modules
>rather than built into the core kernel image.
>
>For i.MX8Q devices running Android with a GKI kernel, the SCU power
>domain driver must be loadable. Without tristate support, power domains
>cannot be properly initialized, preventing these systems from
>functioning under GKI.
>
>Use subsys_initcall() so that when built-in the power domain provider
>probes before its consumers (e.g. the SCU clock driver at
>device_initcall level), fixing "failed to attached the power domain"
>warnings at boot. When built as a module, subsys_initcall() is
>equivalent to module_init(). No module_exit() is provided because the
>SCU power domain provider is a system-level resource that cannot be
>safely removed at runtime.
>
>Add MODULE_DEVICE_TABLE() for OF-based module autoloading.
>
>Signed-off-by: Zhipeng Wang <zhipeng.wang_1@nxp.com>

Reviewed-by: Peng Fan <peng.fan@nxp.com>

  reply	other threads:[~2026-07-27  7:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-23  2:05 [PATCH v5 0/3] pmdomain: imx: build the SCU power domain driver as a module Zhipeng.wang_1
2026-07-23  2:05 ` [PATCH v5 1/3] of: export of_stdout symbol Zhipeng.wang_1
2026-07-23  2:05 ` [PATCH v5 2/3] pmdomain: imx: scu-pd: allow building as a module Zhipeng.wang_1
2026-07-27  7:45   ` Peng Fan [this message]
2026-07-23  2:05 ` [PATCH v5 3/3] clk: imx: imx8qxp: add soft dependency on SCU power domain driver Zhipeng.wang_1
2026-07-23  2:20   ` sashiko-bot
2026-07-23  4:38     ` Zhipeng Wang (OSS)
2026-07-23 16:03   ` Brian Masney
2026-07-27  7:46   ` Peng Fan
2026-07-27 10:00 ` [PATCH v5 0/3] pmdomain: imx: build the SCU power domain driver as a module Ulf Hansson

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=amcMtNFqcfb40Oe+@shlinux89 \
    --to=peng.fan@oss.nxp.com \
    --cc=Frank.Li@nxp.com \
    --cc=Zhipeng.wang_1@oss.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.