linux-kernel - Re: Controlling Driver Load Order

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 27 May 2010 01:52:46 +0200
From:	Wolfram Sang <w.sang@...gutronix.de>
To:	Linus Walleij <linus.ml.walleij@...il.com>
Cc:	Robert Emanuele <rob@...nuele.us>,
	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Controlling Driver Load Order

On Wed, May 26, 2010 at 11:04:01PM +0200, Linus Walleij wrote:
> 2010/5/26 Robert Emanuele <rob@...nuele.us>:
> 
> > On my at91sam9g45 platform I need my i2c drivers to load before the
> > framebuffer driver.  The i2c drivers control a power management IC
> > which is needed to enable the graphics controller.
> >
> > Is there a way to set up that order?
> 
> The usual trick (which you can find in a lot of other I2C busses) is to use
> a core_initcall() instead of module_init().

Correct, but it's subsys_initcall().

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

Download attachment "signature.asc" of type "application/pgp-signature" (198 bytes)