From: sashiko-bot@kernel.org
To: "Arun Iyengar" <aiyengar1990@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH RFC 1/2] usb: dwc3: Let the glue keep the host bus suspended across suspend-to-idle
Date: Thu, 12 Nov 2026 08:49:09 +0000 [thread overview]
Message-ID: <sashiko-outbox-210786@kernel.org> (raw)
In-Reply-To: <20261112-dwc3-s2idle-optin-v1-1-842e3f8413d0@gmail.com>
> From: Arun Iyengar <aiyengar1990@gmail.com>
>
> In host mode, dwc3_suspend_common() tears the core down for system
> suspend (dwc3_core_exit(): PHYs off, core reset) unless the controller
> is a wakeup source. By then xhci-plat has already suspended the bus:
> the root ports and every device behind them are in U3/suspend and
> expect to keep their power session (Documentation/driver-api/usb/
> persist.rst). Resetting the core ends all of them. On resume xhci-plat
> finds a reset controller ("root hub lost power or was reset") and the
> USB core has to reset-resume every device, which only works for devices
> that come back within the 2 s that usb_port_resume() waits for a
> connection.
>
> Devices that are cut off in U3 do not necessarily come back that fast.
> On an Orange Pi 5 (RK3588S) a SanDisk Extreme drive on the Type-A USB3
> [ ... ]
> exactly when suspend tore it down, which xhci_power_lost now records.
> Nothing changes for platforms that do not set the flag, nor for
> suspend-to-RAM, hibernation and needs_full_reinit controllers.
>
> 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-dwc3-s2idle-optin-v1-0-842e3f8413d0@gmail.com?part=1
next prev parent reply other threads:[~2026-11-12 8:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 8:35 [PATCH RFC 0/2] usb: dwc3: Let the Rockchip glue keep the host bus across suspend-to-idle Arun Iyengar via B4 Relay
2026-11-12 8:35 ` [PATCH RFC 1/2] usb: dwc3: Let the glue keep the host bus suspended " Arun Iyengar via B4 Relay
2026-11-12 8:49 ` sashiko-bot [this message]
2026-11-12 8:35 ` [PATCH RFC 2/2] usb: dwc3: rockchip: Keep the host bus across suspend-to-idle on RK3588 Arun Iyengar via B4 Relay
2026-11-12 8:56 ` sashiko-bot
2026-11-12 8:39 ` [PATCH RFC 0/2] usb: dwc3: Let the Rockchip glue keep the host bus across suspend-to-idle Arun Iyengar
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-210786@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox