public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: Uli Luckas <u.luckas@road.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	adaplas@gmail.com, Linux I2C <i2c@lm-sensors.org>,
	Ryan Mallon <ryan@bluewatersys.com>,
	David Brownell <david-b@pacbell.net>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Eric Miao <eric.y.miao@gmail.com>
Subject: Re: Frame buffers and early i2c
Date: Tue, 10 Jun 2008 12:57:37 +0200	[thread overview]
Message-ID: <20080610125737.0622da44@hyperion.delvare> (raw)
In-Reply-To: <200806101131.19763.u.luckas@road.de>

On Tue, 10 Jun 2008 11:31:19 +0200, Uli Luckas wrote:
> On Tuesday, 10. June 2008, Jean Delvare wrote:
> > So you prefer to post to one random list than the two lists where your
> > target audience is? Interesting approach. If you really don't want to
> > post to two lists at once, just send two separate posts?
> >
> And have two seperate threads of communication??? lfml is where they all are 
> and avery maintainer has different preferences. Anyway, I got your point and 
> will come to the i2c list in the future if you prefere.

If you believe that every kernel developer reads LKML, you're seriously
mistaken. We have a hundred of dedicated mailing lists for a reason. I
would have missed your post if you hadn't Cc'd directly.

> Just changing the initcall to subsys really did the trick. I thought, this was 
> the first thing I tried and I thought it crashed my device. But obviousely I 
> had some other problem.
> If Russell gives his Ack, could this be pushed upstream through i2c?
> (...)
> Initialize the pxa i2c bus during subsystem initialization to make it
> available during driver initialization (e.g. display powerup for pxafb).
> 
> Signed-off-by: Uli Luckas <u.luckas@road.de>
> ---
>  drivers/i2c/busses/i2c-pxa.c |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/drivers/i2c/busses/i2c-pxa.c b/drivers/i2c/busses/i2c-pxa.c
> index eb69fba..78c0fc4 100644
> --- a/drivers/i2c/busses/i2c-pxa.c
> +++ b/drivers/i2c/busses/i2c-pxa.c
> @@ -1134,5 +1134,5 @@ static void __exit i2c_adap_pxa_exit(void)
>  MODULE_LICENSE("GPL");
>  MODULE_ALIAS("platform:pxa2xx-i2c");
>  
> -module_init(i2c_adap_pxa_init);
> +subsys_initcall(i2c_adap_pxa_init);
>  module_exit(i2c_adap_pxa_exit);

That's fine with me.

-- 
Jean Delvare

      parent reply	other threads:[~2008-06-10 10:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200806091647.42757.u.luckas@road.de>
2008-06-09 18:52 ` Frame buffers and early i2c Jean Delvare
     [not found]   ` <20080609205212.4b0f1ba6-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-09 21:59     ` Uli Luckas
2008-06-10  6:25       ` Jean Delvare
2008-06-10  9:31         ` Uli Luckas
2008-06-10 10:02           ` [i2c] " Ben Dooks
2008-06-10 10:18             ` Jean Delvare
2008-06-10 11:47             ` Uli Luckas
2008-06-10 10:57           ` Jean Delvare [this message]

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=20080610125737.0622da44@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=adaplas@gmail.com \
    --cc=david-b@pacbell.net \
    --cc=eric.y.miao@gmail.com \
    --cc=i2c@lm-sensors.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=ryan@bluewatersys.com \
    --cc=u.luckas@road.de \
    /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