From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Ramesh Babu <ramesh.babu@linux.intel.com>
Cc: alsa-devel@alsa-project.org, lgirdwood@gmail.com,
vinod.koul@linux.intel.com, vaibhav.agarwal@intel.com,
omair.m.abdullah@intel.com,
Omair Mohammed Abdullah <omair.m.abdullah@linux.intel.com>
Subject: Re: [PATCH] ASoC: Jack: add configurable option for irq_flag
Date: Wed, 13 Feb 2013 13:19:17 +0000 [thread overview]
Message-ID: <20130213131917.GF5062@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <63969.10.223.96.90.1360733997.squirrel@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 701 bytes --]
On Wed, Feb 13, 2013 at 11:09:57AM +0530, Ramesh Babu wrote:
> > If the device only interrupts on one edge how does it detect jack
> > removal?
> Some codecs clears it's interrupt line when driver reads the codec status
> register.
> In such cases, the interupt line will go back to normal after driver
> reads status register. During removal, interrupt line will change and
> triggers on same edge interrupt.
Are you sure this is a GPIO that should be used directly (rather than
handled as part of the CODEC driver) and are you sure that the code
handles things like debounce well?
If this really is a GPIO it feels like the controller out to be exposing
itself as having dual edged interrupts.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-02-13 13:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 5:37 [PATCH] ASoC: Jack: add configurable option for irq_flag Omair Mohammed Abdullah
2013-02-12 11:47 ` Mark Brown
2013-02-13 5:39 ` Ramesh Babu
2013-02-13 13:19 ` Mark Brown [this message]
2013-02-15 7:10 ` Omair M. Abdullah
2013-02-15 12:17 ` Mark Brown
2013-02-17 6:37 ` Omair M. Abdullah
2013-02-17 18:11 ` Mark Brown
2013-02-18 12:55 ` Omair M. Abdullah
2013-02-18 13:29 ` Mark Brown
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=20130213131917.GF5062@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=lgirdwood@gmail.com \
--cc=omair.m.abdullah@intel.com \
--cc=omair.m.abdullah@linux.intel.com \
--cc=ramesh.babu@linux.intel.com \
--cc=vaibhav.agarwal@intel.com \
--cc=vinod.koul@linux.intel.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.