On Tue, Sep 3, 2013 at 10:34 PM, Fabio Estevam <[email protected]> wrote: >> >> If I revert this commit, then I am able to boot correctly. > > I think I found a fix: > > --- a/drivers/gpio/gpiolib.c > +++ b/drivers/gpio/gpiolib.c > @@ -1783,7 +1783,7 @@ static int gpiod_set_debounce(struct gpio_desc *desc, > unsi > if (!chip->set || !chip->set_debounce) { > pr_warn("%s: missing set() or set_debounce() operations\n", > __func__); > - return -EIO; > + goto fail; > } > > will submit it shortly.
A commit like this is already in linux-next, however I screwed up the locking so the final fix arrives today. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-gpio" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
