On Thu, Sep 06, 2012 at 05:27:42PM +0300, Felipe Balbi wrote:
Hi,
On Thu, Sep 06, 2012 at 04:27:12PM +0200, Enrico Scholz wrote:
Felipe Balbi ba...@ti.com writes:
Because the fsl_udc_core driver shares one 'status_req' object for the
complete ep0 control transfer, it is not
On Wed, Sep 05, 2012 at 02:10:39AM +, Chen Peter-B29397 wrote:
Because the fsl_udc_core driver shares one 'status_req' object for the
complete ep0 control transfer, it is not possible to prime the final
STATUS phase immediately after the IN transaction. E.g. ch9getstatus()
Felipe Balbi ba...@ti.com writes:
Because the fsl_udc_core driver shares one 'status_req' object for the
complete ep0 control transfer, it is not possible to prime the final
STATUS phase immediately after the IN transaction. E.g. ch9getstatus()
executed:
| req = udc-status_req;
|
Hi,
On Thu, Sep 06, 2012 at 04:27:12PM +0200, Enrico Scholz wrote:
Felipe Balbi ba...@ti.com writes:
Because the fsl_udc_core driver shares one 'status_req' object for the
complete ep0 control transfer, it is not possible to prime the final
STATUS phase immediately after the IN
Because the fsl_udc_core driver shares one 'status_req' object for the
complete ep0 control transfer, it is not possible to prime the final
STATUS phase immediately after the IN transaction. E.g. ch9getstatus()
executed:
| req = udc-status_req;
| ...
| list_add_tail(req-queue, ep-queue);
| if
Because the fsl_udc_core driver shares one 'status_req' object for the
complete ep0 control transfer, it is not possible to prime the final
STATUS phase immediately after the IN transaction. E.g. ch9getstatus()
executed:
| req = udc-status_req;
| ...
| list_add_tail(req-queue,