All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang@pengutronix.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-embedded@vger.kernel.org, linuxppc-dev@ozlabs.org,
	linux-i2c@vger.kernel.org, devicetree-discuss@ozlabs.org
Subject: Re: [RFC] misc/at24: add experimental OF support for the generic eeprom driver
Date: Thu, 8 Oct 2009 22:27:23 +0200	[thread overview]
Message-ID: <20091008202723.GA8116@pengutronix.de> (raw)
In-Reply-To: <fa686aa40910080848r459c47baob73fc70a95a08604@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1250 bytes --]

> No, this goes beyond PPC/OF.  The real issue is that it is no longer a
> safe assumption that pdata will be a static data structure in platform
> code.  The number of possible data sources is going to get larger, not
> smaller.  OF is just one.  UEFI is another.  Translating that data
> into pdata will be the problem that comes up over and over again.
> However, translation code is still driver specific, so it belongs with
> the driver that it translates code for.
> 
> So, in my opinion, translation code must:
> 1. be *tiny* -- should be trivial to add to a driver without impacting
> common code
> 2. live with the driver that it translates data for; ideally in the
> same .c file for drivers that are small.

I am with Grant on these points. It is more than just PPC.

> > 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.

Will check this tomorrow.

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

[-- Attachment #2: Type: text/plain, Size: 150 bytes --]

_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev

WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <w.sang@pengutronix.de>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-embedded@vger.kernel.org, linuxppc-dev@ozlabs.org,
	linux-i2c@vger.kernel.org, devicetree-discuss@ozlabs.org
Subject: Re: [RFC] misc/at24: add experimental OF support for the generic eeprom driver
Date: Thu, 8 Oct 2009 22:27:23 +0200	[thread overview]
Message-ID: <20091008202723.GA8116@pengutronix.de> (raw)
In-Reply-To: <fa686aa40910080848r459c47baob73fc70a95a08604@mail.gmail.com>

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

> No, this goes beyond PPC/OF.  The real issue is that it is no longer a
> safe assumption that pdata will be a static data structure in platform
> code.  The number of possible data sources is going to get larger, not
> smaller.  OF is just one.  UEFI is another.  Translating that data
> into pdata will be the problem that comes up over and over again.
> However, translation code is still driver specific, so it belongs with
> the driver that it translates code for.
> 
> So, in my opinion, translation code must:
> 1. be *tiny* -- should be trivial to add to a driver without impacting
> common code
> 2. live with the driver that it translates data for; ideally in the
> same .c file for drivers that are small.

I am with Grant on these points. It is more than just PPC.

> > 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.

Will check this tomorrow.

-- 
Pengutronix e.K.                           | Wolfram Sang                |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

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

  reply	other threads:[~2009-10-08 20:27 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
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 [this message]
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=20091008202723.GA8116@pengutronix.de \
    --to=w.sang@pengutronix.de \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-embedded@vger.kernel.org \
    --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.