Re: A better way to sequence driver initialization?

2010-04-10 Thread Bill Gatliff
Paul Mundt wrote: > In some cases that might be valid, but there are many cases where drivers > can reconfigure their capability sets based on which GPIOs are and aren't > available. Just because a pin isn't available doesn't make it a > show-stopper for the probe path.. > Understood. I just t

Re: A better way to sequence driver initialization?

2010-04-10 Thread Paul Mundt
On Sat, Apr 10, 2010 at 08:33:53PM -0500, Bill Gatliff wrote: > Grant Likely wrote: > > On Sat, Apr 10, 2010 at 5:39 PM, Paul Mundt wrote: > > > >> In cases where you can specifically note that dependencies, doing so will > >> save you a world of pain. Despite that, it's simply not possible to

Re: A better way to sequence driver initialization?

2010-04-10 Thread Bill Gatliff
Grant Likely wrote: > On Sat, Apr 10, 2010 at 5:39 PM, Paul Mundt wrote: > >> In cases where you can specifically note that dependencies, doing so will >> save you a world of pain. Despite that, it's simply not possible to do >> this as a free-for-all. Devices or busses that can tolerate multi-

Re: A better way to sequence driver initialization?

2010-04-10 Thread Bill Gatliff
Paul Mundt wrote: > > In cases where you can specifically note that dependencies, doing so will > save you a world of pain. Despite that, it's simply not possible to do > this as a free-for-all. Devices or busses that can tolerate multi-threaded > probing need to be converted over one at a time, bu

Re: A better way to sequence driver initialization?

2010-04-10 Thread Grant Likely
On Sat, Apr 10, 2010 at 5:39 PM, Paul Mundt wrote: > In cases where you can specifically note that dependencies, doing so will > save you a world of pain. Despite that, it's simply not possible to do > this as a free-for-all. Devices or busses that can tolerate multi-threaded > probing need to be

Re: A better way to sequence driver initialization?

2010-04-10 Thread Paul Mundt
On Sat, Apr 10, 2010 at 08:35:41AM -0500, Bill Gatliff wrote: > Benjamin Herrenschmidt wrote: > > On Fri, 2010-04-09 at 14:23 -0500, Bill Gatliff wrote: > > > >> My recent post, "Requesting a GPIO that hasn't been registered yet", and > >> Anton's reply thereto (thanks, Anton!) on linuxppc-dev g

Re: A better way to sequence driver initialization?

2010-04-10 Thread Bill Gatliff
Grant Likely wrote: > On Fri, Apr 9, 2010 at 1:23 PM, Bill Gatliff wrote: > >> Guys: >> >> >> My recent post, "Requesting a GPIO that hasn't been registered yet", and >> Anton's reply thereto (thanks, Anton!) on linuxppc-dev got me thinking >> about the problem of dependencies between devices i

Re: A better way to sequence driver initialization?

2010-04-10 Thread Bill Gatliff
Benjamin Herrenschmidt wrote: > On Fri, 2010-04-09 at 14:23 -0500, Bill Gatliff wrote: > >> My recent post, "Requesting a GPIO that hasn't been registered yet", and >> Anton's reply thereto (thanks, Anton!) on linuxppc-dev got me thinking >> about the problem of dependencies between devices in d

Re: A better way to sequence driver initialization?

2010-04-10 Thread Benjamin Herrenschmidt
On Fri, 2010-04-09 at 14:23 -0500, Bill Gatliff wrote: > > My recent post, "Requesting a GPIO that hasn't been registered yet", and > Anton's reply thereto (thanks, Anton!) on linuxppc-dev got me thinking > about the problem of dependencies between devices in different classes, > and/or between d