public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Wolfram Sang <w.sang-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: platform_data when using of?
Date: Thu, 24 Apr 2008 11:00:45 +0200	[thread overview]
Message-ID: <20080424090045.GA4201@pengutronix.de> (raw)
In-Reply-To: <20080423203012.24ed38b6-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>


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

On Wed, Apr 23, 2008 at 08:30:12PM +0200, Jean Delvare wrote:

Hello Jean,

> Each i2c driver can support many different devices, which are
> differentiated simply by their name. So the driver can behave
> differently for each device type as needed.
We exactly threw this out of at24 in the new revision, as name-matching
stored quite some data in the driver which was needed only once during
initialization. Also, it was not very flexible; what if you want to mark
this chip as read-only, your variant has bigger page size and could be
faster... The list of device names would grow too fast IMHO, adding a
new feature which is selectable by a flag could easily double it.

Then again: If Jochen's patches get applied, then I have to use
MODULE_DEVICE_TABLE anyhow, or?

   Wolfram

-- 
  Dipl.-Ing. Wolfram Sang | http://www.pengutronix.de
 Pengutronix - Linux Solutions for Science and Industry

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

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

_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c

  parent reply	other threads:[~2008-04-24  9:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23 16:45 platform_data when using of? Wolfram Sang
2008-04-23 18:20 ` [i2c] " Jochen Friedrich
     [not found] ` <20080423164523.GA4190-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2008-04-23 18:30   ` Jean Delvare
     [not found]     ` <20080423203012.24ed38b6-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-04-24  9:00       ` Wolfram Sang [this message]
     [not found]         ` <20080424090045.GA4201-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2008-04-24 11:07           ` Jean Delvare

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=20080424090045.GA4201@pengutronix.de \
    --to=w.sang-bicnvbalz9megne8c9+irq@public.gmane.org \
    --cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.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