Linux USB
 help / color / mirror / Atom feed
From: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
To: Krishna Kurapati <quic_kriskura@quicinc.com>
Cc: 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>,
	"quic_ppratap@quicinc.com" <quic_ppratap@quicinc.com>,
	"quic_wcheng@quicinc.com" <quic_wcheng@quicinc.com>,
	"quic_jackp@quicinc.com" <quic_jackp@quicinc.com>,
	"quic_ugoswami@quicinc.com" <quic_ugoswami@quicinc.com>
Subject: Re: [PATCH] usb: dwc3: gadget: Propagate core init errors to UDC during pullup
Date: Thu, 15 Jun 2023 22:31:23 +0000	[thread overview]
Message-ID: <20230615223118.n7mekntjk3qzop4b@synopsys.com> (raw)
In-Reply-To: <20230615222600.er6i6dllmxwylnbf@synopsys.com>

On Thu, Jun 15, 2023, Thinh Nguyen wrote:
> On Wed, Jun 14, 2023, Krishna Kurapati wrote:
> > In scenarios where pullup relies on resume (get sync) to initialize
> > the controller and set the run stop bit, then core_init is followed by
> > gadget_resume which will eventually set run stop bit.
> > 
> > But in cases where the core_init fails, the return value is not sent
> > back to udc appropriately. So according to UDC the controller has
> > started but in reality we never set the run stop bit.
> > 
> > On systems like Android, there are uevents sent to HAL depending on
> > whether the configfs_bind / configfs_disconnect were invoked. In the
> > above mentioned scnenario, if the core init fails, the run stop won't
> > be set and the cable plug-out won't result in generation of any
> > disconnect event and userspace would never get any uevent regarding
> > cable plug out and we never call pullup(0) again. Furthermore none of
> > the next Plug-In/Plug-Out's would be known to configfs.
> > 
> > Return back the appropriate result to UDC to let the userspace/
> > configfs know that the pullup failed so they can take appropriate
> > action.
> > 
> > Signed-off-by: Krishna Kurapati <quic_kriskura@quicinc.com>
> > ---
> >  drivers/usb/dwc3/gadget.c | 4 +++-
> >  1 file changed, 3 insertions(+), 1 deletion(-)
> > 
> > diff --git a/drivers/usb/dwc3/gadget.c b/drivers/usb/dwc3/gadget.c
> > index 578804dc29ca..27cb671e18e3 100644
> > --- a/drivers/usb/dwc3/gadget.c
> > +++ b/drivers/usb/dwc3/gadget.c
> > @@ -2747,7 +2747,9 @@ static int dwc3_gadget_pullup(struct usb_gadget *g, int is_on)
> >  	ret = pm_runtime_get_sync(dwc->dev);
> >  	if (!ret || ret < 0) {
> >  		pm_runtime_put(dwc->dev);
> > -		return 0;
> > +		if (ret < 0)
> > +			pm_runtime_set_suspended(dwc->dev);
> > +		return ret;
> >  	}
> >  
> >  	if (dwc->pullups_connected == is_on) {
> > -- 
> > 2.40.0
> > 
> 
> Acked-by: Thinh Nguyen <Thinh.Nguyen@synopsys.com>
> 

I think this patch qualifies as a fix. Can you also add a fixes tag?

Thanks!
Thinh

      reply	other threads:[~2023-06-15 22:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-14 13:49 [PATCH] usb: dwc3: gadget: Propagate core init errors to UDC during pullup Krishna Kurapati
2023-06-15 22:26 ` Thinh Nguyen
2023-06-15 22:31   ` 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=20230615223118.n7mekntjk3qzop4b@synopsys.com \
    --to=thinh.nguyen@synopsys.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=quic_jackp@quicinc.com \
    --cc=quic_kriskura@quicinc.com \
    --cc=quic_ppratap@quicinc.com \
    --cc=quic_ugoswami@quicinc.com \
    --cc=quic_wcheng@quicinc.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