On Fri, Sep 13, 2013 at 10:31:42AM +0200, Linus Walleij wrote: > The platform using this beeper has support for gpiolib, so there > is no point to use the custom gpio_line* API. A strange ambiguity > where a line was first set as input and then driven high was > solved by first driving the line high as output and then switch > it to input. > > Cc: Imre Kaloz <[email protected]> > Cc: Krzysztof Halasa <[email protected]> > Cc: Alexandre Courbot <[email protected]> > Cc: Dmitry Torokhov <[email protected]> > Acked-by: Arnd Bergmann <[email protected]> > Signed-off-by: Linus Walleij <[email protected]>
Acked-by: Dmitry Torokhov <[email protected]> > --- > Hi Dmitry, requesting an ACK for this to take it through the > GPIO tree as part of an IXP4 clean-up attempt. Sorry for the delay, I missed the fact that you wanted an ask and not merge and was waiting for rc1 to be cut... Thanks. -- Dmitry -- 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
