Linux Hardware Monitor development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Jihong Min" <hurryman2212@gmail.com>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH] usb: xhci: add AMD PROM21 xHCI hwmon support for temperature monitoring
Date: Wed, 06 May 2026 04:07:35 +0000	[thread overview]
Message-ID: <20260506040736.5081DC2BCB8@smtp.kernel.org> (raw)
In-Reply-To: <20260506032939.92351-1-hurryman2212@gmail.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] Potential linker error when USB_XHCI_PCI is built-in and HWMON is a module.
--

commit 66c564d56813f3e58d95a6491735b26bfb5eb91f
Author: Jihong Min <hurryman2212@gmail.com>

usb: xhci: add AMD PROM21 xHCI hwmon support for temperature monitoring

This patch adds hwmon temperature monitoring for AMD PROM21 xHCI controllers.
The hwmon code is built as an extension to the xHCI PCI driver and
initialized during the device probe path.

> diff --git a/drivers/usb/host/Kconfig b/drivers/usb/host/Kconfig
> index 0a277a07cf706..da41ebc272b0f 100644
> --- a/drivers/usb/host/Kconfig
> +++ b/drivers/usb/host/Kconfig
> @@ -42,6 +42,16 @@ config USB_XHCI_PCI
>  	depends on USB_PCI
>  	default y
>  
> +config USB_XHCI_PCI_PROM21_HWMON
> +	bool "AMD PROM21 xHCI temperature sensor support"
> +	depends on USB_XHCI_PCI
> +	depends on HWMON

Can this cause a linker error if CONFIG_USB_XHCI_PCI is built-in (y) and
CONFIG_HWMON is built as a module (m)?

Since USB_XHCI_PCI_PROM21_HWMON is a bool, if its dependencies evaluate to a
module, it can still be selected as built-in (y). This would compile
xhci-prom21-hwmon.c directly into vmlinux, but the code references
devm_hwmon_device_register_with_info(), which would be exported by the
dynamically loaded hwmon module, leading to an undefined reference.

Would it be safer to restrict the dependency using something like
depends on HWMON=y || HWMON=USB_XHCI_PCI?

[ ... ]

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260506032939.92351-1-hurryman2212@gmail.com?part=1

  reply	other threads:[~2026-05-06  4:07 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-06  3:29 [PATCH] usb: xhci: add AMD PROM21 xHCI hwmon support for temperature monitoring Jihong Min
2026-05-06  4:07 ` sashiko-bot [this message]
2026-05-06 13:37 ` Mathias Nyman
2026-05-06 14:26   ` Guenter Roeck
2026-05-06 20:28     ` Jihong Min
2026-05-06 20:40 ` [PATCH v2 0/2] AMD PROM21 xHCI temperature hwmon support Jihong Min
2026-05-06 20:40   ` [PATCH v2 1/2] usb: xhci-pci: add generic auxiliary device interface Jihong Min
2026-05-06 20:53     ` Mario Limonciello
2026-05-06 21:09       ` Jihong Min
2026-05-06 21:15     ` Michal Pecio
2026-05-06 21:42       ` Jihong Min
2026-05-06 20:40   ` [PATCH v2 2/2] hwmon: add initial support for AMD PROM21 xHCI temperature sensor Jihong Min
2026-05-06 21:33     ` Michal Pecio
2026-05-06 21:36       ` Mario Limonciello
2026-05-07  9:08         ` Michal Pecio
2026-05-07 13:24           ` Mario Limonciello
2026-05-06 22:41       ` Jihong Min
2026-05-07  8:51         ` Michal Pecio
2026-05-06 22:17     ` Randy Dunlap
2026-05-06 22:52       ` Jihong Min
2026-05-07  3:29         ` Jihong Min

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=20260506040736.5081DC2BCB8@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=hurryman2212@gmail.com \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=sashiko@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox