Device dependencies and deferred probing

broonie — Fri, 06 Nov 2015 12:30:35 +0000

Yes, exactly.

Device dependencies and deferred probing

tpetazzoni — Wed, 04 Nov 2015 13:14:35 +0000

Rafael Wysocki responded that the real issue is dependencies between drivers

It is not exactly what Rafael said I believe. What Rafael said is that dependencies are not just between devices, but between devices that are actually *bound* to a driver to manage them. Indeed if a device A needs another device B, it doesn't just need this device B to have its platform_device registered. It also needs device B to be bound to a device driver, of which the ->probe() method has been called to actually do something with device B, so that it can be used by device A.

So device A ->probe() should ideally only be triggered when device B ->probe() has completed. Having device B "registered" is not sufficient.

LWN: Comments on "Device dependencies and deferred probing"

Device dependencies and deferred probing

Device dependencies and deferred probing