linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Jon Smirl" <jonsmirl@gmail.com>
To: "Jean Delvare" <khali@linux-fr.org>
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 13:06:37 -0400	[thread overview]
Message-ID: <9e4733910807011006t20c7689ctfe26931f96c84092@mail.gmail.com> (raw)
In-Reply-To: <20080701190151.76782bbd@hyperion.delvare>

On 7/1/08, Jean Delvare <khali@linux-fr.org> wrote:
> On Tue, 1 Jul 2008 10:45:18 -0600, Grant Likely wrote:
>  > On Tue, Jul 01, 2008 at 06:29:49PM +0200, Jean Delvare wrote:
>  > > On Tue, 1 Jul 2008 11:12:58 -0400, Jon Smirl wrote:
>  > > > On 7/1/08, Jean Delvare <khali@linux-fr.org> wrote:
>  > > > > I'm fine with this patch. In particular, exporting i2c_bus_type is OK.
>  > > > >  It was un-exported only because it had no user left, but it can be
>  > > > >  exported again if needed.
>  > > >
>  > > > Another solution would be to move drivers/of/of_i2c into the i2c
>  > > > directory and make it part of i2c core on powerpc builds.
>  > >
>  > > I don't think this is a good idea. Merging arch-specific code (or
>  > > half-arch-specific code in this case) into arch-neutral drivers ends up
>  > > being a pain to maintain. People will keep sending me patches for stuff
>  > > I don't know anything about and can't help with. Having of-specific
>  > > stuff in just one directory as is the case now sounds much better to
>  > > me. All it's missing is a MAINTAINERS entry.
>  >
>  > But the other side of the coin is that each driver must have
>  > driver-specific OF code to translate data in the device tree to data
>  > usable by the driver.  It doesn't make any sense to me for that stuff to
>  > live anywhere other that with the driver that it supports.
>
>
> This code is glue between OF and subsystems. As with any glue code, you
>  can argue forever on which side you want to push the code to. Both
>  answers are valid.
>
>  All I see on my personal side is that I don't have any system using OF
>  and no knowledge about it either, so I can't maintain of_i2c. So having
>  that file in drivers/of rather than drivers/i2c will make my life
>  easier for sure. While I'd guess that most (all?) OF-based systems have
>  an I2C bus, so whoever is responsible for drivers/of should be able to
>  maintain of_i2c.

We could modify the Makefile for i2c core to get the source out of
drivers/of and link it into i2c-core. That would remove the need to
export symbols.

Or you could move the file into the i2c directory and just put a note
on it that Grant is the maintainer.


>
>  --
>
> Jean Delvare
>


-- 
Jon Smirl
jonsmirl@gmail.com

  reply	other threads:[~2008-07-01 17:06 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 [this message]
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
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=9e4733910807011006t20c7689ctfe26931f96c84092@mail.gmail.com \
    --to=jonsmirl@gmail.com \
    --cc=Linuxppc-dev@ozlabs.org \
    --cc=i2c@lm-sensors.org \
    --cc=khali@linux-fr.org \
    --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).