From: Jarkko Nikula <jhnikula@gmail.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Peter@alsa-project.org,
Ujfalusi <peter.ujfalusi@nokia.com>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ASoC: Use delayed work for debounce of GPIO based jacks
Date: Thu, 7 Oct 2010 08:54:31 +0300 [thread overview]
Message-ID: <20101007085431.879415b7.jhnikula@gmail.com> (raw)
In-Reply-To: <1286406301-25767-1-git-send-email-broonie@opensource.wolfsonmicro.com>
On Wed, 6 Oct 2010 16:05:01 -0700
Mark Brown <broonie@opensource.wolfsonmicro.com> wrote:
> Rather than block the workqueue by sleeping to do the debounce use delayed
> work to implement the debounce time. This should also mean that we extend
> the debounce time on each new bounce, potentially allowing shorter debounce
> times for clean insertions.
>
> Signed-off-by: Mark Brown <broonie@opensource.wolfsonmicro.com>
> ---
>
> This is completely untested as I do not have any systems to hand which
> can make use of this functionality but I believe it should work - I've
> CCed a couple of the OMAP people since they seem to be the main users.
>
> include/sound/soc.h | 2 +-
> sound/soc/soc-jack.c | 11 +++++------
> 2 files changed, 6 insertions(+), 7 deletions(-)
>
Works fine on N900 when testing with
hexdump /dev/input/by-path/platform-soc-audio-event
I have a vague memory that user space and actual state can get soon out
of sync if using delay based debouncing only and doing some insane plug
in/out cycle. So this is a step to right direction for implementing
more advanced debouncing.
Acked-by: Jarkko Nikula <jhnikula@gmail.com>
next prev parent reply other threads:[~2010-10-07 5:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-06 23:05 [PATCH] ASoC: Use delayed work for debounce of GPIO based jacks Mark Brown
2010-10-07 5:54 ` Jarkko Nikula [this message]
2010-10-10 10:38 ` Liam Girdwood
2010-10-07 18:13 ` Liam Girdwood
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=20101007085431.879415b7.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=Peter@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
--cc=peter.ujfalusi@nokia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.