From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: "Omair M. Abdullah" <omair.m.abdullah@intel.com>
Cc: Ramesh Babu <ramesh.babu@linux.intel.com>,
alsa-devel@alsa-project.org, vinod.koul@linux.intel.com,
vaibhav.agarwal@intel.com, lgirdwood@gmail.com,
Omair Mohammed Abdullah <omair.m.abdullah@linux.intel.com>
Subject: Re: [PATCH] ASoC: Jack: add configurable option for irq_flag
Date: Mon, 18 Feb 2013 13:29:23 +0000 [thread overview]
Message-ID: <20130218132922.GD30157@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20130218125516.GC23031@oma-dev>
[-- Attachment #1.1: Type: text/plain, Size: 615 bytes --]
On Mon, Feb 18, 2013 at 06:25:17PM +0530, Omair M. Abdullah wrote:
> On Sun, Feb 17, 2013 at 06:11:45PM +0000, Mark Brown wrote:
> > What you're describing does not sound at all sane, the GPIO jack code is
> > there for managing GPIO jacks not for providing a generic debounce
> > mechanism for interrupts. I'm not sure how you'd actually go about
> > doing this...
> If you have the codec interrupt line which is connected to the SoC through a
> GPIO then this is possible.
No, that doesn't make much sense. How is the CODEC IRQ ever going to
get delivered? And in general this doesn't seem sensible anyway.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2013-02-18 13:29 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
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 [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=20130218132922.GD30157@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 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).