From: Jean Delvare <khali@linux-fr.org>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: Linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
i2c@lm-sensors.org
Subject: Re: [PATCH 2/2] Add the of_find_i2c_device_by_node function, V4
Date: Tue, 1 Jul 2008 18:35:09 +0200 [thread overview]
Message-ID: <20080701183509.0d2f0274@hyperion.delvare> (raw)
In-Reply-To: <9e4733910807010929k7088f97ekbadf854c949fbc64@mail.gmail.com>
On Tue, 1 Jul 2008 12:29:29 -0400, Jon Smirl wrote:
> On 7/1/08, Jean Delvare <khali@linux-fr.org> wrote:
> > Hi Jon,
> >
> >
> > On Mon, 30 Jun 2008 19:01:28 -0400, Jon Smirl wrote:
> > > Add the of_find_i2c_device_by_node function. This allows you to
> > > follow a reference in the device to an i2c device node and then
> > > locate the linux device instantiated by the device tree. Example
> > > use, an i2s codec controlled by i2c.
> > > ---
> > >
> > > drivers/i2c/i2c-core.c | 2 +-
> > > drivers/of/of_i2c.c | 37 ++++++++++++++++++++++++++-----------
> > > include/linux/i2c.h | 3 +++
> > > include/linux/of_i2c.h | 2 ++
> > > 4 files changed, 32 insertions(+), 12 deletions(-)
> > >
> > > diff --git a/drivers/i2c/i2c-core.c b/drivers/i2c/i2c-core.c
> > > index d0175f4..e3abe1b 100644
> > > --- a/drivers/i2c/i2c-core.c
> > > +++ b/drivers/i2c/i2c-core.c
> > > @@ -208,7 +208,7 @@ static struct device_attribute i2c_dev_attrs[] = {
> > > { },
> > > };
> > >
> > > -static struct bus_type i2c_bus_type = {
> > > +struct bus_type i2c_bus_type = {
> > > .name = "i2c",
> > > .dev_attrs = i2c_dev_attrs,
> > > .match = i2c_device_match,
> >
> >
> > What if i2c-core is built as a module? Don't you need to export the
> > symbol then?
>
> Jean, can you re-export i2c_bus_type and then I'll drop that part from
> the patch? That way the patch won't hit multiple maintainers.
Just send me a patch doing just that and I will be glad to push early in
the 2.6.27 merge window.
--
Jean Delvare
next prev parent reply other threads:[~2008-07-01 16:35 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-30 23:01 [PATCH 1/2] Convert i2c-mpc from a platform driver into a of_platform driver, V4 Jon Smirl
2008-06-30 23:01 ` [PATCH 2/2] Add the of_find_i2c_device_by_node function, V4 Jon Smirl
2008-07-01 15:05 ` Jean Delvare
2008-07-01 15:12 ` Jon Smirl
2008-07-01 16:29 ` Jean Delvare
2008-07-01 16:38 ` Jon Smirl
2008-07-01 16:44 ` Jean Delvare
2008-07-01 16:45 ` Grant Likely
2008-07-01 17:01 ` Jean Delvare
2008-07-01 17:06 ` Jon Smirl
2008-07-01 18:24 ` Jean Delvare
2008-07-01 16:43 ` Grant Likely
2008-07-01 17:00 ` Jon Smirl
2008-07-01 17:12 ` Jean Delvare
2008-07-01 17:27 ` Jon Smirl
2008-07-01 18:18 ` Jon Smirl
2008-07-01 18:51 ` Jean Delvare
2008-07-01 15:48 ` Jochen Friedrich
2008-07-01 16:29 ` Jon Smirl
2008-07-01 16:35 ` Jean Delvare [this message]
2008-07-01 16:14 ` [PATCH 1/2] Convert i2c-mpc from a platform driver into a of_platform driver, V4 Jean Delvare
2008-07-02 13:33 ` [i2c] " Wolfram Sang
2008-07-02 14:36 ` Jean Delvare
2008-07-09 17:22 ` Grant Likely
2008-07-10 16:36 ` Timur Tabi
2008-07-11 18:12 ` Grant Likely
2008-07-11 18:45 ` Anton Vorontsov
2008-07-11 18:54 ` Grant Likely
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=20080701183509.0d2f0274@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=Linuxppc-dev@ozlabs.org \
--cc=i2c@lm-sensors.org \
--cc=jonsmirl@gmail.com \
--cc=paulus@samba.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).