From: Jean Delvare <khali@linux-fr.org>
To: "Mike Frysinger" <vapier.adi@gmail.com>
Cc: "Bryan Wu" <bryan.wu@analog.com>,
"David Brownell" <david-b@pacbell.net>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Alexey Dobriyan" <adobriyan@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 4/4] Blackfin: on-chip Two Wire Interface I2C driver
Date: Thu, 22 Mar 2007 10:24:31 +0100 [thread overview]
Message-ID: <20070322102431.b55f7ecd.khali@linux-fr.org> (raw)
In-Reply-To: <8bd0f97a0703220112y7d6cef2ax612ea5ece3df9740@mail.gmail.com>
On Thu, 22 Mar 2007 04:12:37 -0400, Mike Frysinger wrote:
> it isnt obvious to me how to leverage the normal platform_device and
> resource structures to achieve moving the class out of the driver and
> into a boards file ... i'm perfectly happy doing this knowing what the
> correct direction to take things ... but i guess this gets us back to
> if no one is doing this yet and no one has any proposals, it's on our
> shoulders to get it resolved satisfactorily
I'd say: leave things as they are, if a problem arises, we'll see how
to fix it. By then, the new i2c driver model will be in mainline, which
will gives us a nicer way to address the problem.
> i might also argue (for fun) that some of the bus drivers arent doing
> it correctly ... they should implement support for the specific I2C
> implementation and then a different file for the specific
> [mother]board would contain the specific details
This sounds easy when you're in the embedded world. Now come and try to
support the literally thousands of different PC motherboard models out
there that way!
--
Jean Delvare
next prev parent reply other threads:[~2007-03-22 9:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-21 10:08 [PATCH -mm 4/4] Blackfin: on-chip Two Wire Interface I2C driver Wu, Bryan
2007-03-21 17:56 ` Jean Delvare
2007-03-21 18:17 ` Bob Copeland
2007-03-21 19:14 ` Mike Frysinger
2007-03-22 7:03 ` Jean Delvare
2007-03-22 7:13 ` Mike Frysinger
2007-03-21 19:22 ` Jean Delvare
2007-03-22 5:39 ` Mike Frysinger
2007-03-22 7:48 ` Jean Delvare
2007-03-22 8:12 ` Mike Frysinger
2007-03-22 9:24 ` Jean Delvare [this message]
2007-03-23 5:46 ` [PATCH -mm try#2] " Wu, Bryan
2007-03-23 7:27 ` Jean Delvare
2007-03-23 7:36 ` Wu, Bryan
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=20070322102431.b55f7ecd.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=adobriyan@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=bryan.wu@analog.com \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=vapier.adi@gmail.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