From: Kean Ren <rh_king@163.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Mathias Nyman <mathias.nyman@intel.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Alan Stern <stern@rowland.harvard.edu>,
Griffin Kroah-Hartman <griffin@kroah.com>,
Kuen-Han Tsai <khtsai@google.com>, Kees Cook <kees@kernel.org>,
Nikhil Solanke <nikhilsolanke5@gmail.com>,
Thorsten Blum <blum@kernel.org>, Kean Ren <rh_king@163.com>
Subject: [PATCH 0/2] usb: fix ASM3242 reporting SuperSpeed for a Gen 2x2 link
Date: Sun, 20 Sep 2026 10:52:41 +0800 [thread overview]
Message-ID: <20260920025308.2358862-1-rh_king@163.com> (raw)
The ASMedia ASM3242 (1b21:3242) reports the SuperSpeed speed ID together
with two active lanes for a link that is actually running at USB 3.2
Gen 2x2 after a cold boot. Linux therefore classifies the device as
USB 3.0 SuperSpeed and reports 5000M/x2, although the measured
throughput is 1.49-1.60 GB/s (11.9-12.8 Gbps), which is above the
physical ceiling of a 10 Gbps link (~1.25 GB/s).
Patch 1 is a generic correctness fix: get_port_ssp_rate() currently
cannot recognise USB 3.2 Gen 1x2 at all, because it rejects any
matching sublink entry whose link protocol is not SuperSpeedPlus
before it looks at the number of active lanes.
Patch 2 adds a controller quirk so that this hardware reports the
Gen 2x2 speed ID. The raw extended port status, the measured
throughput and the list of resets that do and do not restore the
correct report are all in the patch description.
The wrong report is 100% reproducible after every reboot and is only
cleared by an S3 suspend/resume. Raw data (lsusb -v, lspci -vv, sysfs
and BOS dumps, kernel log) is available on request.
Kean Ren (2):
usb: core: hub: recognise two-lane SuperSpeed sublinks as Gen 1x2
xhci: fix ASM3242 port speed report for Gen 2x2 links after cold boot
drivers/usb/core/hub.c | 30 ++++++++++++++++++++----------
drivers/usb/host/xhci-hub.c | 17 +++++++++++++++--
drivers/usb/host/xhci-pci.c | 4 ++++
drivers/usb/host/xhci.h | 1 +
4 files changed, 40 insertions(+), 12 deletions(-)
next reply other threads:[~2026-09-20 2:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-20 2:52 Kean Ren [this message]
2026-09-20 2:52 ` [PATCH 1/2] usb: core: hub: recognise two-lane SuperSpeed sublinks as Gen 1x2 Kean Ren
2026-09-20 2:52 ` [PATCH 2/2] xhci: fix ASM3242 port speed report for Gen 2x2 links after cold boot Kean Ren
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=20260920025308.2358862-1-rh_king@163.com \
--to=rh_king@163.com \
--cc=blum@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=griffin@kroah.com \
--cc=kees@kernel.org \
--cc=khtsai@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=nikhilsolanke5@gmail.com \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®