devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: Wolfram Sang <w.sang@pengutronix.de>,
	Linus Walleij <linus.walleij@linaro.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
	linux-arm-kernel@lists.infradead.org, linux-next@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Alessandro Rubini <rubini@gnudd.com>,
	Linus Walleij <linus.walleij@stericsson.com>,
	Stephen Warren <swarren@wwwdotorg.org>,
	Deepak Saxena <dsaxena@linaro.org>,
	devicetree-discuss@lists.ozlabs.org,
	Grant Likely <grant.likely@secretlab.ca>
Subject: Re: linux-next: manual merge of the arm-soc tree with the i2c-embedded tree
Date: Tue, 17 Jul 2012 15:22:22 +0100	[thread overview]
Message-ID: <20120717142222.GE4477@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <50057058.2060002@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 902 bytes --]

On Tue, Jul 17, 2012 at 03:02:00PM +0100, Lee Jones wrote:

> I'm sure sure this is relevant in the current case though, as the
> i2c properties proposed here are platform specific. What we're

I've not seen the specific example (though fankly it seems quite
surprising that there's anything other than bus speed that the platform
might want to configure for I2C...).

> discussing is some consolidation of property names, which I do
> support in theory. What I fear is that this driver will lack Device
> Tree functionality for yet another kernel version if it isn't
> resolved quickly.

Well, if checking the DT checky box is the important thing then just
adding an of_match_table ought to be enough?  It's fairly common for
platform data to have lots of stuff that's not used by most systems
so you can often cover 90% of systems with a very small subset of the 
configurability.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-07-17 14:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120710164130.f38e4d1673f925ddb13914c9@canb.auug.org.au>
     [not found] ` <20120712131231.GH2194@pengutronix.de>
     [not found]   ` <20120712131231.GH2194-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-07-14 21:34     ` linux-next: manual merge of the arm-soc tree with the i2c-embedded tree Linus Walleij
2012-07-16 10:17       ` Wolfram Sang
2012-07-16 11:31         ` Lee Jones
2012-07-16 13:00           ` Wolfram Sang
2012-07-16 13:55             ` Lee Jones
2012-07-17 13:06           ` Mark Brown
2012-07-17 13:30             ` Lee Jones
2012-07-17 13:35               ` Mark Brown
2012-07-17 14:02                 ` Lee Jones
2012-07-17 14:22                   ` Mark Brown [this message]
2012-07-17 14:52                     ` Lee Jones
     [not found]                       ` <50057C1A.80606-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2012-07-17 15:20                         ` Mark Brown
2012-07-18  5:33                           ` Shawn Guo
2012-07-18  9:59                             ` Mark Brown
2012-07-18 10:29                               ` Lee Jones
2012-07-18 10:33                                 ` Mark Brown
2012-07-18 10:43                                   ` Lee Jones
2012-07-18  7:35                           ` Lee Jones
2012-07-18 11:12                             ` Mark Brown
2012-07-18 11:24                               ` Lee Jones
2012-07-16 11:37         ` Linus Walleij
2012-07-16 12:35           ` Wolfram Sang
     [not found]             ` <20120716123550.GE17435-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2012-07-16 19:45               ` Linus Walleij
     [not found]                 ` <CACRpkdaMB-n7XYcxE8QtAm-WrGc2DR0krfTjQZCbvOL1HYep1Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-07-16 20:04                   ` Chris Ball
2012-07-17 13:10             ` Mark Brown

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=20120717142222.GE4477@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=arnd@arndb.de \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dsaxena@linaro.org \
    --cc=grant.likely@secretlab.ca \
    --cc=lee.jones@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=olof@lixom.net \
    --cc=rubini@gnudd.com \
    --cc=sfr@canb.auug.org.au \
    --cc=swarren@wwwdotorg.org \
    --cc=w.sang@pengutronix.de \
    /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).