On Thu, Mar 27, 2003 at 06:30:49AM +0100, Oliver Neukum wrote: > Am Donnerstag, 27. März 2003 01:54 schrieb Greg KH: > > On Wed, Mar 26, 2003 at 11:02:43PM +0100, Oliver Neukum wrote: > > > Hi, > > > > > > this won't be quite to Greg's liking as it introduces holding another > > > semaphore, but it is needed. You must not probe and reset at the same > > > time. This can best be assured by the device's semaphore. > > > > Why not just use the usb bus.subsystem semaphore to prevent this from > > happening? It's grabbed by the driver core when probe happens, so it > > would protect us if we also grab it in reset. > > For two reasons, > > 1. The locking naturally is at device level. > 2. Should USB specific code really use locks of the generic core?
Well I asked Pat, and he said it was ok to use. I'd prefer that, as we would not have to grab yet-another-lock in the probe sequence. Just document it well :) thanks, greg k-h ------------------------------------------------------- This SF.net email is sponsored by: The Definitive IT and Networking Event. Be There! NetWorld+Interop Las Vegas 2003 -- Register today! http://ads.sourceforge.net/cgi-bin/redirect.pl?keyn0001en _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
