From: Jean Delvare <khali@linux-fr.org>
To: Uli Luckas <u.luckas@road.de>
Cc: linux-kernel@vger.kernel.org, adaplas@gmail.com,
Linux I2C <i2c@lm-sensors.org>
Subject: Re: Frame buffers and early i2c
Date: Mon, 9 Jun 2008 20:52:12 +0200 [thread overview]
Message-ID: <20080609205212.4b0f1ba6@hyperion.delvare> (raw)
In-Reply-To: <200806091647.42757.u.luckas@road.de>
On Mon, 9 Jun 2008 16:47:42 +0200, Uli Luckas wrote:
> I am in the process of trying out a display connected to a colibri board's
> pxa frame buffer device. The display's power supply is switch through i2c.
>
> In order to use the frame buffer console I have i2c and pxafb compiled in.
>
> By default, the pxafb driver get's initialized before the i2c bus causing the
> display power up to fail.
>
> What do i2c people think about changing the link order here?
Why don't you ask on the i2c mailing list? Cc added.
Personally I have no objection, but dependencies can be tricky so
you'll have to be careful. video is early in the link order at the
moment.
> What do other frame buffer drivers handle the absence of i2c during early
> boot?
Interestingly enough, they appear to do fine, despite the linking
order. Maybe because i2c_init is a subsys_initcall() while framebuffer
drivers are initialized with module_init()? Then I'm not sure why your
own driver has a problem there.
--
Jean Delvare
next parent reply other threads:[~2008-06-09 18:52 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 ` Jean Delvare [this message]
[not found] ` <20080609205212.4b0f1ba6-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-09 21:59 ` Frame buffers and early i2c 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
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=20080609205212.4b0f1ba6@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=adaplas@gmail.com \
--cc=i2c@lm-sensors.org \
--cc=linux-kernel@vger.kernel.org \
--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