From: Scott Wood <scottwood@freescale.com>
To: Olof Johansson <olof@lixom.net>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [PATCH v2] pasemi: process i2c device tree entries at boot
Date: Tue, 16 Oct 2007 11:21:25 -0500 [thread overview]
Message-ID: <4714E505.3080801@freescale.com> (raw)
In-Reply-To: <20071016001701.GA25444@lixom.net>
Olof Johansson wrote:
> On Mon, Oct 15, 2007 at 05:54:51PM -0500, Scott Wood wrote:
>> Olof Johansson wrote:
>>> Setup i2c_board_info based on device tree contents. This has to be
>>> a device_initcall since we need PCI to be probed by the time we
>>> run it, but before the actual driver is initialized.
>> Can we factor at least some of this stuff out into common code?
>
> I didn't really feel strong motivations to do so, given that the amount
> of shared code is quite small, and the official bindings are not yet
> determined.
Enh... I'm just irked because I originally did it in a generic manner,
and whoever it was that did further work on my patch shoved in into
fsl_soc. :-P
> Chances are whenever the bindings are done they might be incompatible
> with what we already have in our firmware, so the code would need to be
> separated out again.
Well, then it'd be better to just have one bit of code to fix, right? :-)
It'd suck to see different i2c controllers end up implementing the
binding differently due to the forking, though. Already with this
patch, we have a different set of i2c devices that will be recognized
depending on the adapter.
-Scott
prev parent reply other threads:[~2007-10-16 19:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-15 1:52 [PATCH] pasemi: process i2c device tree entries at boot Olof Johansson
2007-10-15 22:49 ` [PATCH v2] " Olof Johansson
2007-10-15 22:54 ` Scott Wood
2007-10-16 0:17 ` Olof Johansson
2007-10-16 16:21 ` Scott Wood [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=4714E505.3080801@freescale.com \
--to=scottwood@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.