mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jean Delvare <khali@linux-fr.org>
To: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
Cc: Adrian Bunk <bunk@kernel.org>,
	i2c@lm-sensors.org, linux-kernel@vger.kernel.org,
	Lennert Buytenhek <buytenh@wantstofly.org>,
	Russell King <rmk+kernel@arm.linux.org.uk>
Subject: Re: [2.6 patch] some overdue I2C driver removal
Date: Wed, 28 Nov 2007 11:23:57 +0100	[thread overview]
Message-ID: <20071128112357.3828d469@hyperion.delvare> (raw)
In-Reply-To: <20071024164347.GN4003@csclub.uwaterloo.ca>

On Wed, 24 Oct 2007 12:43:47 -0400, Lennart Sorensen wrote:
> On Wed, Oct 24, 2007 at 06:25:28PM +0200, Adrian Bunk wrote:
> > This patch contains the overdue removal of three I2C drivers.
> > 
> > Signed-off-by: Adrian Bunk <bunk@kernel.org>
> > 
> > ---
> > 
> >  Documentation/feature-removal-schedule.txt |    8 
> >  drivers/i2c/busses/Kconfig                 |   59 ------
> >  drivers/i2c/busses/Makefile                |    3 
> >  drivers/i2c/busses/i2c-ixp2000.c           |  167 -------------------
> >  drivers/i2c/busses/i2c-ixp4xx.c            |  178 ---------------------
> >  drivers/i2c/busses/scx200_i2c.c            |  131 ---------------
> >  6 files changed, 546 deletions(-)
> > 
> > 6a8e0e37019c0ffeb0071fae30210baf2c3bdd75 
> > diff --git a/Documentation/feature-removal-schedule.txt b/Documentation/feature-removal-schedule.txt
> > index 2af3835..9114379 100644
> > --- a/Documentation/feature-removal-schedule.txt
> > +++ b/Documentation/feature-removal-schedule.txt
> > @@ -218,14 +218,6 @@ Who:	Len Brown <len.brown@intel.com>
> >  
> >  ---------------------------
> >  
> > -What:	i2c-ixp2000, i2c-ixp4xx and scx200_i2c drivers
> > -When:	September 2007
> > -Why:	Obsolete. The new i2c-gpio driver replaces all hardware-specific
> > -	I2C-over-GPIO drivers.
> > -Who:	Jean Delvare <khali@linux-fr.org>
> > -
> > ----------------------------
> 
> Did anyone ever write a driver that does i2c on the scx200 using the new
> i2c-gpio method?  I sure haven't seen it, although I am still running
> 2.6.18 (since that is what debian stable uses) on my scx200 systems.  I
> certainly haven't found any useful instructions on how to use the new
> i2c-gpio driver on an scx200.

There's no driver to write (i2c-gpio is the driver). Instead, the
scx200 platform needs to implement the standard GPIO API. I don't think
that it has happened yet, and last time this was discussed, someone
(can't remember who, sorry), complained that the GPIO API "sucked" and
that the scx200 platform would not be updated to use it. I didn't buy
the claim due to a lack of argumentation and the fact that the GPIO
infrastructure seems to work well enough for many other platforms.

As far as I can see, the ixp2000 platform also doesn't implement the
standard GPIO API yet, so of the 3 drivers that are about to be
removed, only i2c-ixp4xx can be removed without functionality loss at
the moment. Lennert, Russell, are there any plans to convert the
ixp2000 platform to use the generic GPIO layer?

Maybe I shouldn't have added this entry in feature-removal-schedule.txt
in the first place: these drivers should ideally be dropped in favor of
i2c-gpio, but it can only happen for platforms that implement the
standard GPIO API. As I am not the one who will convert these
platforms, and some of them might as well never be converted (I don't
know how active they are nowadays), there's not much I can do.

Thanks,
-- 
Jean Delvare

  reply	other threads:[~2007-11-28 10:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 16:25 Adrian Bunk
2007-10-24 16:43 ` Lennart Sorensen
2007-11-28 10:23   ` Jean Delvare [this message]
2007-11-28 17:30     ` Lennart Sorensen
2007-11-28 17:43       ` [i2c] " Jon Smirl
2007-11-28 17:53         ` Jean Delvare
2007-11-28 17:54         ` Russell King
2007-11-28 19:04         ` Lennart Sorensen
2007-11-28 17:41     ` Russell King
2007-11-28 18:37     ` Lennert Buytenhek
2007-11-28 19: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=20071128112357.3828d469@hyperion.delvare \
    --to=khali@linux-fr.org \
    --cc=bunk@kernel.org \
    --cc=buytenh@wantstofly.org \
    --cc=i2c@lm-sensors.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lsorense@csclub.uwaterloo.ca \
    --cc=rmk+kernel@arm.linux.org.uk \
    /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

Powered by JetHome