Linux USB
 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 1/2] usb: dwc3: Tell xhci-plat when the core lost its state on resume
Date: Tue, 10 Nov 2026 07:28:09 +0000	[thread overview]
Message-ID: <sashiko-outbox-206491@kernel.org> (raw)
In-Reply-To: <20261110-dwc3-s2idle-v1-1-2ef4cc3f8130@gmail.com>

> From: Arun Iyengar <aiyengar1990@gmail.com>
> 
> In host mode without wakeup, dwc3_suspend_common() tears the core down
> with dwc3_core_exit() and dwc3_resume_common() initialises it again, so
> the xHCI registers are back at their reset values when xhci-plat resumes.
> xhci_resume() is not told about this: it writes the saved operational
> registers back and asks the controller to restore its internal state
> (USBCMD.CRS), which cannot work on a freshly reset core. It fails with
> USBSTS.SRE, and xhci_resume() only then falls back to a full reset:
> 
>   xhci-hcd xhci-hcd.1.auto: xHC error in resume, USBSTS 0x401, Reinit
> 
> xhci-plat already has a way for the glue to report this:
> xhci_plat_priv.power_lost, which cdns3 sets the same way. Set it from
> dwc3_resume_common() whenever the core was re-initialised (and clear it
> when it was kept running for wakeup), so xhci_resume() goes straight to
> the reset and re-init path.
> 
> Signed-off-by: Arun Iyengar <aiyengar1990@gmail.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261110-dwc3-s2idle-v1-0-2ef4cc3f8130@gmail.com?part=1


  reply	other threads:[~2026-11-10  7:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10  7:16 [PATCH 0/2] usb: dwc3: Keep the host bus across suspend-to-idle Arun Iyengar via B4 Relay
2026-11-10  7:16 ` [PATCH 1/2] usb: dwc3: Tell xhci-plat when the core lost its state on resume Arun Iyengar via B4 Relay
2026-11-10  7:28   ` sashiko-bot [this message]
2026-11-10  7:16 ` [PATCH 2/2] usb: dwc3: Keep the host bus suspended, not torn down, across suspend-to-idle Arun Iyengar via B4 Relay
2026-11-10  7:46   ` sashiko-bot
2026-11-11 12:15   ` Vlad
2026-11-12  8:40     ` 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-206491@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