Re: usb hub driver bug in overcurrent handling?

On Fri, Jul 13, 2018 at 04:35:33PM -0400, Alan Stern wrote: > On Fri, 13 Jul 2018, Bin Liu wrote: > > > Hi, > > > > I got a report saying that when overcurrent happens in one of the hub > > downstream ports, USB_PORT_STAT_OVERCURRENT is not set in portstatus, > > instead

Re: usb hub driver bug in overcurrent handling?

On Fri, 13 Jul 2018, Bin Liu wrote: > Hi, > > I got a report saying that when overcurrent happens in one of the hub > downstream ports, USB_PORT_STAT_OVERCURRENT is not set in portstatus, > instead USB_PORT_STAT_C_OVERCURRENT is set in portchange, then the > overcurrent condition is not handled

Re: usb hub driver bug in overcurrent handling?

On Fri, Jul 13, 2018 at 02:22:32PM -0500, Bin Liu wrote: > Hi, > > I got a report saying that when overcurrent happens in one of the hub > downstream ports, USB_PORT_STAT_OVERCURRENT is not set in portstatus, > instead USB_PORT_STAT_C_OVERCURRENT is set in portchange, then the > overcurrent

usb hub driver bug in overcurrent handling?

Hi, I got a report saying that when overcurrent happens in one of the hub downstream ports, USB_PORT_STAT_OVERCURRENT is not set in portstatus, instead USB_PORT_STAT_C_OVERCURRENT is set in portchange, then the overcurrent condition is not handled in hub_event(). The following patch solves the