The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Badhri Jagan Sridharan <badhri@google.com>
Cc: Thinh Nguyen <Thinh.Nguyen@synopsys.com>,
	"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
	"raychi@google.com" <raychi@google.com>,
	"royluo@google.com" <royluo@google.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: [PATCH v1 1/2] usb: dwc3: Refactor usb-psy init
Date: Fri, 22 Dec 2023 22:40:23 +0000	[thread overview]
Message-ID: <20231222224022.f57nlj35d2n6azp5@synopsys.com> (raw)
In-Reply-To: <20231216034335.242168-1-badhri@google.com>

On Sat, Dec 16, 2023, Badhri Jagan Sridharan wrote:
> Move usb-psy init to dwc3_populate_usb_psy() so that gadget can re-use
> it to retry setting up usb-psy when null.
> 
> Cc: stable@vger.kernel.org
> Fixes: 6f0764b5adea ("usb: dwc3: add a power supply for current control")

This is not a fix. It shouldn't go to stable.

> Signed-off-by: Badhri Jagan Sridharan <badhri@google.com>
> ---
>  drivers/usb/dwc3/core.c | 24 ++++++++++++++++--------
>  drivers/usb/dwc3/core.h |  1 +
>  2 files changed, 17 insertions(+), 8 deletions(-)
> 
> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> index b101dbf8c5dc..a93425b9c1c0 100644
> --- a/drivers/usb/dwc3/core.c
> +++ b/drivers/usb/dwc3/core.c
> @@ -1495,6 +1495,19 @@ static void dwc3_core_exit_mode(struct dwc3 *dwc)
>  	dwc3_set_prtcap(dwc, DWC3_GCTL_PRTCAP_DEVICE);
>  }
>  
> +void dwc3_populate_usb_psy(struct dwc3 *dwc)
> +{
> +	const char *usb_psy_name;
> +	int ret;
> +
> +	if (dwc->usb_psy)
> +		return;
> +
> +	ret = device_property_read_string(dwc->dev, "usb-psy-name", &usb_psy_name);
> +	if (ret >= 0)
> +		dwc->usb_psy = power_supply_get_by_name(usb_psy_name);
> +}
> +
>  static void dwc3_get_properties(struct dwc3 *dwc)
>  {
>  	struct device		*dev = dwc->dev;
> @@ -1510,8 +1523,6 @@ static void dwc3_get_properties(struct dwc3 *dwc)
>  	u8			tx_thr_num_pkt_prd = 0;
>  	u8			tx_max_burst_prd = 0;
>  	u8			tx_fifo_resize_max_num;
> -	const char		*usb_psy_name;
> -	int			ret;
>  
>  	/* default to highest possible threshold */
>  	lpm_nyet_threshold = 0xf;
> @@ -1544,12 +1555,9 @@ static void dwc3_get_properties(struct dwc3 *dwc)
>  	else
>  		dwc->sysdev = dwc->dev;
>  
> -	ret = device_property_read_string(dev, "usb-psy-name", &usb_psy_name);
> -	if (ret >= 0) {
> -		dwc->usb_psy = power_supply_get_by_name(usb_psy_name);
> -		if (!dwc->usb_psy)
> -			dev_err(dev, "couldn't get usb power supply\n");
> -	}
> +	dwc3_populate_usb_psy(dwc);
> +	if (!dwc->usb_psy)
> +		dev_err(dev, "couldn't get usb power supply\n");
>  
>  	dwc->has_lpm_erratum = device_property_read_bool(dev,
>  				"snps,has-lpm-erratum");
> diff --git a/drivers/usb/dwc3/core.h b/drivers/usb/dwc3/core.h
> index efe6caf4d0e8..6c65d76e6fe2 100644
> --- a/drivers/usb/dwc3/core.h
> +++ b/drivers/usb/dwc3/core.h
> @@ -1526,6 +1526,7 @@ struct dwc3_gadget_ep_cmd_params {
>  void dwc3_set_prtcap(struct dwc3 *dwc, u32 mode);
>  void dwc3_set_mode(struct dwc3 *dwc, u32 mode);
>  u32 dwc3_core_fifo_space(struct dwc3_ep *dep, u8 type);
> +void dwc3_populate_usb_psy(struct dwc3 *dwc);
>  
>  #define DWC3_IP_IS(_ip)							\
>  	(dwc->ip == _ip##_IP)
> 
> base-commit: 51920207674e9e3475a91d2091583889792df99a
> -- 
> 2.43.0.472.g3155946c3a-goog
> 

Why do we want to retry again? Perhaps the dwc3 needs to wait for the
power supply available by using -EPROBE_DEFERRED?

BR,
Thinh

      parent reply	other threads:[~2023-12-22 22:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-16  3:43 [PATCH v1 1/2] usb: dwc3: Refactor usb-psy init Badhri Jagan Sridharan
2023-12-16  3:43 ` [PATCH v1 2/2] usb: gadget: Retry populating usb-psy when null Badhri Jagan Sridharan
2023-12-22 22:40 ` Thinh Nguyen [this message]

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=20231222224022.f57nlj35d2n6azp5@synopsys.com \
    --to=thinh.nguyen@synopsys.com \
    --cc=badhri@google.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=raychi@google.com \
    --cc=royluo@google.com \
    --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