From: Michael Lawnick <ml.lawnick-Mmb7MZpHnFY@public.gmane.org>
To: guenter.roeck-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org
Cc: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Using the gpio i2c multiplexer driver
Date: Wed, 16 Feb 2011 08:07:26 +0100 [thread overview]
Message-ID: <4D5B77AE.20307@gmx.de> (raw)
In-Reply-To: <1297810054.24938.218.camel@groeck-laptop>
Guenter Roeck said the following:
> Hi all,
>
> I am trying to use the new GPIO based I2C multiplexer. Unfortunately, I
> have an initialization problem with it.
>
> Some time after registering the multiplexer as platform driver, its
> probe function is called. Unfortunately, that does not happen in sync
> with I2C adapter initialization. The GPIO mux probe function is called
> before the parent's (ie the multiplexed I2C adapter) probe function is
> called. As a result, the GPIO mux driver does not find its parent i2c
> adapter, and the probe function aborts with an error.
>
> Any idea how I I can fix the problem, ie how I can ensure that the GPIO
> mux probe function is only called after its parent I2C adapter is
> initialized ?
>
Well, I assume your GPIO-Mux is registered as an GPIO device? Can't you
add it as an I2C-device? This way the right sequence should be kept.
HTH
--
Michael
next prev parent reply other threads:[~2011-02-16 7:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-15 22:47 Using the gpio i2c multiplexer driver Guenter Roeck
2011-02-16 7:07 ` Michael Lawnick [this message]
[not found] ` <4D5B77AE.20307-Mmb7MZpHnFY@public.gmane.org>
2011-02-16 14:29 ` Guenter Roeck
2011-02-16 8:13 ` Peter Korsgaard
[not found] ` <87ei789z3g.fsf-uXGAPMMVk8amE9MCos8gUmSdvHPH+/yF@public.gmane.org>
2011-02-16 14:28 ` Guenter Roeck
2011-02-16 23:50 ` Guenter Roeck
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=4D5B77AE.20307@gmx.de \
--to=ml.lawnick-mmb7mzphnfy@public.gmane.org \
--cc=guenter.roeck-IzeFyvvaP7pWk0Htik3J/w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.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).