end again at the time.
How do you think?
Best Regards,
Jung Daehwan
> Alan Stern
>
> > Signed-off-by: Daehwan Jung
> > ---
> > drivers/usb/dwc3/gadget.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/usb/dwc3/g
ease check it.
usb: dwc3: gadget: Allow runtime suspend if UDC unbinded
Best Regards,
Jung Daehwan
e-suspend but it doesn't mean stopping gadget.
Are you stopping gadget manually in this case?
Best Regards,
Jung Daehwan
On Wed, Jan 20, 2021 at 11:44:05PM -0800, Wesley Cheng wrote:
>
>
> On 1/20/2021 10:49 PM, Jung Daehwan wrote:
> > Hi,
> >
> > On Thu, Jan 21, 2021 at 01:00:32AM +, Thinh Nguyen wrote:
> >> Hi,
> >>
> >> Daehwan Jung wrote:
> &
gt;
> Thanks,
> Thinh
I checked Wesly Cheng's pathces but it's not same.
What I want to do for this patch is to avoid pullup from platform side.
(android in my case)
It's possible that platform side tries to pullup by UDC_Store after usb is
already disconnected.
It can finally run controller and enable irq.
I think we have to avoid it and other possible things related to platform side.
BR,
Jung Daehwan
Hi,
On Thu, Jan 21, 2021 at 01:00:32AM +, Thinh Nguyen wrote:
> Hi,
>
> Daehwan Jung wrote:
> > Sometimes dwc3_gadget_pullup and dwc3_gadget_set_speed are called after
> > entering suspend. That's why it needs to check whether suspend
> >
> > 1. dwc3 sends disconnect uevent and turn off.
6 matches
Mail list logo