From: Arun Iyengar via B4 Relay <devnull+aiyengar1990.gmail.com@kernel.org>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Mathias Nyman <mathias.nyman@intel.com>,
Chen-Yu Tsai <wenst@chromium.org>, Rob Herring <robh@kernel.org>,
Arun Iyengar <aiyengar1990@gmail.com>
Subject: [PATCH v5 0/2] usb: core: Pair ports of different host controllers through their connector
Date: Wed, 18 Nov 2026 04:34:57 +0000 [thread overview]
Message-ID: <20261118-usb-port-pairing-v5-0-5f1a26789270@gmail.com> (raw)
On the RK3588, the USB 2.0 lines of the USB 3.0 host 2 connector go to
a separate EHCI, so the USB core pairs its SuperSpeed port with the
wrong USB 2.0 port, and a USB 3 device present at boot stays at 480 Mb/s.
Patch 1 pairs the ports through their usb-connector. Patch 2 resets the
USB 2.0 port of such a device once, so that it retries SuperSpeed. The
Orange Pi 5 DT follows separately and needs Chen-Yu Tsai's usb-hcd
binding [1].
Tested on an Orange Pi 5 (7.3-based kernel): a USB 3 disk moved to
5 Gb/s in 3/3 boots, 6/6 xHCI rebinds and 2/2 runtime-suspended resets;
a device that stays at high speed kept its driver and a running read.
Not tested with an external USB 3 hub.
Developed with Claude (Anthropic), which wrote the code and the commit
messages. I reviewed every change.
[1] https://lore.kernel.org/all/20261014082037.1774672-2-wenst@chromium.org/
---
Changes in v5 (all from Sashiko):
- Patch 1: look up connect_type by the controller port number; don't hold
back a port without a matching peer; connector_peer is not a bitfield
- Patch 2: reset through usb_reset_device(); keep the device if the
SuperSpeed port can't be read or is connected; hold its lock until the
USB 2.0 device is gone
- Link to v4: https://patch.msgid.link/20261115-usb-port-pairing-v4-0-25d3c9adcc21@gmail.com
---
Arun Iyengar (2):
usb: core: Pair ports of different hubs through their connector
usb: hub: Retry SuperSpeed for a device stuck on its USB 2.0 peer
drivers/usb/core/hub.c | 158 ++++++++++++++++++++++++++++++++++++++++++++++++
drivers/usb/core/hub.h | 5 ++
drivers/usb/core/of.c | 87 ++++++++++++++++++++++++++
drivers/usb/core/port.c | 70 +++++++++++++++++++--
include/linux/usb/of.h | 8 +++
5 files changed, 323 insertions(+), 5 deletions(-)
---
base-commit: f11fe7603df07fbb9fa02b0d385c1696c87a6dab
change-id: 20261110-usb-port-pairing-af0f66f0ab2e
Best regards,
--
Arun Iyengar <aiyengar1990@gmail.com>
next reply other threads:[~2026-11-18 4:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 4:34 Arun Iyengar via B4 Relay [this message]
2026-11-18 4:34 ` [PATCH v5 1/2] usb: core: Pair ports of different hubs " Arun Iyengar via B4 Relay
2026-11-18 15:11 ` Alan Stern
2026-11-18 4:34 ` [PATCH v5 2/2] usb: hub: Retry SuperSpeed for a device stuck on its USB 2.0 peer Arun Iyengar via B4 Relay
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=20261118-usb-port-pairing-v5-0-5f1a26789270@gmail.com \
--to=devnull+aiyengar1990.gmail.com@kernel.org \
--cc=aiyengar1990@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=robh@kernel.org \
--cc=stern@rowland.harvard.edu \
--cc=wenst@chromium.org \
/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®