All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mirko Jechow <mirko.jechow@gmx.de>
To: linux@stevetech.au
Cc: mathias.nyman@intel.com, gregkh@linuxfoundation.org,
	Shyam-sundar.S-k@amd.com, hurryman2212@gmail.com,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] usb: xhci-pci: Add AMD 600 series to xhci-pci-prom21
Date: Sat, 5 Sep 2026 03:35:32 +0200	[thread overview]
Message-ID: <6e81b0fa-de68-4a83-a152-fe26ea7cc359@gmx.de> (raw)

Tested on an MSI MPG X670E Carbon WiFi (Ryzen 9 7950X3D). The board 
exposes two 600 series chipset xHCI functions, 1022:43f7 at 13:00.0 and 
15:00.0 -- X670E is built from two Promontory 21 dies.

Without the patch neither function creates an auxiliary device, so 
prom21-xhci has nothing to bind to and the sensor is unavailable. With 
it applied to 7.2.3, both functions bind xhci-pci-prom21, both auxiliary 
devices appear, and both dies report:

   prom21_xhci-pci-1300  temp1: +57.4 C
   prom21_xhci-pci-1500  temp1: +62.8 C

k10temp Tctl read +58.0 C at the same moment, so the conversion derived 
on 800 series silicon looks right here too.

USB is unaffected: the devices behind both controllers enumerate 
normally and the log shows no new xHCI errors after they moved to the 
glue driver.

Tested-by: Mirko Jechow <mirko.jechow@gmx.de>

             reply	other threads:[~2026-09-05  1:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-05  1:35 Mirko Jechow [this message]
  -- strict thread matches above, loose matches on Subject: below --
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

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=6e81b0fa-de68-4a83-a152-fe26ea7cc359@gmx.de \
    --to=mirko.jechow@gmx.de \
    --cc=Shyam-sundar.S-k@amd.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hurryman2212@gmail.com \
    --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.