On Thu, 15 Jan 2004, David Brownell wrote:
> All drivers that unblock endpoints would be by definition buggy.
> That API should be purely internal to usbcore anyway; that's what
> it is today (effectively), since drivers aren't allowed to change
> the endpoint maxpacket sizes.
I disagree. A driver might want to block an endpoint as an easy way to
prevent automatic resubmissions, say in a release() routine. Once the URB
was idle, the driver would then want to unblock the endpoint for use in a
later open() call. The code might look like this:
usb_refuse_requests(usbdev, epnum, dir);
usb_unlink_urb(urb); // Async
usb_wait_for_urb(urb);
urb_accept_requests(usbdev, epnum, dir);
I think that's a legitimate usage and not buggy at all.
Alan Stern
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
[EMAIL PROTECTED]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
