[PATCH 1/9] spi/pxa2xx: don't use subys initcall for driver init

[Grant Likely]

On Wed, Nov 24, 2010 at 7:16 AM, Mark Brown
<broonie at opensource.wolfsonmicro.com> wrote:
> On Wed, Nov 24, 2010 at 03:09:25PM +0100, Sebastian Andrzej Siewior wrote:
>
>> I've been pointed out to this commit but I don't understand _why_.
>> The part I don't get is "so it can be used with cpufreq". Is it
>> refered to a driver or the subsystem as it?
>
> We need the regulators for the CPU rails to start before the cpufreq
> driver starts so cpufreq can talk to them, and since the regulators may
> be SPI attached this means we also need the SPI controller to start
> before cpufreq.  cpufreq starts at vanilla init time.
>
> There's an approach being looked at for handling this for devices but
> for deviceless stuff like cpufreq we've nothing.

It would be easy enough to defer cpufreq initialization based on some
platform defined criteria.  It's just an initcall.  However, I don't
know what the impact area is for subsystems that depend on cpufreq.
Are there drivers that depend on cpufreq before initialized?

g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.