From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: avorontsov@ru.mvista.com
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc-dev@ozlabs.org, Mingkai Hu <Mingkai.hu@freescale.com>
Subject: Re: [PATCH v1] Add support for getting device platform data to I2C device
Date: Wed, 07 Jan 2009 11:55:21 +1100 [thread overview]
Message-ID: <1231289721.14860.47.camel@pasglop> (raw)
In-Reply-To: <20081218174927.GA16574@oksana.dev.rtsoft.ru>
On Thu, 2008-12-18 at 20:49 +0300, Anton Vorontsov wrote:
> Exactly, this matters for non-embedded case. Why would I want totally
> unneeded I2C bindings built-in into my iBook kernel? ;-)
>
> >> And the solution that everybody seem to agree with (SPI driver example):
> >> http://lkml.org/lkml/2008/10/30/393
> >
> > Hmm, that doesn't seem to allow for any binding mechanism other than
> > internal and OF
>
> Yeah, not without hacks (though, we can do some sort of chained pdata
> handlers, thus we can allow other bindings mechanisms). But so far we
> don't have anything other than OF and "board files"/raw bindings (I can't
> actually imagine any other option).
>
> Both approaches have their cons, sure. The difference is: for the
> $subject approach we'll see the cons immediately, while in my approach
> the cons are theoretical.
So what's the situation with this patch ? In general, who should be
considered as "in charge" of the OF i2c stuff btw ?
Cheers,
Ben.
prev parent reply other threads:[~2009-01-07 0:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-18 2:14 [PATCH v1] Add support for getting device platform data to I2C device Mingkai Hu
2008-12-18 16:59 ` Anton Vorontsov
2008-12-18 17:20 ` Scott Wood
2008-12-18 17:49 ` Anton Vorontsov
2009-01-07 0:55 ` Benjamin Herrenschmidt [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=1231289721.14860.47.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=Mingkai.hu@freescale.com \
--cc=avorontsov@ru.mvista.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).