From: Wolfram Sang <w.sang@pengutronix.de>
To: Robert Emanuele <rob@emanuele.us>
Cc: Linus Walleij <linus.ml.walleij@gmail.com>,
linux-arm-kernel <linux-arm-kernel@lists.infradead.org>,
linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: Controlling Driver Load Order
Date: Thu, 27 May 2010 06:13:58 +0200 [thread overview]
Message-ID: <20100527041358.GA14070@pengutronix.de> (raw)
In-Reply-To: <AANLkTikj8yGSK5Ovud_k8f6jWloojqDJmQ_H6pD_IFgM@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1542 bytes --]
On Wed, May 26, 2010 at 06:39:13PM -0700, Robert Emanuele wrote:
> Still the framebuffer device would initialize first and it would lack
> having the i2c chips it needs ready. That is the order I'm trying to
> straighten out.
Understood. Our pointers were probably not precise enough, sorry. Please try
this patch and give a Tested-by-tag if it solves your problems.
From: Wolfram Sang <w.sang@pengutronix.de>
Date: Thu, 27 May 2010 06:03:48 +0200
Subject: [PATCH] i2c-at91: use subsys_initcall() for early initialization
I2C needs to be available early, so other subsystems can access it.
Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
Cc: Robert Emanuele <rob@emanuele.us>
Cc: Ben Dooks <ben-linux@fluff.org>
---
drivers/i2c/busses/i2c-at91.c | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/i2c/busses/i2c-at91.c b/drivers/i2c/busses/i2c-at91.c
index 305c075..bea5794 100644
--- a/drivers/i2c/busses/i2c-at91.c
+++ b/drivers/i2c/busses/i2c-at91.c
@@ -313,13 +313,12 @@ static int __init at91_i2c_init(void)
{
return platform_driver_register(&at91_i2c_driver);
}
+subsys_initcall(at91_i2c_init);
static void __exit at91_i2c_exit(void)
{
platform_driver_unregister(&at91_i2c_driver);
}
-
-module_init(at91_i2c_init);
module_exit(at91_i2c_exit);
MODULE_AUTHOR("Rick Bronson");
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: Controlling Driver Load Order
Date: Thu, 27 May 2010 06:13:58 +0200 [thread overview]
Message-ID: <20100527041358.GA14070@pengutronix.de> (raw)
In-Reply-To: <AANLkTikj8yGSK5Ovud_k8f6jWloojqDJmQ_H6pD_IFgM@mail.gmail.com>
On Wed, May 26, 2010 at 06:39:13PM -0700, Robert Emanuele wrote:
> Still the framebuffer device would initialize first and it would lack
> having the i2c chips it needs ready. That is the order I'm trying to
> straighten out.
Understood. Our pointers were probably not precise enough, sorry. Please try
this patch and give a Tested-by-tag if it solves your problems.
From: Wolfram Sang <w.sang@pengutronix.de>
Date: Thu, 27 May 2010 06:03:48 +0200
Subject: [PATCH] i2c-at91: use subsys_initcall() for early initialization
I2C needs to be available early, so other subsystems can access it.
Signed-off-by: Wolfram Sang <w.sang@pengutronix.de>
Cc: Robert Emanuele <rob@emanuele.us>
Cc: Ben Dooks <ben-linux@fluff.org>
---
drivers/i2c/busses/i2c-at91.c | 3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/i2c/busses/i2c-at91.c b/drivers/i2c/busses/i2c-at91.c
index 305c075..bea5794 100644
--- a/drivers/i2c/busses/i2c-at91.c
+++ b/drivers/i2c/busses/i2c-at91.c
@@ -313,13 +313,12 @@ static int __init at91_i2c_init(void)
{
return platform_driver_register(&at91_i2c_driver);
}
+subsys_initcall(at91_i2c_init);
static void __exit at91_i2c_exit(void)
{
platform_driver_unregister(&at91_i2c_driver);
}
-
-module_init(at91_i2c_init);
module_exit(at91_i2c_exit);
MODULE_AUTHOR("Rick Bronson");
--
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/0ac368f0/attachment.sig>
next prev parent reply other threads:[~2010-05-27 4:13 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-26 19:08 Controlling Driver Load Order Robert Emanuele
2010-05-26 19:08 ` Robert Emanuele
2010-05-26 21:04 ` Linus Walleij
2010-05-26 21:04 ` Linus Walleij
2010-05-26 21:04 ` Linus Walleij
2010-05-26 21:04 ` Linus Walleij
2010-05-26 23:52 ` Wolfram Sang
2010-05-26 23:52 ` Wolfram Sang
2010-05-27 1:33 ` Robert Emanuele
2010-05-27 1:33 ` Robert Emanuele
2010-05-27 1:39 ` Robert Emanuele
2010-05-27 1:39 ` Robert Emanuele
2010-05-27 4:13 ` Wolfram Sang [this message]
2010-05-27 4:13 ` Wolfram Sang
[not found] ` <20100527041358.GA14070-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-05-27 17:07 ` Robert Emanuele
2010-05-27 17:07 ` Robert Emanuele
2010-05-27 17:07 ` Robert Emanuele
2010-05-27 21:01 ` Wolfram Sang
2010-05-27 21:01 ` Wolfram Sang
2010-05-27 21:09 ` Ryan Mallon
2010-05-27 21:09 ` Ryan Mallon
2010-05-27 21:42 ` Wolfram Sang
2010-05-27 21:42 ` Wolfram Sang
[not found] ` <20100527214209.GC5636-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2010-05-27 21:54 ` Ryan Mallon
2010-05-27 21:54 ` Ryan Mallon
2010-05-27 21:54 ` Ryan Mallon
[not found] ` <4BFEEA08.70401-7Wk5F4Od5/oYd5yxfr4S2w@public.gmane.org>
2010-05-27 22:09 ` Wolfram Sang
2010-05-27 22:09 ` Wolfram Sang
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=20100527041358.GA14070@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rob@emanuele.us \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.