From: Gary Thomas <gary@mlbassoc.com>
To: "linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: Initcall ordering
Date: Fri, 23 Apr 2010 15:54:17 -0600 [thread overview]
Message-ID: <4BD21709.7040500@mlbassoc.com> (raw)
In-Reply-To: <4BD1C317.5000909@mlbassoc.com>
On 04/23/2010 09:56 AM, Gary Thomas wrote:
> I'm having trouble with the I2C devices on my 8347 platform.
> The problem is that I2C device probe() functions are only called
> once, as the I2C bus is being initialized (in this case fsl_i2c_init())
> I have 2 devices on this bus, one device gets it's initcall
> before fsl_i2c_init, the second one does not :-( This means
> that the second device is never probed.
>
> What can I do about this? Has the problem been seen before?
> I can provide more data, as required.
>
> note: I'm currently using 2.6.28, but I will be moving to 2.6.32
> soon in case it matters, but I'd rather find/understand/fix this
> in 2.6.28 if possible.
A possibly related question: how can I2C devices work as
modules when the device address + probe info is in the device
tree? Given the behaviour I'm seeing (I2C device probes only
happen when the bus is enumerated), how is this supposed to
work?
... maybe I'm missing something fundamental?
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-04-23 21:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-23 15:56 Initcall ordering Gary Thomas
2010-04-23 21:54 ` Gary Thomas [this message]
2010-04-24 1:24 ` Wolfram Sang
2010-04-24 14:26 ` Gary Thomas
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=4BD21709.7040500@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=linuxppc-dev@lists.ozlabs.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).