[PATCH 2/5] drivercore: Add driver probe deferral mechanism
stern at rowland.harvard.edu
Fri Oct 14 11:39:16 EDT 2011
On Thu, 13 Oct 2011, Grant Likely wrote:
> > However it's worth pointing out right at the start that we already have
> > device_pm_move_before(), device_pm_move_after(), and
> > device_pm_move_last(). They are intended specifically to provide
> > drivers with a way of making sure that dpm_list is in the right order
> > -- people have been aware of these issues for some time.
> I saw those. I also notice that they are only used by device_move()
> when reparenting a device (which is another wrinkle I hadn't though
> about). Reparenting a device becomes problematic if the probe order
> is also represented in the list. If device_move() gets called, then
> any implicit probe-order sorting for that device would be lost.
> I also notice that device_move disregards any children when moving a
> device, which could also be a problem.
> Although it looks like the only users of device_move are:
> So it may not be significant to adapt.
I trust that very little will be needed. I haven't checked the
existing callers, but it's reasonable to require that a device being
moved not have any children.
More information about the linux-arm-kernel