From: Anton Vorontsov <avorontsov@ru.mvista.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linuxppc-dev@ozlabs.org, devicetree-discuss@ozlabs.org,
linux-i2c@vger.kernel.org
Subject: Re: [RFC] misc/at24: add experimental OF support for the generic eeprom driver
Date: Thu, 8 Oct 2009 19:10:07 +0400 [thread overview]
Message-ID: <20091008151007.GA21328@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <fa686aa40910080753v6f597b0h4ce835db9f7a653@mail.gmail.com>
On Thu, Oct 08, 2009 at 08:53:46AM -0600, Grant Likely wrote:
[...]
> Please don't. It is such a small amount of code,
It's *always* a small amound of code, at a start. Then we get
floppy disk drivers and the tty layer. ;-)
[...]
> Driver writers shouldn't have to
> write anything more than a tiny function to populate pdata from the
> device tree. Managing that pdata instance needs to be done with
> common infrastructure (but I don't have a firm idea about how it
> should look yet). In the mean time I think Wolfram's approach has
> lower impact.
If I wasn't a PPC/OF guy to some degree, I'd hate PPC/OF people
for bringing arch-specific details into a generic code... :-P
No matter how small the OF code is, I believe we shouldn't put it
into the generic code. Take a look at mmc_spi case again, it can be
easily extended to any arch, because there is no arch-specific stuff,
but a "get/put" pattern for platform data.
Thanks,
--
Anton Vorontsov
email: cbouatmailru@gmail.com
irc://irc.freenode.net/bd2
next prev parent reply other threads:[~2009-10-08 15:10 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-08 14:04 [RFC] misc/at24: add experimental OF support for the generic eeprom driver Wolfram Sang
2009-10-08 14:33 ` Anton Vorontsov
[not found] ` <20091008143301.GA6084-wnGakbxT3iijyJ0x5qLZdcN33GVbZNy3@public.gmane.org>
2009-10-08 14:53 ` Grant Likely
2009-10-08 14:53 ` Grant Likely
2009-10-08 15:10 ` Anton Vorontsov [this message]
2009-10-08 15:48 ` Grant Likely
2009-10-08 15:48 ` Grant Likely
2009-10-08 15:48 ` Grant Likely
2009-10-08 20:27 ` Wolfram Sang
2009-10-08 20:27 ` Wolfram Sang
2009-10-09 5:14 ` Wolfram Sang
2009-10-09 5:14 ` Wolfram Sang
[not found] ` <20091009051409.GA2361-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-10-09 5:40 ` Grant Likely
2009-10-09 5:40 ` Grant Likely
2009-10-09 5:40 ` Grant Likely
2009-10-09 14:01 ` Nate Case
2009-10-09 14:01 ` Nate Case
2009-10-09 16:09 ` Grant Likely
2009-10-09 16:09 ` Grant Likely
2009-10-09 16:09 ` Grant Likely
2009-10-09 16:20 ` Wolfram Sang
2009-10-09 16:20 ` Wolfram Sang
2009-10-09 13:43 ` Nate Case
2009-10-09 16:12 ` Wolfram Sang
2009-10-09 16:12 ` Wolfram Sang
2009-10-09 16:13 ` Grant Likely
2009-10-09 16:13 ` Grant Likely
2009-10-09 16:13 ` Grant Likely
[not found] ` <fa686aa40910080848r459c47baob73fc70a95a08604-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-08 22:20 ` Anton Vorontsov
2009-10-08 22:20 ` Anton Vorontsov
2009-10-09 6:37 ` Grant Likely
2009-10-09 6:37 ` Grant Likely
2009-10-09 6:37 ` Grant Likely
2009-10-08 14:37 ` Grant Likely
[not found] ` <fa686aa40910080737l5b21654cw9c8f7426f9faf7c3-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-10-08 20:48 ` Wolfram Sang
2009-10-08 20:48 ` Wolfram Sang
[not found] ` <20091008204808.GB8116-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-10-08 22:59 ` Grant Likely
2009-10-08 22:59 ` Grant Likely
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=20091008151007.GA21328@oksana.dev.rtsoft.ru \
--to=avorontsov@ru.mvista.com \
--cc=devicetree-discuss@ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-i2c@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.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.