Re: [PATCH] USB: DWC3: Fix missed isoc IN transaction

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, May 23, 2012 at 10:52:14AM -0400, Alan Stern wrote:
> >  generates xfernotready 
> > to SW, gadget is not ready to send data now. Host is still sending IN 
> > token and receives 0 byte packet. Gadget becomes ready after an 
> > *undefined* time. Now it does not have track of micro frame number.
> 
> The Gadget API has a weakness in that it does not give drivers a way to 
> specify which microframe a particular isochronous packet should belong 
> to.
> 
> So what happens if an IN packet from the host gets corrupted or lost?  
> Does all the following isochronous data get shifted back by one
> interval, or does some of the data get skipped?  The Gadget API doesn't
> say.

yeah this is something which needs to be sorted out, indeed. But this
will only work if controllers give us a reliable way for gadget drivers
to ask which uframe we are now, which isn't always the case. Then how do
we solve that part ?

-- 
balbi

Attachment: signature.asc
Description: Digital signature


[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux