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

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

 



On 5/23/2012 12:02 AM, Paul Zimmerman wrote:
The sequence should go like this:

- The host sends the Set Interface command that enables the isoc
   endpoint.


So, is it necessary to have a different alternate setting for isoc transfer? Is Set Interface mandatory to start isoc?

Is it that, there can not be asynchronous isoc transfer? Host sends IN token. Core receives it, sends 0 packet to host, 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.


--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


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

  Powered by Linux