From: sashiko-bot@kernel.org
To: "Filippo Falezza" <effeffe99@gmail.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: dwc3: qcom: Restore UTMI PIPE clock on resume
Date: Tue, 27 Oct 2026 01:26:05 +0000 [thread overview]
Message-ID: <sashiko-outbox-185979@kernel.org> (raw)
In-Reply-To: <20261027-dwc3-utmi-resume-v1-1-ca9f0aa65783@gmail.com>
> Boards whose controller has no SuperSpeed PHY set
> qcom,select-utmi-as-pipe-clk, and the glue then programs QSCRATCH
> GENERAL_CFG so that the core's PIPE clock domain runs from the UTMI
> clock. This is only done at probe.
>
> When the SoC reaches its deepest state in suspend-to-idle (CX power
> collapse), the QSCRATCH registers lose their contents. On resume the
> core is reinitialised with its PIPE domain unclocked, and the gadget
> does not come back:
>
> dwc3-qcom a600000.usb: failed to enable ep0out
>
> The link stays down until the driver is unbound and bound again.
>
> Remember the property at probe and select the UTMI clock again in
> dwc3_qcom_resume(), after the clocks and interconnect paths are enabled
> and before the core is resumed. Move dwc3_qcom_select_utmi_clk() up so
> that it is defined before its new caller.
>
> Fixes: a4333c3a6ba9 ("usb: dwc3: Add Qualcomm DWC3 glue driver")
> Signed-off-by: Filippo Falezza <effeffe99@gmail.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261027-dwc3-utmi-resume-v1-1-ca9f0aa65783@gmail.com?part=1
next prev parent reply other threads:[~2026-10-27 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 1:21 [PATCH] usb: dwc3: qcom: Restore UTMI PIPE clock on resume Filippo Falezza
2026-10-27 1:26 ` sashiko-bot [this message]
2026-10-27 5:01 ` Prashanth K
2026-10-27 11:06 ` Dmitry Baryshkov
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-185979@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=effeffe99@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