From: sashiko-bot@kernel.org
To: "Qianhui Xu" <xiaqinghuan@mail.ustc.edu.cn>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH 3/3] usb: dwc3: support two connectors sharing one HS data bus
Date: Fri, 06 Nov 2026 11:40:39 +0000 [thread overview]
Message-ID: <sashiko-outbox-201328@kernel.org> (raw)
In-Reply-To: <20261106112811.963923-4-xiaqinghuan@mail.ustc.edu.cn>
> On some boards a single DWC3 controller drives two receptacles: the Super
> Speed pairs are wired to separate PHYs, while the High Speed data lines are
> muxed to whichever connector is in use. Such a controller has to service
> two independent role-switch inputs, and the shared data path has to be
> moved before the controller is reinitialised for the requested role.
>
> Register one usb_role_switch per connector endpoint described by
> "port-select-gpios" and the per-endpoint "mux-state" property. Requests
> from the two switches are serialised by the mux lock, the oldest pending
> request wins, and the port-select GPIO is only changed once the previous
> host or gadget instance has been torn down, which is where
> __dwc3_set_mode() runs. A same-role request that moves the data path to
> the other connector reinitialises the controller as well and starts it
> from the same SUSPHY state as a role change.
>
> [ ... ]
>
> While the two-connector mux owns role selection, the debugfs "mode" write
> used to force a specific role is refused instead of racing with it.
>
> Signed-off-by: Qianhui Xu <xiaqinghuan@mail.ustc.edu.cn>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261106112811.963923-1-xiaqinghuan@mail.ustc.edu.cn?part=3
next prev parent reply other threads:[~2026-11-06 11:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-06 11:28 [PATCH v7 0/3] usb: dwc3: two Type-C connectors sharing one HS data bus Qianhui Xu
2026-11-06 11:28 ` [PATCH 1/3] dt-bindings: usb: snps,dwc3: describe two connectors sharing one HS bus Qianhui Xu
2026-11-06 11:49 ` sashiko-bot
2026-11-06 11:28 ` [PATCH 2/3] usb: roles: look up role switches attached to a graph endpoint Qianhui Xu
2026-11-06 11:35 ` sashiko-bot
2026-11-06 11:28 ` [PATCH 3/3] usb: dwc3: support two connectors sharing one HS data bus Qianhui Xu
2026-11-06 11:40 ` sashiko-bot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-11-04 3:27 [PATCH 0/3] usb: dwc3: two Type-C " Qianhui Xu
2026-11-04 3:27 ` [PATCH 3/3] usb: dwc3: support two " Qianhui Xu
2026-11-04 3:44 ` sashiko-bot
2026-10-13 10:29 [PATCH 0/3] " Qianhui Xu
2026-10-13 10:29 ` [PATCH 3/3] " Qianhui Xu
2026-10-13 11:02 ` sashiko-bot
2026-10-14 20:19 ` kernel test robot
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-201328@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
--cc=xiaqinghuan@mail.ustc.edu.cn \
/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