You've convinced me that disconnect() has to block sometimes, if only on occasions when a submission is taking place simultaneously. The blocking could be handled by a spinlock, but on the whole it's probably easier to use a semaphore.
On Thu, 15 Jan 2004, Oliver Neukum wrote: > [..] > > There isn't much difference between a driver blocking the core from > > calling disconnect() by means of ->serialize and a driver sleeping within > > disconnect(). I'm amenable to either approach, and in fact the core will > > work properly either way -- provided the blocking doesn't last _too_ long. > > > > This decision can simply be left up to the individual drivers. > > What about skeleton? If it's not broken... 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
