Thread (2 messages) 2 messages, 2 authors, 2013-09-17

[PATCH 2/7] input: misc: ixp4-beeper: switch to use gpiolib

From: dmitry.torokhov@gmail.com (Dmitry Torokhov)
Date: 2013-09-17 19:01:49
Also in: linux-gpio

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 <kaloz@openwrt.org>
Cc: Krzysztof Halasa <khc@pm.waw.pl>
Cc: Alexandre Courbot <acourbot@nvidia.com>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Linus Walleij <redacted>
Acked-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
---
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help