linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Jisheng Zhang <jszhang@kernel.org>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: dwc3: don't reset device side if dwc3 was configured as host-only
Date: Fri, 30 Jun 2023 22:23:56 +0000	[thread overview]
Message-ID: <20230630222353.uxaaa3t2av2fktu7@synopsys.com> (raw)
In-Reply-To: <20230627162018.739-1-jszhang@kernel.org>

On Wed, Jun 28, 2023, Jisheng Zhang wrote:
> Commit c4a5153e87fd ("usb: dwc3: core: Power-off core/PHYs on
> system_suspend in host mode") replaces check for HOST only dr_mode with
> current_dr_role. But during booting, the current_dr_role isn't
> initialized, thus the device side reset is always issued even if dwc3
> was configured as host-only. What's more, on some platforms with host
> only dwc3, aways issuing device side reset by accessing device register
> block can cause kernel panic.
> 

Ah... good catch!

This should be backported to stable.

So perhaps you or Greg can add Cc: stable@vger.kernel.org

> Fixes: c4a5153e87fd ("usb: dwc3: core: Power-off core/PHYs on system_suspend in host mode")
> Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
> ---
>  drivers/usb/dwc3/core.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> index 7b2ce013cc5b..16d7a1d1cbfa 100644
> --- a/drivers/usb/dwc3/core.c
> +++ b/drivers/usb/dwc3/core.c
> @@ -277,9 +277,9 @@ int dwc3_core_soft_reset(struct dwc3 *dwc)
>  	/*
>  	 * We're resetting only the device side because, if we're in host mode,
>  	 * XHCI driver will reset the host block. If dwc3 was configured for
> -	 * host-only mode, then we can return early.
> +	 * host-only mode or current role is host, then we can return early.
>  	 */
> -	if (dwc->current_dr_role == DWC3_GCTL_PRTCAP_HOST)
> +	if (dwc->dr_mode == USB_DR_MODE_HOST || dwc->current_dr_role == DWC3_GCTL_PRTCAP_HOST)
>  		return 0;
>  
>  	reg = dwc3_readl(dwc->regs, DWC3_DCTL);
> -- 
> 2.40.1
> 

Acked-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>

Thanks,
Thinh

  reply	other threads:[~2023-06-30 22:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 16:20 [PATCH] usb: dwc3: don't reset device side if dwc3 was configured as host-only Jisheng Zhang
2023-06-30 22:23 ` Thinh Nguyen [this message]
2023-09-30  7:43 ` Lu jicong
  -- strict thread matches above, loose matches on Subject: below --
2023-11-16 16:42 Köry Maincent
2023-11-16 16:59 ` Köry Maincent
2023-11-17  1:40   ` Thinh Nguyen
2023-11-17  1:55     ` Thinh Nguyen
2023-11-17  9:22       ` Köry Maincent
2023-11-21  9:49       ` Köry Maincent
2023-12-01  9:09         ` Köry Maincent
2023-12-02  0:26           ` Thinh Nguyen
2023-12-05  1:27             ` Thinh Nguyen
2023-12-05 13:56               ` Jisheng Zhang
2023-12-05 14:19             ` Köry Maincent

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=20230630222353.uxaaa3t2av2fktu7@synopsys.com \
    --to=thinh.nguyen@synopsys.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jszhang@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@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;
as well as URLs for NNTP newsgroup(s).