On Wed, Sep 16, 2015 at 10:17:43AM +0200, Tomeu Vizoso wrote: > AFAICS, this is a must currently for correct operation in simple-bus > and simple-mfd situations, because probing order is currently very > unpredictable and it's totally possible for the probing of a child to > start before the probing of its parent has finished (if async probing > is enabled or if a module is loaded that registers a child's driver at > the wrong time). Hrm. That's worrying for devices that rely on peering into their parent device for things... > I would prefer if the core would take care of making sure that parents > are always probed before their children, but the unconditional locking > of the parent device stands in the way. In the MFD case this is another reason for not putting the device structure into the DT - if it isn't then the ordering is controlled by the device being instantiated.
Attachment:
signature.asc
Description: Digital signature
