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 for Android: free password hash cracker in your pocket

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

Message-ID: <AANLkTinkY8JYh44UOEPflBUDyQ2wat_AKShRjA3HPxrf@mail.gmail.com>
Date:	Wed, 26 May 2010 23:04:01 +0200
From:	Linus Walleij <linus.ml.walleij@...il.com>
To:	Robert Emanuele <rob@...nuele.us>
Cc:	linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
	linux-kernel@...r.kernel.org
Subject: Re: Controlling Driver Load Order

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().

You find the different init levels in include/linux/init.h

Yours,
Linus Walleij
--
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/