On Thu, 8 May 2014, Paul Zimmerman wrote: > > Just FYI, the DWC3 core is designed to always respond to SETUP packets. > > It has a 3-deep input buffer for SETUPs, provided the RxFIFO is set up > > properly according to the databook. If the buffer fills up, then > > further SETUP packets will get lost, but they will still be ACKed. > > I forgot to say, this means that it is not necessary to prepare a > buffer for the next SETUP immediately after the previous SETUP stage > ends, since the next SETUP will be cached in the controller. > > There is a flowchart in the databook that describes the programming > flow for Control transfers. I think the DWC3 driver follows this > pretty closely, although it has been a while since I last reviewed it. Okay. I'm not really interested in pursuing this in depth. I just wanted to bring it to people's attention -- particularly since it seems like the most important synchronization work needs to be done in composite.c but isn't there now. Alan Stern -- 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
