From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: Controlling Driver Load Order
Date: Thu, 27 May 2010 23:01:12 +0200 [thread overview]
Message-ID: <20100527210112.GA5636@pengutronix.de> (raw)
In-Reply-To: <AANLkTilKUfcYsPqr5kXlONJQAFCaE8D8U9ltQybIzCPu@mail.gmail.com>
> 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
With chip-driver you mean the PMIC? Yes, that is probably needed there, too.
Which driver is it?
> 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
Nope, there is no bigger drawback to this and probably a number of useres
wouldn't know what to select here. Just patch the module_init() away.
Kind regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100527/89732004/attachment.sig>
next prev parent reply other threads:[~2010-05-27 21:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 19:08 Controlling Driver Load Order Robert Emanuele
2010-05-26 21:04 ` Linus Walleij
2010-05-26 21:04 ` Linus Walleij
2010-05-26 23:52 ` Wolfram Sang
2010-05-27 1:33 ` Robert Emanuele
2010-05-27 1:39 ` Robert Emanuele
2010-05-27 4:13 ` Wolfram Sang
2010-05-27 17:07 ` Robert Emanuele
2010-05-27 21:01 ` Wolfram Sang [this message]
2010-05-27 21:09 ` Ryan Mallon
2010-05-27 21:42 ` Wolfram Sang
2010-05-27 21:54 ` Ryan Mallon
2010-05-27 22:09 ` Wolfram Sang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100527210112.GA5636@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).