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 9:51 AM, Pratyush Anand <pratyush.anand@xxxxxx> wrote:
>
> 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.
>
I am not sure we should hit this condition ideally.
By default the gadget's interface would be parked at AltSetting_0 by the host,
which would mean no IN token. And if it's non-zero AltSetting the gadget
should be ready to provide data - be it 'real' or 'dummy'.
Also, ISOC is not meant to be lossless. So such missed frames should
simply appear as distortion in media.
--
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