From: Jihong Min <hurryman2212@gmail.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Stephen Horvath <linux@stevetech.au>,
Mathias Nyman <mathias.nyman@intel.com>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Shyam Sundar S K <Shyam-sundar.S-k@amd.com>
Subject: Re: [PATCH v2] usb: xhci-pci: Add AMD 600 series to xhci-pci-prom21
Date: Sun, 23 Aug 2026 22:12:14 +0900 [thread overview]
Message-ID: <496d1dee-e34d-4b47-8cd0-829d695e8147@gmail.com> (raw)
In-Reply-To: <2026082304-ebook-expel-d0b7@gregkh>
Hi,
On 8/23/26 21:25, Greg Kroah-Hartman wrote:
> On Sun, Aug 23, 2026 at 09:23:42PM +0900, Jihong Min wrote:
>> Hi,
>>
>> On 8/20/26 21:59, Stephen Horvath wrote:
>>> It seems the xhci-pci-prom21 module only has IDs for the 800 series
>>> chipsets. However, the 600 series chipsets also have Promontory 21
>>> chips, so we should add their IDs to the list as well.
>>>
>>> I have tested this on my X670 board featuring DID `0x43f7`.
>>>
>>> `1022:43f7` also appears on the PCI ID database
>>> (https://pci-ids.ucw.cz/read/PC/1022/43f7).
>>> Device IDs `0x43f9` (B665) & `0x43fa` (A620) were suggested by Shyam.
>>
>> It would be nice to update all the newly added device IDs to the kernel
>> documentation as well.
>
> Documentation where exactly?
Initially, `Documentation/hwmon/prom21-xhci.rst` has added the following
line:
PCI IDs: 1022:43fc, 1022:43fd
It would be more appropriate to add these new IDs into the same line, or
just drop the deprecated document line.
>
> thanks,
>
> greg k-h
Sincerely,
Jihong Min
next prev parent reply other threads:[~2026-08-23 13:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-20 12:59 [PATCH v2] usb: xhci-pci: Add AMD 600 series to xhci-pci-prom21 Stephen Horvath
2026-08-23 12:23 ` Jihong Min
2026-08-23 12:25 ` Greg Kroah-Hartman
2026-08-23 13:12 ` Jihong Min [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-09-05 1:35 Mirko Jechow
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=496d1dee-e34d-4b47-8cd0-829d695e8147@gmail.com \
--to=hurryman2212@gmail.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@stevetech.au \
--cc=mathias.nyman@intel.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.