Multiple Commands in USB-2 - UAS

Madhukar madhukar.gubba at gmail.com
Sat Aug 22 02:45:40 PDT 2009


* From the T10 Reflector (t10 at t10.org), posted by:
* Madhukar <madhukar.gubba at gmail.com>
*
On Thu, Aug 20, 2009 at 7:06 PM, Madhukar<madhukar.gubba at gmail.com> wrote:
> Thank You for the replies.
>
> I have one last question. If USB2.0 supports multiple command
> processing, here is the scenario where I am getting problem
>
> If “UAS initiator port” issues a READ command followed by WRITE
> command, the SENSE_IU (of READ command) data buffer is getting filled
> with the data of WRITE_READY issued for WRITE command by the “UAS
> target port” at the HCD level.
>
> This is happening because when UAS Initiator port is expecting
> SENSE_IU (for READ Command) the UAS target port sent WRITE_READY (for
> WRITE Command) to UAS Initiator port on same pipe.
>
> I am assuming that the READ and WRITE can be processed simultaneously
> at “UAS target port” and there is no verification of Tag values of
> request and response at HCD level in USB 2.0.
>
I'm in midway of the implementation. Any help is much appreciated.
Thanks and Regards,
madhukar
*
* For T10 Reflector information, send a message with
* 'info t10' (no quotes) in the message body to majordomo at t10.org



More information about the T10 mailing list