From: Peter Korsgaard <jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org>
To: "Richard Röjfors"
<richard.rojfors.ext-l7gf1WXxx3uGw+nKnLezzg@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH 3/9] I2C: i2c-ocores: Can add I2C devices to the bus
Date: Fri, 05 Jun 2009 16:40:15 +0200 [thread overview]
Message-ID: <87k53qyca8.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4A292050.7010602-l7gf1WXxx3uGw+nKnLezzg@public.gmane.org> ("Richard Röjfors"'s message of "Fri\, 05 Jun 2009 15\:40\:32 +0200")
>>>>> "Richard" == Richard Röjfors <richard.rojfors.ext@mocean-labs.com> writes:
Richard> There is sometimes a need for the ocores driver to add
Richard> devices to the bus when installed.
Richard> i2c_register_board_info can not always be used, because the
Richard> I2C devices are not known at an early state, they could for
Richard> instance be connected on a I2C bus on a PCI device which has
Richard> the Open Cores IP.
Richard> i2c_new_device can not be used in all cases either since the
Richard> resulting bus nummer might be unknown.
Richard> The solution is the pass a list of I2C devices in the
Richard> platform data to the Open Cores driver. This is useful for
Richard> MFD drivers.
Richard> Signed-off-by: Richard Röjfors <richard.rojfors.ext@mocean-labs.com>
Acked-by: Peter Korsgaard <jacmet-OfajU3CKLf1/SzgSGea1oA@public.gmane.org>
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2009-06-05 14:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-05 13:40 [PATCH 3/9] I2C: i2c-ocores: Can add I2C devices to the bus Richard Röjfors
[not found] ` <4A292050.7010602-l7gf1WXxx3uGw+nKnLezzg@public.gmane.org>
2009-06-05 14:40 ` Peter Korsgaard [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=87k53qyca8.fsf@macbook.be.48ers.dk \
--to=jacmet-ofaju3cklf1/szgsgea1oa@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=richard.rojfors.ext-l7gf1WXxx3uGw+nKnLezzg@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