From: Scott Wood <scottwood@freescale.com>
To: Vitaly Bordug <vitb@kernel.crashing.org>
Cc: Olof Johansson <olof@lixom.net>,
Jean Delvare <khali@linux-fr.org>,
lkml <linux-kernel@vger.kernel.org>,
"linuxppc-dev@ozlabs.org" <linuxppc-dev@ozlabs.org>
Subject: Re: [PATCH][RFC][POWERPC] i2c: adds support for i2c bus on 8xx
Date: Wed, 25 Apr 2007 13:53:45 -0500 [thread overview]
Message-ID: <462FA3B9.5080008@freescale.com> (raw)
In-Reply-To: <462F8953.1020201@kernel.crashing.org>
Vitaly Bordug wrote:
> i2c && 8xx combo never work with 2.6 at least in mainstream. That's why
> related stuff were scheduled to removal by Jean even,
> before I came up with this stuff.
[snip]
>> This could all be done with an of_platform driver instead, and avoid
>> the above.
>> (Someone else already suggested that I believe).
>>
>>
>
> I know i know. But it was decided, while both ppc/ and powerpc/ wander
> around, platform devices way is preferrable.
The idea is to avoid regressions in arch/ppc; maintaining feature parity
isn't necessary. If, as you say above, 8xx i2c was already broken in
2.6 (even in arch/ppc), then I see no reason not to go to an of_device
right away.
> It is apparent why - so far only mpc885 is alive in arch/powerpc, and it
> is not going to change soon for 8xx.
Actually, I plan to do some arch/powerpc 8xx work over the next couple
months, so hopefully it will change soon. :-)
-Scott
prev parent reply other threads:[~2007-04-25 18:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 4:27 [PATCH][RFC][POWERPC] i2c: adds support for i2c bus on 8xx Vitaly Bordug
2007-04-20 8:57 ` Segher Boessenkool
2007-04-20 15:15 ` Milton Miller
2007-04-21 7:57 ` [PATCH][RFC] " Jean Delvare
2007-04-22 11:29 ` Vitaly Bordug
2007-04-23 9:19 ` Jean Delvare
2007-04-25 17:06 ` Vitaly Bordug
2007-04-26 15:54 ` Jean Delvare
2007-04-26 16:07 ` Vitaly Bordug
2007-04-23 2:57 ` [PATCH][RFC][POWERPC] " Olof Johansson
2007-04-25 17:01 ` Vitaly Bordug
2007-04-25 18:53 ` 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=462FA3B9.5080008@freescale.com \
--to=scottwood@freescale.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=olof@lixom.net \
--cc=vitb@kernel.crashing.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).