Linux USB
 help / color / mirror / Atom feed
From: Dang Huynh <danct12@riseup.net>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	Jisheng Zhang <jszhang@kernel.org>,
	Kenta Sato <tosainu.maple@gmail.com>,
	Thinh Nguyen <Thinh.Nguyen@synopsys.com>
Cc: John Youn <John.Youn@synopsys.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	stable <stable@kernel.org>, Manu Gautam <mgautam@codeaurora.org>,
	Roger Quadros <rogerq@ti.com>
Subject: Re: [PATCH] usb: dwc3: Soft reset phy on probe for host
Date: Tue, 03 Oct 2023 14:49:03 +0000	[thread overview]
Message-ID: <6120384.lOV4Wx5bFT@melttower> (raw)
In-Reply-To: <70aea513215d273669152696cc02b20ddcdb6f1a.1694564261.git.Thinh.Nguyen@synopsys.com>

Hi Thinh,

I can confirm that this patch fixed the USB 3.0 port on the Pinebook Pro. It may 
be too late for a Tested-by but:

Tested-by: Dang Huynh <danct12@riseup.net>

Best regards,
Dang

On Wednesday, September 13, 2023 12:52:15 AM UTC Thinh Nguyen wrote:
> When there's phy initialization, we need to initiate a soft-reset
> sequence. That's done through USBCMD.HCRST in the xHCI driver and its
> initialization, However, the dwc3 driver may modify core configs before
> the soft-reset. This may result in some connection instability. So,
> ensure the phy is ready before the controller updates the GCTL.PRTCAPDIR
> or other settings by issuing phy soft-reset.
> 
> Note that some host-mode configurations may not expose device registers
> to initiate the controller soft-reset (via DCTL.CoreSftRst). So we reset
> through GUSB3PIPECTL and GUSB2PHYCFG instead.
> 
> Cc: stable@vger.kernel.org
> Fixes: e835c0a4e23c ("usb: dwc3: don't reset device side if dwc3 was
> configured as host-only") Reported-by: Kenta Sato <tosainu.maple@gmail.com>
> Closes: https://lore.kernel.org/linux-usb/ZPUciRLUcjDywMVS@debian.me/
> Signed-off-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
> ---
>  drivers/usb/dwc3/core.c | 39 ++++++++++++++++++++++++++++++++++++++-
>  1 file changed, 38 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> index 9c6bf054f15d..343d2570189f 100644
> --- a/drivers/usb/dwc3/core.c
> +++ b/drivers/usb/dwc3/core.c
> @@ -279,9 +279,46 @@ int dwc3_core_soft_reset(struct dwc3 *dwc)
>  	 * XHCI driver will reset the host block. If dwc3 was configured 
for
>  	 * host-only mode or current role is host, then we can return 
early.
>  	 */
> -	if (dwc->dr_mode == USB_DR_MODE_HOST || dwc->current_dr_role ==
> DWC3_GCTL_PRTCAP_HOST) +	if (dwc->current_dr_role == 
DWC3_GCTL_PRTCAP_HOST)
>  		return 0;
> 
> +	/*
> +	 * If the dr_mode is host and the dwc->current_dr_role is not the
> +	 * corresponding DWC3_GCTL_PRTCAP_HOST, then the 
dwc3_core_init_mode
> +	 * isn't executed yet. Ensure the phy is ready before the 
controller
> +	 * updates the GCTL.PRTCAPDIR or other settings by soft-resetting
> +	 * the phy.
> +	 *
> +	 * Note: GUSB3PIPECTL[n] and GUSB2PHYCFG[n] are port settings where 
n
> +	 * is port index. If this is a multiport host, then we need to 
reset
> +	 * all active ports.
> +	 */
> +	if (dwc->dr_mode == USB_DR_MODE_HOST) {
> +		u32 usb3_port;
> +		u32 usb2_port;
> +
> +		usb3_port = dwc3_readl(dwc->regs, DWC3_GUSB3PIPECTL(0));
> +		usb3_port |= DWC3_GUSB3PIPECTL_PHYSOFTRST;
> +		dwc3_writel(dwc->regs, DWC3_GUSB3PIPECTL(0), usb3_port);
> +
> +		usb2_port = dwc3_readl(dwc->regs, DWC3_GUSB2PHYCFG(0));
> +		usb2_port |= DWC3_GUSB2PHYCFG_PHYSOFTRST;
> +		dwc3_writel(dwc->regs, DWC3_GUSB2PHYCFG(0), usb2_port);
> +
> +		/* Small delay for phy reset assertion */
> +		usleep_range(1000, 2000);
> +
> +		usb3_port &= ~DWC3_GUSB3PIPECTL_PHYSOFTRST;
> +		dwc3_writel(dwc->regs, DWC3_GUSB3PIPECTL(0), usb3_port);
> +
> +		usb2_port &= ~DWC3_GUSB2PHYCFG_PHYSOFTRST;
> +		dwc3_writel(dwc->regs, DWC3_GUSB2PHYCFG(0), usb2_port);
> +
> +		/* Wait for clock synchronization */
> +		msleep(50);
> +		return 0;
> +	}
> +
>  	reg = dwc3_readl(dwc->regs, DWC3_DCTL);
>  	reg |= DWC3_DCTL_CSFTRST;
>  	reg &= ~DWC3_DCTL_RUN_STOP;
> 
> base-commit: 0bb80ecc33a8fb5a682236443c1e740d5c917d1d





  parent reply	other threads:[~2023-10-03 14:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-13  0:52 [PATCH] usb: dwc3: Soft reset phy on probe for host Thinh Nguyen
2023-09-13  0:57 ` Thinh Nguyen
2023-09-13 17:31   ` Kenta Sato
2023-10-03 14:49 ` Dang Huynh [this message]
2023-10-12 18:20   ` Thinh Nguyen
  -- strict thread matches above, loose matches on Subject: below --
2023-09-21 12:41 Da Xue
2023-10-02 18:59 ` Thinh Nguyen

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=6120384.lOV4Wx5bFT@melttower \
    --to=danct12@riseup.net \
    --cc=John.Youn@synopsys.com \
    --cc=Thinh.Nguyen@synopsys.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jszhang@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mgautam@codeaurora.org \
    --cc=rogerq@ti.com \
    --cc=stable@kernel.org \
    --cc=tosainu.maple@gmail.com \
    /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