From: Mark Brown <broonie@kernel.org>
To: Bard Liao <bardliao@realtek.com>
Cc: Oder Chiou <oder_chiou@realtek.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
Flove <flove@realtek.com>
Subject: Re: [PATCH] ASoC: rt5640: add headset detection function
Date: Thu, 25 Jul 2013 10:15:47 +0100 [thread overview]
Message-ID: <20130725091547.GS9858@sirena.org.uk> (raw)
In-Reply-To: <1121E117AD4ECE49880A389A396215BB935C48A2B2@rtitmbs7.realtek.com.tw>
[-- Attachment #1.1: Type: text/plain, Size: 455 bytes --]
On Thu, Jul 25, 2013 at 11:36:42AM +0800, Bard Liao wrote:
> Usually, our customers use cpu's gpio as the interrupt pin of jack insert/remove.
> So we assume they will handle the interrupt event in machine driver.
> When machine driver get a jack insert/remove event, it will call this function to know the jack type(headset or headphone).
> Should I handle the interrupt event in codec driver?
Yes, of course. Interrupts are just interrupts on Linux.
[-- 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-07-25 9:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-23 6:54 [PATCH] ASoC: rt5640: add headset detection function bardliao
2013-07-23 13:00 ` Mark Brown
2013-07-25 3:36 ` Bard Liao
2013-07-25 9:15 ` Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-08 6:33 bardliao
2013-07-08 11:26 ` Mark Brown
2013-07-08 13:12 ` Bard Liao
2013-07-08 13:31 ` 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=20130725091547.GS9858@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=flove@realtek.com \
--cc=lgirdwood@gmail.com \
--cc=oder_chiou@realtek.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.