Re: [PATCH] i2c-mv64xxx: use subsys_initcall for early initialization

[Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>]

On Thu, Sep 23, 2010 at 09:11:00AM +0200, Linus Walleij wrote:
> 2010/9/15 Ben Dooks <ben-i2c-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>:
> > On Sun, Sep 12, 2010 at 11:35:29AM +0200, Mike Rapoport wrote:
> >> Signed-off-by: Mike Rapoport <mike-UTxiZqZC01RS1MOuV/RT9w@public.gmane.org>
> >> ---
> >>  drivers/i2c/busses/i2c-mv64xxx.c |    2 +-
> >>  1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > We really should have an i2c_initcall, but it may be difficult to move
> > everyone over to it. What would be lovely is some form of dependency
> > based initialisation, but that's probably a way off...
> 
> SPI, SDIO and other external busses (Dallas 1-wire? w1) may all have
> the same "needs to be up early because we need that before that"
> type of problem.
> 
> Makes me think of crazy things like putting a lightweight version of
> Lennars Pötterings "systemd" scheme into the kernel for resolving
> these initcalls.

Either that, or build stuff as modules and use an initrd...

Not sure what the best solution is...

-- 
Ben

Q:      What's a light-year?
A:      One-third less calories than a regular year.