Re: [PATCH v4 13/15] usb: dwc3: Add workaround for isoc start transfer failure

2018-03-16 Thread Felipe Balbi
Hi, Thinh Nguyen writes: >>> Thank you for reviewing the patches. I'll make the change to this patch >>> for the next merge window. However, can you cherry-pick the other >>> patches in this series for this merge window? If they also need more >>> work, please let me

Re: [PATCH v4 13/15] usb: dwc3: Add workaround for isoc start transfer failure

2018-03-14 Thread Thinh Nguyen
Hi Felipe, On 3/14/2018 1:56 AM, Felipe Balbi wrote: > > Hi, > > Thinh Nguyen writes: >>> Thinh Nguyen writes: In DWC_usb31 version 1.70a-ea06 and prior, for highspeed and fullspeed isochronous IN, BIT[15:14] of the 16-bit

Re: [PATCH v4 13/15] usb: dwc3: Add workaround for isoc start transfer failure

2018-03-14 Thread Felipe Balbi
Hi, Thinh Nguyen writes: >> Thinh Nguyen writes: >>> In DWC_usb31 version 1.70a-ea06 and prior, for highspeed and fullspeed >>> isochronous IN, BIT[15:14] of the 16-bit microframe number reported by >>> the XferNotReady event are invalid.

Re: [PATCH v4 13/15] usb: dwc3: Add workaround for isoc start transfer failure

2018-03-13 Thread Thinh Nguyen
Hi Felipe, On 3/13/2018 1:45 AM, Felipe Balbi wrote: > > Hi, > > Thinh Nguyen writes: >> In DWC_usb31 version 1.70a-ea06 and prior, for highspeed and fullspeed >> isochronous IN, BIT[15:14] of the 16-bit microframe number reported by >> the XferNotReady event are

Re: [PATCH v4 13/15] usb: dwc3: Add workaround for isoc start transfer failure

2018-03-13 Thread Felipe Balbi
Hi, Thinh Nguyen writes: > In DWC_usb31 version 1.70a-ea06 and prior, for highspeed and fullspeed > isochronous IN, BIT[15:14] of the 16-bit microframe number reported by > the XferNotReady event are invalid. The driver uses this number to > schedule the isochronous