From: Arnd Bergmann <arnd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Tomer Maimon <tmaimon77@gmail.com>
Cc: "Arnd Bergmann" <arnd@arndb.de>, "Yixun Lan" <dlan@gentoo.org>,
"Sven Peter" <sven@kernel.org>,
"Inochi Amaoto" <inochiama@outlook.com>,
"Andrea della Porta" <andrea.porta@suse.com>,
"Robert Marko" <robert.marko@sartura.hr>,
"Théo Lebrun" <theo.lebrun@bootlin.com>,
"Nikita Shubin" <nikita.shubin@maquefel.me>,
"Andreas Kemnade" <andreas@kemnade.info>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH] clk: npcm: select CONFIG_AUXILIARY_BUS
Date: Thu, 7 Aug 2025 09:22:37 +0200 [thread overview]
Message-ID: <20250807072241.4190376-1-arnd@kernel.org> (raw)
From: Arnd Bergmann <arnd@arndb.de>
There are very rare randconfig builds that turn on this driver but
don't already select CONFIG_AUXILIARY_BUS from another driver, and
this results in a build failure:
arm-linux-gnueabi-ld: drivers/clk/clk-npcm8xx.o: in function `npcm8xx_clock_driver_init':
clk-npcm8xx.c:(.init.text+0x18): undefined reference to `__auxiliary_driver_register'
Select the bus here, as all other clk drivers using it do.
Fixes: e0b255df027e ("clk: npcm8xx: add clock controller")
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
---
drivers/clk/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/clk/Kconfig b/drivers/clk/Kconfig
index 4d56475f94fc..b1425aed6593 100644
--- a/drivers/clk/Kconfig
+++ b/drivers/clk/Kconfig
@@ -364,6 +364,7 @@ config COMMON_CLK_LOCHNAGAR
config COMMON_CLK_NPCM8XX
tristate "Clock driver for the NPCM8XX SoC Family"
depends on ARCH_NPCM || COMPILE_TEST
+ select AUXILIARY_BUS
help
This driver supports the clocks on the Nuvoton BMC NPCM8XX SoC Family,
all the clocks are initialized by the bootloader, so this driver
--
2.39.5
next reply other threads:[~2025-08-07 7:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-07 7:22 Arnd Bergmann [this message]
2025-08-14 21:41 ` Stephen Boyd
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=20250807072241.4190376-1-arnd@kernel.org \
--to=arnd@kernel.org \
--cc=andrea.porta@suse.com \
--cc=andreas@kemnade.info \
--cc=arnd@arndb.de \
--cc=dlan@gentoo.org \
--cc=inochiama@outlook.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=nikita.shubin@maquefel.me \
--cc=robert.marko@sartura.hr \
--cc=sboyd@kernel.org \
--cc=sven@kernel.org \
--cc=theo.lebrun@bootlin.com \
--cc=tmaimon77@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
all inboxes | Powered by JetHome®