On Wed, Feb 6, 2019 at 5:16 PM Frank Mori Hess <fmh6jj@xxxxxxxxx> wrote: > > Hi Minas, > > On Tue, Feb 5, 2019 at 5:22 AM Minas Harutyunyan > <minas.harutyunyan@xxxxxxxxxxxx> wrote: > > Could you please try patch submitted by me today:"[PATCH] usb: dwc2: > > gadget: Consider VBUS discharge time in disconnect flow" > > I should be able to try it tonight or tomorrow to see if it makes the > driver recognize a cable disconnect. However, looking at the patch it > is doing by default a 1 second busy wait in interrupt context. My > understanding is that is a highly discouraged practice, on a single > core machine it would freeze the entire machine for a full second. > Can the disconnect handling be done in a tasklet? > I backported the patch to my 4.17 dwc2 driver but it didn't help. I did see it do the extra 1 second pause when I pulled the plug, but no "b session end/disconnect", just a suspend. I doubt I will be able to test further since my use case treats suspended and disconnected the same so this isn't actually a problem for us. -- Frank
