Hi,
As the recommended practice in 2.6 is to keep the endpoint queue busy,
drivers (should) normally want to use multiple urbs on an endpoint.
Given that, it would be very handy to have a list head in struct urb, so
that drivers could conveniently manipulate multiple urbs.
(As a real world example, in the soon to be submitted renewed usbatm
subsystem we have to use a wrapper struct only to associate urbs with
list heads.)
OTOH struct urb already contains a list head:
struct urb {
/* private, usb core and host controller only fields in the urb */
...
struct list_head urb_list; /* list pointer to all active urbs */
...
};
Is it safe to use it for driver's purposes when the driver owns the urb,
that is, starting from the completion routine until the urb is submitted
with usb_submit_urb()? If it is, can it be guaranteed in future, e.g.
by moving the list head into the public section of struct urb?
Otherwise, would it be possible and/or useful to add a public list head
to struct urb for use by the drivers?
Thanks,
Roman.
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.
Get your fingers limbered up and give it your best shot. 4 great events, 4
opportunities to win big! Highest score wins.NEC IT Guy Games. Play to
win an NEC 61 plasma display. Visit http://www.necitguy.com/?r=20
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
