All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Arun Iyengar" <aiyengar1990@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v2 1/2] usb: core: Pair ports of different hubs through their connector
Date: Thu, 12 Nov 2026 08:50:45 +0000	[thread overview]
Message-ID: <sashiko-outbox-210789@kernel.org> (raw)
In-Reply-To: <20261112-usb-port-pairing-v2-1-45f5a1a29f1f@gmail.com>

> From: Arun Iyengar <aiyengar1990@gmail.com>
> 
> A USB 3 port is two ports to the USB core, a USB 2.0 one and a
> SuperSpeed one, and the core pairs them as peers. Root hub ports are
> paired with the same port number of the other root hub of the same
> xHCI, unless ACPI gives their locations.
> 
> Some SoCs route the two halves of a connector to different host
> controllers. On the Rockchip RK3588, USB 3.0 host 2 is SuperSpeed-only:
> its own USB 2.0 root hub port is not wired to a PHY, and the connector's
> USB 2.0 lines go to a separate EHCI instead. Default pairing then joins
> the SuperSpeed port to a dead USB 2.0 port, and nothing knows about the
> EHCI port that really shares the connector.
> 
> A usb-connector node describes its USB 2.0 data lines as graph port 0
> and its SuperSpeed lanes as graph port 1. When a hub's or host
> controller's graph links one of its ports to a connector whose other
> half leads to a different hub or host controller, pair the port with
> that one instead, and keep it out of the default pairing. Connectors
> whose two halves end on the same node, like a Type-C connector on a
> DWC3, keep the default pairing.
> 
> This lets the runtime PM rules for peers (keep the SuperSpeed port
> powered while its USB 2.0 peer is) apply to such connectors too.
> 
> Signed-off-by: Arun Iyengar <aiyengar1990@gmail.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261112-usb-port-pairing-v2-0-45f5a1a29f1f@gmail.com?part=1


  reply	other threads:[~2026-11-12  8:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12  8:26 [PATCH v2 0/2] usb: core: Pair ports of different host controllers through their connector Arun Iyengar
2026-11-12  8:26 ` Arun Iyengar via B4 Relay
2026-11-12  8:26 ` [PATCH v2 1/2] usb: core: Pair ports of different hubs " Arun Iyengar
2026-11-12  8:26   ` Arun Iyengar via B4 Relay
2026-11-12  8:50   ` sashiko-bot [this message]
2026-11-12  8:26 ` [PATCH v2 2/2] usb: hub: Retry SuperSpeed for a device stuck on its USB 2.0 peer Arun Iyengar
2026-11-12  8:26   ` Arun Iyengar via B4 Relay
2026-11-12  8:42   ` sashiko-bot

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=sashiko-outbox-210789@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=aiyengar1990@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --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.