Hi!
> > > > Except the led code that is being proposed CAN sit on top of a generic
> > > > GPIO layer.
> > >
> > > I also have issues with a generic GPIO layer. As I mentioned in the
> > > past, there's serious locking issues with any generic abstraction of
> > > GPIOs.
> > >
> > > 1. You want to be able to change GPIO state from interrupts. This
> > > implies you can not sleep in GPIO state changing functions.
> > >
> > > 2. Some GPIOs are implemented on I2C devices. This means that to
> > > change state, you must sleep.
> >
> > Can't you just busywait? Yes, it is ugly in general, but perhaps it
> > is better than alternatives...
>
> Does the i2c layer support busy waiting or are you suggesting something
> else?
I'm suggesting that adding busy wait support to i2c is probably good
idea. GPIOs are on many small machines, and there are machine
(spitz/akita?) that differ mainly in "where GPIO lines are
connected". That cries for GPIO layer.
Pavel
--
Thanks, Sharp!
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
