Hi,
I am writing a new gadget driver for a USB device controller by Renesas,
the M66591GP. I have a question about the way the endpoint
autoconfiguration (linux/drivers/usb/gadget/epautoconf.c) interacts with
the endpoint list I provide from my driver.
In ep_matches() (line 93 in 2.6.15 and 2.6.20.1), where the endpoint name
is parsed for the type of endpoint (bulk, interrupt, etc.):
switch (type) {
case USB_ENDPOINT_XFER_INT:
/* bulk endpoints handle interrupt transfers,
* except the toggle-quirky iso-synch kind
*/
if ('s' == tmp[2]) // == "-iso"
return 0;
/* for now, avoid PXA "interrupt-in";
* it's documented as never using DATA1.
*/
if (gadget_is_pxa (gadget)
&& 'i' == tmp [1])
return 0;
break;
Can someone explain the comment "bulk endpoints handle interrupt
transfers"?
Assuming it means that bulk endpoints can transmit interrupt frames, why
would there be dedicated interrupt endpoints in the controller? (Perhaps
this is an "ask the manufacturer" type of question, but I am looking for
guidance, not demanding answers -- speculations are welcome.)
Thanks,
Catalin
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
