Re: [PATCH v4] usb: dwc2: host: Don't retry NAKed transactions right away

Hi, On Tue, Dec 19, 2017 at 8:56 AM, Stefan Wahren wrote: > Hi Doug, > >> Doug Anderson hat am 19. Dezember 2017 um 16:57 >> geschrieben: >> >> >> Felipe, >> >> On Tue, Dec 12, 2017 at 10:30 AM, Douglas Anderson >> wrote:

Re: [PATCH v4] usb: dwc2: host: Don't retry NAKed transactions right away

Hi, On Tue, Dec 19, 2017 at 8:56 AM, Stefan Wahren wrote: > Hi Doug, > >> Doug Anderson hat am 19. Dezember 2017 um 16:57 >> geschrieben: >> >> >> Felipe, >> >> On Tue, Dec 12, 2017 at 10:30 AM, Douglas Anderson >> wrote: >> ... >> >> I don't mean to be a pest, but I'm hoping that we can land

Re: [PATCH v4] usb: dwc2: host: Don't retry NAKed transactions right away

Hi Doug, > Doug Anderson hat am 19. Dezember 2017 um 16:57 > geschrieben: > > > Felipe, > > On Tue, Dec 12, 2017 at 10:30 AM, Douglas Anderson > wrote: > ... > > I don't mean to be a pest, but I'm hoping that we can land this > somewhere (if

Re: [PATCH v4] usb: dwc2: host: Don't retry NAKed transactions right away

Hi Doug, > Doug Anderson hat am 19. Dezember 2017 um 16:57 > geschrieben: > > > Felipe, > > On Tue, Dec 12, 2017 at 10:30 AM, Douglas Anderson > wrote: > ... > > I don't mean to be a pest, but I'm hoping that we can land this > somewhere (if nothing else in your /next tree) just so it

Re: [PATCH v4] usb: dwc2: host: Don't retry NAKed transactions right away

Felipe, On Tue, Dec 12, 2017 at 10:30 AM, Douglas Anderson wrote: > On rk3288-veyron devices on Chrome OS it was found that plugging in an > Arduino-based USB device could cause the system to lockup, especially > if the CPU Frequency was at one of the slower operating

Re: [PATCH v4] usb: dwc2: host: Don't retry NAKed transactions right away

Felipe, On Tue, Dec 12, 2017 at 10:30 AM, Douglas Anderson wrote: > On rk3288-veyron devices on Chrome OS it was found that plugging in an > Arduino-based USB device could cause the system to lockup, especially > if the CPU Frequency was at one of the slower operating points (like > 100 MHz /

[PATCH v4] usb: dwc2: host: Don't retry NAKed transactions right away

On rk3288-veyron devices on Chrome OS it was found that plugging in an Arduino-based USB device could cause the system to lockup, especially if the CPU Frequency was at one of the slower operating points (like 100 MHz / 200 MHz). Upon tracing, I found that the following was happening: * The USB

[PATCH v4] usb: dwc2: host: Don't retry NAKed transactions right away

On rk3288-veyron devices on Chrome OS it was found that plugging in an Arduino-based USB device could cause the system to lockup, especially if the CPU Frequency was at one of the slower operating points (like 100 MHz / 200 MHz). Upon tracing, I found that the following was happening: * The USB