Hello, I have a question regarding USB Gadget Implementation. The question is regarding the zero byte packets that are sent/recvd during USB Transfers. Assuming that I have my own peripheral driver, and am using a mass storage functionality on it. Who is responsible to send zero byte packets in the following cases? Is it the peripheral controller driver or is it the gadget layer's responsibility?
1. For a Control transaction, which is of the form Control->Data->Status. When the Data is 'In', there will be a Status stage which will be 'OUT', which is to receive zero byte from host. Will the gadget layer queue such a request, or is it the responsibility of the peripheral driver? 2. Similarly, for a Control transaction, which is of the form Control->Data->Status. When the Data is 'OUT', there will be a Status stage which will be 'IN', which is to send zero byte to host. Will the gadget layer queue such a request, or is it the responsibility of the peripheral driver? 3. Lastly, for a Control transaction of the form Control->Status, where the host will need a zero byte packet. Again, will the upper layer queue such a request? Thanks & Regards. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
