All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Mirko Jechow" <mirko.jechow@gmx.de>
Cc: linux-hwmon@vger.kernel.org
Subject: Re: [PATCH v3] usb: xhci-pci: Add AMD 600 series to xhci-pci-prom21
Date: Sun, 04 Oct 2026 00:37:14 +0000	[thread overview]
Message-ID: <20261004003714.D51C91F0089B@smtp.kernel.org> (raw)
In-Reply-To: <20261004002731.49927-1-mirko.jechow@gmx.de>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] usb: xhci-pci: missing PM quirk for new Prom21 chips and incomplete refactoring
--

commit 88cfe4d5f35bfe8fa1398a1c64bdb16fc99db18c
Author: Stephen Horvath <linux@stevetech.au>

usb: xhci-pci: Add AMD 600 series to xhci-pci-prom21

This commit adds the device IDs for the AMD 600 series chipsets (which feature
Promontory 21 chips) to the xhci-pci-prom21 driver and documentation. It
ensures they are recognized alongside the 800 series chipsets.

> diff --git a/drivers/usb/host/xhci-pci.h b/drivers/usb/host/xhci-pci.h
> index 11f435f94322a..533efc7db8012 100644
> --- a/drivers/usb/host/xhci-pci.h
> +++ b/drivers/usb/host/xhci-pci.h
> @@ -4,6 +4,9 @@
>  #ifndef XHCI_PCI_H
>  #define XHCI_PCI_H
>  
> +#define PCI_DEVICE_ID_AMD_PROM21_XHCI_43F7	0x43f7
> +#define PCI_DEVICE_ID_AMD_PROM21_XHCI_43F9	0x43f9
> +#define PCI_DEVICE_ID_AMD_PROM21_XHCI_43FA	0x43fa

[Severity: Medium]
In drivers/usb/host/xhci-pci.c:xhci_pci_quirks(), there is an existing quirk
check that applies to one of the Promontory 21 chips:

    if (pdev->vendor == PCI_VENDOR_ID_AMD && pdev->device == 0x43f7)
        xhci->quirks |= XHCI_DEFAULT_PM_RUNTIME_ALLOW;

Should this hardcoded value be refactored to use the newly defined
PCI_DEVICE_ID_AMD_PROM21_XHCI_43F7 macro?

Additionally, since the new Promontory 21 chips (0x43f9, 0x43fa) are identical
silicon to 0x43f7, do they also need to be added to this check?

Without this quirk, runtime PM will not be enabled by default for motherboards
with B665 or A620 chipsets, causing a power regression when initializing the
xHCI controller.

>  #define PCI_DEVICE_ID_AMD_PROM21_XHCI_43FC	0x43fc
>  #define PCI_DEVICE_ID_AMD_PROM21_XHCI_43FD	0x43fd
>

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261004002731.49927-1-mirko.jechow@gmx.de?part=1

  reply	other threads:[~2026-10-04  0:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-04  0:27 [PATCH v3] usb: xhci-pci: Add AMD 600 series to xhci-pci-prom21 Mirko Jechow
2026-10-04  0:37 ` sashiko-bot [this message]
2026-10-04  1:27 ` Stephen Horvath

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=20261004003714.D51C91F0089B@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-hwmon@vger.kernel.org \
    --cc=mirko.jechow@gmx.de \
    --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.