On Wed, May 14, 2014 at 12:06:40PM -0400, Alan Stern wrote: > On Wed, 14 May 2014, Greg KH wrote: > > > > Is it really safe to rely on the device core always probing drivers in > > > order of driver registration? > > > > Yes it is. > > Okay, good. Do you know if this is documented anywhere? Nope, it isn't, except in the code :) > > > If it is then we are okay (at least in this particular case), because > > > the hub driver will always be registered before the lvstest driver. > > > > Good, then there shouldn't be an issue. > > > > Or just make the lvstest driver have to be "manually" bound to the > > device through the bind file in sysfs, don't let the driver > > automatically bind to anything. > > How can we do that? The probe routine doesn't know whether it was > called as a result of automatic or manual binding. This was Bjørn's > point. Don't put the device id in the driver structure. Then the core will never call the probe function unless manually asked to from the sysfs file interface. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
