mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Philipp Zabel <p.zabel@pengutronix.de>,
	Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.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: qcom: Don't leave BCR asserted
Date: Fri, 6 Jun 2025 00:11:48 +0000	[thread overview]
Message-ID: <20250606001139.jaods5yefjccqni2@synopsys.com> (raw)
In-Reply-To: <20250604060019.2174029-1-krishna.kurapati@oss.qualcomm.com>

On Wed, Jun 04, 2025, Krishna Kurapati wrote:
> Leaving the USB BCR asserted prevents the associated GDSC to turn on. This
> blocks any subsequent attempts of probing the device, e.g. after a probe
> deferral, with the following showing in the log:
> 
> [    1.332226] usb30_prim_gdsc status stuck at 'off'
> 
> Leave the BCR deasserted when exiting the driver to avoid this issue.
> 
> Signed-off-by: Krishna Kurapati <krishna.kurapati@oss.qualcomm.com>

Is this a fix? Does this need to be backported to stable?

Either way,

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

Thanks,
Thinh

> ---
>  drivers/usb/dwc3/dwc3-qcom.c | 7 ++-----
>  1 file changed, 2 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/usb/dwc3/dwc3-qcom.c b/drivers/usb/dwc3/dwc3-qcom.c
> index 7334de85ad10..ca7e1c02773a 100644
> --- a/drivers/usb/dwc3/dwc3-qcom.c
> +++ b/drivers/usb/dwc3/dwc3-qcom.c
> @@ -680,12 +680,12 @@ static int dwc3_qcom_probe(struct platform_device *pdev)
>  	ret = reset_control_deassert(qcom->resets);
>  	if (ret) {
>  		dev_err(&pdev->dev, "failed to deassert resets, err=%d\n", ret);
> -		goto reset_assert;
> +		return ret;
>  	}
>  
>  	ret = clk_bulk_prepare_enable(qcom->num_clocks, qcom->clks);
>  	if (ret < 0)
> -		goto reset_assert;
> +		return ret;
>  
>  	r = platform_get_resource(pdev, IORESOURCE_MEM, 0);
>  	if (!r) {
> @@ -755,8 +755,6 @@ static int dwc3_qcom_probe(struct platform_device *pdev)
>  	dwc3_core_remove(&qcom->dwc);
>  clk_disable:
>  	clk_bulk_disable_unprepare(qcom->num_clocks, qcom->clks);
> -reset_assert:
> -	reset_control_assert(qcom->resets);
>  
>  	return ret;
>  }
> @@ -771,7 +769,6 @@ static void dwc3_qcom_remove(struct platform_device *pdev)
>  	clk_bulk_disable_unprepare(qcom->num_clocks, qcom->clks);
>  
>  	dwc3_qcom_interconnect_exit(qcom);
> -	reset_control_assert(qcom->resets);
>  }
>  
>  static int dwc3_qcom_pm_suspend(struct device *dev)
> -- 
> 2.34.1
> 

  reply	other threads:[~2025-06-06  0:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04  6:00 Krishna Kurapati
2025-06-06  0:11 ` Thinh Nguyen [this message]
2025-06-17 21:28   ` Konrad Dybcio
2025-06-18  5:22     ` Krishna Kurapati

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=20250606001139.jaods5yefjccqni2@synopsys.com \
    --to=thinh.nguyen@synopsys.com \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=krishna.kurapati@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    /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

all inboxes | Powered by JetHome®