From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Jean Delvare <khali@linux-fr.org>
Cc: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>,
Adrian Bunk <bunk@kernel.org>,
i2c@lm-sensors.org, linux-kernel@vger.kernel.org,
Lennert Buytenhek <buytenh@wantstofly.org>
Subject: Re: [2.6 patch] some overdue I2C driver removal
Date: Wed, 28 Nov 2007 17:41:11 +0000 [thread overview]
Message-ID: <20071128174111.GA30084@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20071128112357.3828d469@hyperion.delvare>
On Wed, Nov 28, 2007 at 11:23:57AM +0100, Jean Delvare wrote:
> 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.
There's actually a number of people who aren't thrilled by the concept
of a GPIO API. The current API is quite limiting in that it isn't
actually a "generic" GPIO API - you can't address GPIOs on a GPIO
expander with it for instance.
Some of those issues are in the process of being resolved, but I
suspect that this is a classic case where you can not satisfy everyone.
There'll always be people who refuse to use whatever GPIO API.
> 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?
It's really for Lennert to comment on; while you may consider I'm the
overall ARM maintainer, that doesn't mean that I have access to the
entire set of ARM hardware. Bit like expecting Linus to write working
drivers for SH4 without ever having had a SH4 platform... ;)
> 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.
... especially as those who need to comment on it don't get to see
Adrian's patches to remove them.
I think it's quite wrong to mark something "obsolete" and scheduling
it for removal unless there's an actual functioning replacement.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of:
next prev parent reply other threads:[~2007-11-28 18:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 16:25 [2.6 patch] some overdue I2C driver removal Adrian Bunk
2007-10-24 16:43 ` Lennart Sorensen
2007-11-28 10:23 ` Jean Delvare
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 [this message]
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=20071128174111.GA30084@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=bunk@kernel.org \
--cc=buytenh@wantstofly.org \
--cc=i2c@lm-sensors.org \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/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