From: David Henningsson <david.henningsson@canonical.com>
To: Mark Brown <broonie@kernel.org>
Cc: Tanu Kaskinen <tanu.kaskinen@linux.intel.com>,
Takashi Iwai <tiwai@suse.de>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
"Girdwood, Liam R" <liam.r.girdwood@intel.com>
Subject: Re: [PATCH v2 1/2] ALSA: jack: create jack kcontrols for every jack input device
Date: Tue, 24 Mar 2015 07:50:39 +0100 [thread overview]
Message-ID: <5511093F.1010708@canonical.com> (raw)
In-Reply-To: <20150323164129.GE14954@sirena.org.uk>
On 2015-03-23 17:41, Mark Brown wrote:
> On Mon, Mar 23, 2015 at 12:51:07PM +0100, David Henningsson wrote:
>> On 2015-03-23 11:56, Tanu Kaskinen wrote:
>
>>> One thing that is unclear for me is that how are those jacks represented
>>> that support any of headsets/headphones/microphones, but don't provide
>>> information about which device type has been plugged in.
>
>> For headphone or headset, independent switches:
>
>> * "Headphone Jack"
>> * "Headset Mic Jack"
>
>> For headphone or headset, one hw switch only:
>
>> * "Headphone Jack"
>> * "Headset Mic Phantom Jack"
>
> I'd have expected these to be the same thing, just with the second case
> always having the same state for both switches.
We need to distinguish the use cases: in case of independent switches,
we can make the assumption that if the user plugged in a headset, the
user wants to use the headset mic instead of the internal mic, so we
switch to it.
In the other case, where we don't know if the user plugged in a
headphone or a headset, we need to ask the user what (s)he plugged in,
so we can determine whether to select headphone+internal mic or
headphone+headset mic.
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
next prev parent reply other threads:[~2015-03-24 6:50 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-20 8:55 [PATCH v2 0/2] ALSA: jack: Refactoring for jack kctls Jie Yang
2015-03-20 8:55 ` Jie Yang
2015-03-20 8:55 ` [PATCH v2 1/2] ALSA: jack: create jack kcontrols for every jack input device Jie Yang
2015-03-20 9:27 ` Takashi Iwai
2015-03-20 9:29 ` Takashi Iwai
2015-03-20 12:22 ` Jie, Yang
2015-03-20 12:26 ` Takashi Iwai
2015-03-20 12:50 ` Jie, Yang
2015-03-20 13:21 ` Takashi Iwai
2015-03-20 13:49 ` Jie, Yang
2015-03-20 14:18 ` Takashi Iwai
2015-03-23 10:56 ` Tanu Kaskinen
2015-03-23 11:51 ` David Henningsson
2015-03-23 11:59 ` Takashi Iwai
2015-03-23 16:41 ` Mark Brown
2015-03-24 6:50 ` David Henningsson [this message]
2015-03-24 17:57 ` Mark Brown
2015-03-25 0:48 ` Raymond Yau
2015-03-25 2:14 ` Raymond Yau
2015-03-25 13:53 ` Jie, Yang
2015-03-25 16:13 ` Raymond Yau
2015-03-26 6:42 ` David Henningsson
2015-03-26 8:29 ` Jie, Yang
2015-03-26 9:05 ` David Henningsson
2015-03-26 12:39 ` Jie, Yang
2015-03-27 0:39 ` Raymond Yau
2015-03-27 2:13 ` Jie, Yang
2015-03-26 12:43 ` Jie, Yang
2015-03-27 6:50 ` David Henningsson
2015-03-27 7:45 ` Jie, Yang
2015-03-27 8:01 ` David Henningsson
2015-03-27 9:11 ` Jie, Yang
2015-03-30 7:27 ` David Henningsson
2015-03-26 2:34 ` Raymond Yau
2015-03-25 7:53 ` Jie, Yang
2015-03-25 9:27 ` Tanu Kaskinen
2015-03-25 14:13 ` Jie, Yang
2015-03-28 6:09 ` Raymond Yau
2015-03-20 10:30 ` Raymond Yau
2015-03-20 8:55 ` [PATCH v2 2/2] ALSA: hda - Remove jack kctls Jie Yang
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=5511093F.1010708@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=liam.r.girdwood@intel.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=tanu.kaskinen@linux.intel.com \
--cc=tiwai@suse.de \
/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.