[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4BFEDF6D.3090100@bluewatersys.com>
Date: Fri, 28 May 2010 09:09:01 +1200
From: Ryan Mallon <ryan@...ewatersys.com>
To: Robert Emanuele <rob@...nuele.us>
CC: Wolfram Sang <w.sang@...gutronix.de>,
Linus Walleij <linus.ml.walleij@...il.com>,
linux-kernel@...r.kernel.org,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
linux-i2c@...r.kernel.org
Subject: Re: Controlling Driver Load Order
Robert Emanuele wrote:
> Hi Wolfram,
>
> I am using the i2c-gpio.c driver, not the i2c-at91 driver. The Atmel
> folks have expressed concerns over their i2c silicon and wrote a gpio
> version.
>
> Anyway, I better understand the subsys_initcall now and applied that
> to the i2c-gpio and my i2c chip driver. That worked perfectly for my
> issue. I'd be happy to return a patch of this. Would be this the
> sort of thing that would benefit from a config option? Something
> like:
>
> #if defined(CONFIG_EARLY_i2C_GPIO)
> subsys_initcall(i2c_gpio_init);
> #else
> module_init(i2c_gpio_init);
> #endif
Looks like this has already been done:
http://www.mail-archive.com/linux-i2c@vger.kernel.org/msg03056.html
There was a discussion a while back to make all of the embedded i2c
busses be subsys_initcall since i2c is often a system bus on embedded
devices. Looks the i2c_gpio driver got missed the first time round.
~Ryan
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon 5 Amuri Park, 404 Barbadoes St
ryan@...ewatersys.com PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com New Zealand
Phone: +64 3 3779127 Freecall: Australia 1800 148 751
Fax: +64 3 3779135 USA 1800 261 2934
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists