From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Janusz Krzysztofik <jkrzyszt@tis.icnet.pl>
Cc: alsa-devel@alsa-project.org,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
linux-input@vger.kernel.org
Subject: Re: Can a phone hook switch follow alsa jack model?
Date: Thu, 25 Jun 2009 12:05:08 +0100 [thread overview]
Message-ID: <20090625110508.GF17812@sirena.org.uk> (raw)
In-Reply-To: <4A4229EB.2090606@tis.icnet.pl>
On Wed, Jun 24, 2009 at 03:28:11PM +0200, Janusz Krzysztofik wrote:
> Mark Brown wrote:
> type. Don't you think that a new type like SND_JACK_PHONE_HOOK or
> SND_JACK_PHONE_HANDSET should be defined for the purpose? Even if
> HEADSET may not be very different from HANDSET, corresponding
> SW_HEADPHONE_INSERT and SW_MICROPHONE_INSERT event names seem have very
> little to do with picking up a phone.
Possibly, TBH I had thought I'd seen something for off-hook when I
looked at this originally but I can't seem to spot it now.
> So, if I want to follow the ASoC jack model, my in-kernel hook switch
> handler should only power on/off the handset, not touching the
> speakerphone at all. The latter should be controlled from userspace.
> Please correct me if I am missing something.
That's my initial guess - I've not looked at your particular hardware
so it may not end up being the best way of dealing with your system but
from what you said it was the approach that sprang to mind.
next prev parent reply other threads:[~2009-06-25 11:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-23 13:28 Can a phone hook switch follow alsa jack model? Janusz Krzysztofik
2009-06-23 22:22 ` Mark Brown
2009-06-24 13:28 ` Janusz Krzysztofik
2009-06-25 11:05 ` Mark Brown [this message]
2009-06-25 12:48 ` [alsa-devel] " Janusz Krzysztofik
2009-06-29 14:32 ` Mark Brown
2009-06-29 16:35 ` Janusz Krzysztofik
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=20090625110508.GF17812@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=jkrzyszt@tis.icnet.pl \
--cc=linux-input@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
/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