From: "Ramesh Babu" <ramesh.babu@linux.intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.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 11:09:57 +0530 (IST) [thread overview]
Message-ID: <63969.10.223.96.90.1360733997.squirrel@linux.intel.com> (raw)
In-Reply-To: <20130212114752.GA1678@opensource.wolfsonmicro.com>
>> For a jack using GPIO based detection, the framework sets it to trigger
>> on both
>> edges (rising and falling). Some codecs may provide only a falling or
>> rising edge
>> interrupt but not both.
>
> 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.
next prev parent reply other threads:[~2013-02-13 5:40 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 [this message]
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
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=63969.10.223.96.90.1360733997.squirrel@linux.intel.com \
--to=ramesh.babu@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lgirdwood@gmail.com \
--cc=omair.m.abdullah@intel.com \
--cc=omair.m.abdullah@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.