On Fri, Dec 13, 2002, Oliver Neukum <[EMAIL PROTECTED]> wrote: > > > > For 2.4 I suggest that you do the reset by hand. 2.5 will need to > > > seperate physical and logical reset. > > > > It doesn't look obvious to me. > > > > usb_reset_device() doesn't trigger any probe() or disconnect() > > processing. > > > > That is unless the driver actually does what the comment for > > usb_reset_device() says and does all of the disconnect() by hand. > > Won't reset cause the device to lose its address thus in the eyes > of usbcore to go away?
Not really. Take a look at the implementation of usb_reset_device(). It resets the device, then reprograms the address and refetches the descriptors. The idea is that it can be called during probe() specifically to allow drivers to upload firmware and then reset the device. An interrupt will be generated to the hub driver for that reset presumably and the hub will be queued to be checked. However, the initial probe() call is happening in khubd, so can't possibly deadlock. JE ------------------------------------------------------- This sf.net email is sponsored by: With Great Power, Comes Great Responsibility Learn to use your power at OSDN's High Performance Computing Channel http://hpc.devchannel.org/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
