> > > same error code. The > > > USB core treats it the same as though the device > had > > > been unplugged and > > > then plugged in again. This means your driver > (or > > > possibly a different > > > driver) will be re-probed with a new usb_device > > > structure. > > > > I'm sorry I didn't understand this. > usb_reset_device's > > only error return is ENODEV. Does this cause the > > re-probing? So, this is considered as a new device > - > > right? > > More or less right. The idea is that if anything > goes wrong, the old > device structure is removed -- hence the ENODEV. > When a new device > structure is created, the drivers will be re-probed. > So your code doesn't need to do anything special.
How does this re-probing happen? Does USB core re-register my driver on its own or do I have to do it? > > And, what's the advantage/disadvantage of going > with > > this route or with usb_reset_dev? > > This _is_ the usb_reset_device route. > What I meant was, is it better to return ENODEV directly from probe when I find a failed device, or is it better to call usb_reset_device, and let it handle. Thanks.. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
