linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Sean MacLennan <smaclennan@pikatech.com>
Cc: linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: [RFC] Non-numbered ibm iic driver
Date: Sat, 28 Jun 2008 22:31:11 -0600	[thread overview]
Message-ID: <20080629043111.GB13658@secretlab.ca> (raw)
In-Reply-To: <20080628234339.382f31ac@lappy.seanm.ca>

On Sat, Jun 28, 2008 at 11:43:39PM -0400, Sean MacLennan wrote:
> On Sat, 28 Jun 2008 23:25:05 -0400
> "Jon Smirl" <jonsmirl@gmail.com> wrote:
> 
> > On 6/28/08, Sean MacLennan <smaclennan@pikatech.com> wrote:
> > > This is a patch to the ibm iic driver that uses the non-numbered
> > >  i2c call and therefore does not need an index. Instead, it
> > > registers the ibm iic, then walks all the child nodes and adds
> > > them. This is required for new style drivers, old style drivers
> > > "just work".
> > 
> > Check out the code in drivers/of/of_i2c.c. Can you use it instead?
> 
> Sure can. The for loop can be replaced with:
> 
> 	of_register_i2c_devices(adap, np);
> 
> I have tested it and it works. I guess it makes sense to put of_i2c.c
> under drivers/of, but if it had been under drivers/i2c, I would have
> noticed it ;)
> 
> But is this the way we want to go? I personally like it. It gets rid of
> the index and gets rid of the i2c_register_board_info() from the
> platform code.

Oops, forgot to include the list on my first reply...

Yes, this is the way to go.  I've got a patch that does the same thing
for SPI busses which I need to post for 2nd review.

g.

  reply	other threads:[~2008-06-29  4:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-29  3:20 [RFC] Non-numbered ibm iic driver Sean MacLennan
2008-06-29  3:25 ` Jon Smirl
2008-06-29  3:43   ` Sean MacLennan
2008-06-29  4:31     ` Grant Likely [this message]
2008-06-29 18:52 ` Jon Loeliger

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=20080629043111.GB13658@secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=smaclennan@pikatech.com \
    /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).