From: sashiko-bot@kernel.org
To: "Joonhoe Kim" <26rote@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH v2] usb: dwc3: tell xHCI that it lost its state when the core is powered off
Date: Thu, 12 Nov 2026 14:26:25 +0000 [thread overview]
Message-ID: <sashiko-outbox-211314@kernel.org> (raw)
In-Reply-To: <20261112141512.1840-1-26rote@gmail.com>
> dwc3_suspend_common() powers the core off for system suspend
> (dwc3_core_exit()) in OTG mode (DWC3_GCTL_PRTCAP_OTG), and in host mode
> when the controller may not wake the system or needs a full re-init. The
> xHCI registers and the state saved with the Controller Save State
> command are gone then, but nothing tells xhci-plat: xhci_resume() takes
> the "state intact" path, writes the saved registers back and asks the
> controller to restore its state (CRS).
>
> xhci-plat has a flag for exactly this, power_lost (commit 668cc6bc1178
> ("usb: host: xhci-plat: allow upper layers to signal power loss"), used
> by cdns3), but dwc3 never sets it.
>
> On a Lenovo Y700 Gen 5 (TB323FU, SM8850; DWC3 + eUSB2 PHY) with a USB
> 2.0 hub, a USB 3 flash drive and a Billboard device attached, and USB
> wakeup disabled, s2idle then broke the host controller on resume: either
> [ ... ]
> the dwc3 core is suspended does not reset the controller.
>
> Fixes: c4a5153e87fd ("usb: dwc3: core: Power-off core/PHYs on system_suspend in host mode")
> Fixes: f09cc79b4b33 ("usb: dwc3: add dual role support using OTG block")
> Signed-off-by: Joonhoe Kim <26rote@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261112141512.1840-1-26rote@gmail.com?part=1
prev parent reply other threads:[~2026-11-12 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 14:15 [PATCH v2] usb: dwc3: tell xHCI that it lost its state when the core is powered off Joonhoe Kim
2026-11-12 14:26 ` sashiko-bot [this message]
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-211314@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=26rote@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.