On Tuesday, October 20, 2015 08:35:28 PM Mark Brown wrote:

--7fVr/IRGAG9sAW4J
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 20, 2015 at 01:14:46PM -0400, Alan Stern wrote:

quoted

On Tue, 20 Oct 2015, Tomeu Vizoso wrote:

quoted

quoted

This iteration of the series would make this quite easy, as
dependencies are calculated before probes are attempted:

quoted

quoted

https://lkml.org/lkml/2015/6/17/311

quoted

But what Rafael is proposing is quite general; it would apply to _all_
dependencies as opposed to just those present in DT drivers or those=20
affecting platform_devices.

We'll still need most of the DT bits that are there at the minute (the
ones strewn around the subsystems) AFAICT since it's at the point where
we parse the DT and work out what the dependencies are which we probably
want to do prior to getting the drivers up and will be different for
ACPI.  I think the level of DT dependency here looks a lot larger than
it actually is due to the fact that a lot of what's being modified is DT
parsing code.

Right, something will have to register the dependency, or a "link" between
devices, with the core once we find out that the dependency is there.

Thanks,
Rafael