From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: John Youn <John.Youn@synopsys.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH] usb: dwc3: Set SUSPENDENABLE soon after phy init
Date: Mon, 3 Mar 2025 22:47:19 +0000 [thread overview]
Message-ID: <20250303224706.wzvsf4nw2swzelaw@synopsys.com> (raw)
In-Reply-To: <633aef0afee7d56d2316f7cc3e1b2a6d518a8cc9.1738280911.git.Thinh.Nguyen@synopsys.com>
Hi Greg,
On Thu, Jan 30, 2025, Thinh Nguyen wrote:
> After phy initialization, some phy operations can only be executed while
> in lower P states. Ensure GUSB3PIPECTL.SUSPENDENABLE and
> GUSB2PHYCFG.SUSPHY are set soon after initialization to avoid blocking
> phy ops.
>
> Previously the SUSPENDENABLE bits are only set after the controller
> initialization, which may not happen right away if there's no gadget
> driver or xhci driver bound. Revise this to clear SUSPENDENABLE bits
> only when there's mode switching (change in GCTL.PRTCAPDIR).
>
> Fixes: 6d735722063a ("usb: dwc3: core: Prevent phy suspend during init")
> Cc: stable@vger.kernel.org
> Signed-off-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
> ---
> drivers/usb/dwc3/core.c | 69 +++++++++++++++++++++++++----------------
> drivers/usb/dwc3/core.h | 2 +-
> drivers/usb/dwc3/drd.c | 4 +--
> 3 files changed, 45 insertions(+), 30 deletions(-)
>
Just checking, I hope this patch isn't lost in your inbox. If not, then
you can ignore this message.
BR,
Thinh
next prev parent reply other threads:[~2025-03-03 23:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 23:49 [PATCH] usb: dwc3: Set SUSPENDENABLE soon after phy init Thinh Nguyen
2025-03-03 22:47 ` Thinh Nguyen [this message]
2025-03-04 5:26 ` Greg Kroah-Hartman
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=20250303224706.wzvsf4nw2swzelaw@synopsys.com \
--to=thinh.nguyen@synopsys.com \
--cc=John.Youn@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=stable@vger.kernel.org \
/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