Hi,
On 11/23/06, David Brownell <[EMAIL PROTECTED]> wrote:
On Tuesday 21 November 2006 7:57 am, Bill Gatliff wrote:
> Once you're hiding the GPIO number behind an enumeration, you can create
> a bitmap with more information than a single integer. That extra
> information could be used--- in my implementations, if any ever come
> about--- to store routing information.
But none of the existing GPIO users do that. The goal wasn't to define
a new notion of GPIO; it was collecting the existing ones under a single
arch-neutral umbrella.
> >It'd also be a big (and needless) disruption to code that's been working
> >fine for several years now ...
>
> ... all of which is using the current GPIO API, you mean? :)
Effectively, yes. I counted quite a few implementations in the current
tree which can trivially (#defines) map to that API.
I tried to do that for pxa, the patch is attached.
So what is the state of this discussion, now that 2.6.19 is here?
I just submitted an input driver for GPIO buttons to linux-input that
we use in the handhelds.org kernel for sa1100, pxa and s3c2410 archs.
It needs some ugly
#ifdefs currently, but with common GPIO calls they all could go away.
regards
Philipp
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
