Re: [Q] reprobe deferred-probing drivers

From: Greg Kroah-Hartman
Date: Wed Oct 17 2012 - 11:02:35 EST

On Wed, Oct 17, 2012 at 10:27:36AM +0200, Guennadi Liakhovetski wrote:
> Hi
> I've got a situation, for which I currently don't have a (good) solution.
> Let's say device A depends on device B and as long as B hasn't probed, A
> requests deferred probing. Now B probes, which causes A to also succeed
> its probing. Next we want to remove B, say, by unloading its driver. A has
> to go back into "deferred-probing" state. How do we do it? This can be
> achieved by unloading B's driver and loading again. Essentially, we have
> to use the sysfs "unbind" and then the "bind" attributes. But how do we do
> this from the kernel? Shall we export driver_bind() and driver_unbind()?

No, no driver should ever have to mess with that at all, it is up to the
bus to do this. Do you have a pointer to the code you are concerned

greg k-h
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at