| commit | c7fcdeb2627c46b7ec3f0bcb2054b10405f9a70e | |
| author | Felipe Balbi <balbi@ti.com> | |
| Sat, 27 Aug 2011 19:28:36 +0000 (27 22:28 +0300) | ||
| committer | Felipe Balbi <balbi@ti.com> | |
| Fri, 9 Sep 2011 10:02:07 +0000 (9 13:02 +0300) | ||
| tree | e773414177e516a4e7dfad6bfe03f7e46a7388ea | treesnapshot (tar.gz zip) |
| parent | 984f66a6f9b9c02d6cb077ac49ec9fe5445fb1ee | commitdiff |
usb: dwc3: ep0: simplify EP0 state machine
The DesignWare USB3 core tells us which phase
of a control transfer should be started, it
also tells us which physical endpoint needs
that transfer.
With these two informations, we have all we
need to simply EP0 handling quite a lot and
get rid rid of the SW state machine tracking
ep0 states.
For achieving this perfectly, we needed to
add support for situations where we get
XferNotReady while endpoint is still busy
and XferNotReady while gadget driver still
hasn't queued a request.
Signed-off-by: Felipe Balbi <balbi@ti.com>
The DesignWare USB3 core tells us which phase
of a control transfer should be started, it
also tells us which physical endpoint needs
that transfer.
With these two informations, we have all we
need to simply EP0 handling quite a lot and
get rid rid of the SW state machine tracking
ep0 states.
For achieving this perfectly, we needed to
add support for situations where we get
XferNotReady while endpoint is still busy
and XferNotReady while gadget driver still
hasn't queued a request.
Signed-off-by: Felipe Balbi <balbi@ti.com>
| drivers/usb/dwc3/core.h | diffblobblamehistory | |
| drivers/usb/dwc3/ep0.c | diffblobblamehistory | |
| drivers/usb/dwc3/gadget.c | diffblobblamehistory |