From: sashiko-bot@kernel.org
To: "Geert Uytterhoeven" <geert+renesas@glider.be>
Cc: linux-pci@vger.kernel.org, linux-gpio@vger.kernel.org
Subject: Re: [PATCH] PCI/pwrctrl/gpio: Correct GPIO_TC9563 / PCI_PWRCTRL_TC9563 dependency
Date: Tue, 20 Oct 2026 15:11:13 +0000 [thread overview]
Message-ID: <sashiko-outbox-179228@kernel.org> (raw)
In-Reply-To: <889ae6695b19ce57ca4b17526c69b48c9414f5ae.1792508601.git.geert+renesas@glider.be>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] PCI/pwrctrl: missing select AUXILIARY_BUS in PCI_PWRCTRL_TC9563
--
commit a7730129e4c039c8e8c890c4f31a553b4c62308d
Author: Geert Uytterhoeven <geert+renesas@glider.be>
PCI/pwrctrl/gpio: Correct GPIO_TC9563 / PCI_PWRCTRL_TC9563 dependency
This commit reverses the Kconfig dependency between GPIO_TC9563 and
PCI_PWRCTRL_TC9563 so that GPIO_TC9563 depends on PCI_PWRCTRL_TC9563 ||
COMPILE_TEST instead of PCI_PWRCTRL_TC9563 depending on GPIO_TC9563.
> diff --git a/drivers/pci/pwrctrl/Kconfig b/drivers/pci/pwrctrl/Kconfig
> index 38aab596aa04b..1952ab4f29b69 100644
> --- a/drivers/pci/pwrctrl/Kconfig
> +++ b/drivers/pci/pwrctrl/Kconfig
> @@ -29,7 +29,6 @@ config PCI_PWRCTRL_TC9563
> select PCI_PWRCTRL
> default m if ARCH_QCOM
> depends on I2C
> - depends on GPIO_TC9563
> select REGMAP_I2C
> help
> Say Y here to enable the PCI Power Control driver of TC9563 PCIe
[Severity: Low]
Does PCI_PWRCTRL_TC9563 also need to select AUXILIARY_BUS when dropping the
dependency on GPIO_TC9563?
Previously, depending on GPIO_TC9563 transitively selected AUXILIARY_BUS.
Without that dependency, if PCI_PWRCTRL_TC9563 is enabled with GPIO_TC9563=n
and nothing else selects AUXILIARY_BUS, drivers/base/auxiliary.o is not
built:
drivers/base/Makefile:
obj-$(CONFIG_AUXILIARY_BUS) += auxiliary.o
Meanwhile, tc9563_pwrctrl_adev_add() in
drivers/pci/pwrctrl/pci-pwrctrl-tc9563.c unconditionally calls
auxiliary_device_init() and auxiliary_device_add():
drivers/pci/pwrctrl/pci-pwrctrl-tc9563.c:tc9563_pwrctrl_adev_add() {
...
ret = auxiliary_device_init(adev);
if (ret) {
ida_free(&tc9563_pwrctrl_ida, id);
of_node_put(adev->dev.of_node);
kfree(adev);
return ret;
}
ret = auxiliary_device_add(adev);
...
}
Can this cause undefined reference link errors for auxiliary_device_init and
__auxiliary_device_add when CONFIG_AUXILIARY_BUS is not enabled?
--
Sashiko AI review · https://sashiko.dev/#/patchset/889ae6695b19ce57ca4b17526c69b48c9414f5ae.1792508601.git.geert+renesas@glider.be?part=1
prev parent reply other threads:[~2026-10-20 15:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-20 15:03 [PATCH] PCI/pwrctrl/gpio: Correct GPIO_TC9563 / PCI_PWRCTRL_TC9563 dependency Geert Uytterhoeven
2026-10-20 15:11 ` sashiko-bot [this message]
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=sashiko-outbox-179228@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=geert+renesas@glider.be \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.