From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: linux-input@vger.kernel.org, Felipe Balbi <me@felipebalbi.com>
Subject: Re: [PATCH] Input: gpio-keys - add gpiolib debounce support
Date: Tue, 29 Jun 2010 00:06:53 -0700 [thread overview]
Message-ID: <20100629070653.GA19712@core.coreip.homeip.net> (raw)
In-Reply-To: <1277573636-10345-1-git-send-email-notasas@gmail.com>
On Sat, Jun 26, 2010 at 08:33:56PM +0300, Grazvydas Ignotas wrote:
> gpiolib now has debounce support added in .35, so let's make use of it.
> This allows to use hardware GPIO debouncing on some platforms like OMAP.
>
> In case gpiolib debounce setup fails for some GPIO, the driver will fall
> back to timer based debouncing, which is what it used before.
>
> Signed-off-by: Grazvydas Ignotas <notasas@gmail.com>
Applie to 'next', thank you Grazvydas.
--
Dmitry
prev parent reply other threads:[~2010-06-29 7:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-26 17:33 [PATCH] Input: gpio-keys - add gpiolib debounce support Grazvydas Ignotas
2010-06-29 7:06 ` Dmitry Torokhov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100629070653.GA19712@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=me@felipebalbi.com \
--cc=notasas@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).