gpiolib and sleeping gpios
david-b at pacbell.net
Sun Jun 20 22:40:46 EDT 2010
--- On Sun, 6/20/10, Ryan Mallon <ryan at bluewatersys.com> wrote:
> >> The point I was trying to make is that
> >> there are lots of drivers which
> >> will not work with gpios on sleeping io expandersbecause they call the
> >> spinlock safe gpio calls.
"Lots"? You mean there are lots of
maintainers who aren't even bothering to
provide trivial fixes for bug which are
clearly reported to them by warnings?
These one-liner fixes are not hard...
Such problems are people-problems, not issues
with any framework.
> > And they will trigger runtime warnings, and
> > thus eventually get fixed.
> err = gpio_request(some_gpio, "some_gpio",
NAK ... keep it simple. Such flags are
clearly not necessary...
I understand that some folk are bothered
by concepts/frameworks that seem "too simple"
and thus want to complexify them. In this
case I am in a position to help avoid that.
Complexity is not a virtue.
More information about the linux-arm-kernel