public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: David Brownell <david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
Cc: Linux I2C <i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org>
Subject: Re: [PATCH 2/3] i2c: Let bus drivers add SPD to their class
Date: Wed, 4 Jun 2008 08:09:33 +0200	[thread overview]
Message-ID: <20080604080933.456c8ce2@hyperion.delvare> (raw)
In-Reply-To: <200806031319.56606.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>

Hi David,

Thanks for the feedback.

On Tue, 3 Jun 2008 13:19:56 -0700, David Brownell wrote:
> On Tuesday 03 June 2008, Jean Delvare wrote:
> > 
> > Note that I took a conservative approach here, adding I2C_CLASS_SPD to
> > all drivers that had I2C_CLASS_HWMON before. This is to make sure that
> > the eeprom driver doesn't stop probing buses where SPD EEPROMs live.
> > But the truth is that, for most of these, I simply have no idea whether
> > they can host SPD EEPROMs or not.
> 
> Few embedded platforms use discrete sticks of DRAM.
> My two cents:  use the opposite default in those cases.

I wish I knew which of these bus drivers exactly are for embedded
platforms. Would you be able to give me a list of all drivers under
drivers/i2c/busses that fall in this category? I would be able to update
http://lists.lm-sensors.org/pipermail/i2c/2008-May/003713.html
then.

Also, couldn't these platforms have other EEPROMs on these buses,
either EDID EEPROMs or proprietary ones, for which people might be
using the read-only eeprom driver at the moment? I don't want users to
experience a regression by applying this patch set. I'd rather have
them migrate their platform to the at24 driver once it is upstream and
remove the I2C_CLASS_SPD flag when they do.

> 
> I'll highlight a few below, where I happen to have more
> specific knowledge.
> 
> 
> > So, bus driver maintainers and users 
> > should feel free to remove the SPD class from drivers those buses never
> > have SPD EEPROMs or they don't want the eeprom driver to bind to them.
> > Likewise, feel free to add the SPD class to any bus driver I might have
> > missed.
> > 
> > Signed-off-by: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
> > ---
> >  drivers/i2c/busses/i2c-ali1535.c       |    2 +-
> >  drivers/i2c/busses/i2c-ali1563.c       |    2 +-
> >  drivers/i2c/busses/i2c-ali15x3.c       |    2 +-
> >  drivers/i2c/busses/i2c-amd756.c        |    2 +-
> >  drivers/i2c/busses/i2c-amd8111.c       |    2 +-
> >  drivers/i2c/busses/i2c-at91.c          |    2 +-
> 
> I've never heard of an AT91 board using DRAM sticks ...
> 
> >  drivers/i2c/busses/i2c-cpm.c           |    2 +-
> >  drivers/i2c/busses/i2c-davinci.c       |    2 +-
> 
> ... or a DaVinci one ...
> 
> 
> >  drivers/i2c/busses/i2c-elektor.c       |    2 +-
> >  drivers/i2c/busses/i2c-gpio.c          |    2 +-
> >  drivers/i2c/busses/i2c-i801.c          |    2 +-
> >  drivers/i2c/busses/i2c-ibm_iic.c       |    4 ++--
> >  drivers/i2c/busses/i2c-iop3xx.c        |    2 +-
> >  drivers/i2c/busses/i2c-isch.c          |    2 +-
> >  drivers/i2c/busses/i2c-mpc.c           |    2 +-
> >  drivers/i2c/busses/i2c-mv64xxx.c       |    2 +-
> >  drivers/i2c/busses/i2c-nforce2.c       |    2 +-
> >  drivers/i2c/busses/i2c-ocores.c        |    2 +-
> >  drivers/i2c/busses/i2c-omap.c          |    2 +-
> 
> ... or an OMAP one ...
> 
> >  drivers/i2c/busses/i2c-parport-light.c |    2 +-
> >  drivers/i2c/busses/i2c-parport.c       |    2 +-
> >  drivers/i2c/busses/i2c-pasemi.c        |    2 +-
> >  drivers/i2c/busses/i2c-piix4.c         |    2 +-
> >  drivers/i2c/busses/i2c-pmcmsp.c        |    2 +-
> >  drivers/i2c/busses/i2c-s3c2410.c       |    2 +-
> >  drivers/i2c/busses/i2c-sibyte.c        |    4 ++--
> >  drivers/i2c/busses/i2c-sis5595.c       |    2 +-
> >  drivers/i2c/busses/i2c-sis630.c        |    2 +-
> >  drivers/i2c/busses/i2c-sis96x.c        |    2 +-
> >  drivers/i2c/busses/i2c-stub.c          |    2 +-
> >  drivers/i2c/busses/i2c-tiny-usb.c      |    2 +-
> 
> ... DRAM-over-USB would be bizarre too ...
> 
> >  drivers/i2c/busses/i2c-via.c           |    2 +-
> >  drivers/i2c/busses/i2c-viapro.c        |    2 +-
> >  drivers/i2c/busses/scx200_acb.c        |    2 +-
> >  include/linux/i2c.h                    |    1 +
> >  35 files changed, 37 insertions(+), 36 deletions(-)

OK, I'll revert the change for these 4 drivers.

Thanks,
-- 
Jean Delvare

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

  parent reply	other threads:[~2008-06-04  6:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-03 11:02 [PATCH 2/3] i2c: Let bus drivers add SPD to their class Jean Delvare
     [not found] ` <20080603130221.1f819e64-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-03 20:19   ` David Brownell
     [not found]     ` <200806031319.56606.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-06-03 21:12       ` Jon Smirl
     [not found]         ` <9e4733910806031412t52e7ed1bl8fd56751bef12a7a-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-03 21:33           ` Trent Piepho
     [not found]             ` <Pine.LNX.4.58.0806031420160.10290-13q4cmjDBaTP3RPoUHIrnuTW4wlIGRCZ@public.gmane.org>
2008-06-03 22:03               ` Jon Smirl
     [not found]                 ` <9e4733910806031503w46662d4fib36d3b67563bbdf1-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-06-04 19:59                   ` Trent Piepho
2008-06-04  6:09       ` Jean Delvare [this message]
     [not found]         ` <20080604080933.456c8ce2-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-06-04  7:18           ` David Brownell
     [not found]             ` <200806040018.10191.david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org>
2008-06-04 20:05               ` Trent Piepho
     [not found]                 ` <Pine.LNX.4.58.0806041303340.10290-13q4cmjDBaTP3RPoUHIrnuTW4wlIGRCZ@public.gmane.org>
2008-06-04 20:48                   ` David Brownell
2008-06-04 21:01                   ` 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=20080604080933.456c8ce2@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=david-b-yBeKhBN/0LDR7s880joybQ@public.gmane.org \
    --cc=i2c-GZX6beZjE8VD60Wz+7aTrA@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