From: David Henningsson <david.henningsson@canonical.com>
To: "Jie, Yang" <yang.jie@intel.com>,
Tanu Kaskinen <tanu.kaskinen@linux.intel.com>,
Takashi Iwai <tiwai@suse.de>
Cc: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"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: Fri, 27 Mar 2015 09:01:29 +0100 [thread overview]
Message-ID: <55150E59.8080803@canonical.com> (raw)
In-Reply-To: <E7B1D079BA13FB44A978CC8F69C7D6A901BDE7F0@SHSMSX101.ccr.corp.intel.com>
On 2015-03-27 08:45, Jie, Yang wrote:
>> -----Original Message-----
>> From: David Henningsson [mailto:david.henningsson@canonical.com]
>> Sent: Friday, March 27, 2015 2:50 PM
>> To: Jie, Yang; Tanu Kaskinen; Takashi Iwai
>> Cc: perex@perex.cz; broonie@kernel.org; alsa-devel@alsa-project.org;
>> Girdwood, Liam R; Liam Girdwood
>> Subject: Re: [PATCH v2 1/2] ALSA: jack: create jack kcontrols for every jack
>> input device
>>
>>
>>
>> On 2015-03-26 13:43, Jie, Yang wrote:
>>>
>>> Sorry, Correct a typo(removing line "create "Mic Jack" kctl;" in
>>> default case)
>>
>> It looks like your code can be simplified as:
> [Keyon] thanks, I will try simplify them.
>>
>> switch (type | SND_JACK_HEADSET) {
>> case SND_JACK_HEADSET:
>> create "Headset Mic Jack" kctl;
>> /* fall through */
>> case SND_JACK_MICROPHONE:
>> case SND_JACK_HEADPHONE:
>> create format("%s Jack", id) kctl;
> [Keyon] I don't want to fill "id" to kctl name, because sometimes it can be
> string which can't be understood by PA, such as:
>
> soc/intel/mfld_machine.c: ret_val = snd_soc_card_jack_new(runtime->card,
> soc/intel/mfld_machine.c- "Intel(R) MID Audio Jack", SND_JACK_HEADSET |
> soc/intel/mfld_machine.c- SND_JACK_BTN_0 | SND_JACK_BTN_1, &mfld_jack,
>
> soc/omap/ams-delta.c: ret = snd_soc_card_jack_new(card, "hook_switch", SND_JACK_HEADSET,
> soc/omap/ams-delta.c- &ams_delta_hook_switch, NULL, 0);
Ok, good point. It's a matter of different conventions between ASoC and
HDA. In ASoC, naming is wild west. In HDA, naming is (mostly) consistent
and we depend on the exact naming for userspace to know exactly how the
jack functions.
Another example is HDMI/DisplayPort, where the hw often supports several
ports and we need to know which jack belongs to which PCM device, and we
use the name of the jack to determine that.
I would very much prefer that all the ASoC jack names (and mixer control
names!) would be fixed up to be consistent to the extent that makes
sense, but the ASoC people haven't really agreed to do that, but instead
prefer to use a large database of UCM files. :-( And seen from a UCM
context, that the ASoC jacks are labelled terribly inconsistent, isn't
that big of a deal given that UCM will specify the jack name anyhow.
>> }
>>
>> ...that way, prefixes such as "Front Headphone Jack" are preserved too,
> [Keyon] if PA can recognize "Front Headphone Jack" and "Rear Headphone Jack", then I
> prefer to add a determine here:
>
> if (!strcmp(id, "Front Headphone Jack") || !strcmp(id, "Rear Headphone Jack"))
> create format("%s Jack", id) kctl;
This will not scale, there are too many variants.
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
next prev parent reply other threads:[~2015-03-27 8:01 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
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 [this message]
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=55150E59.8080803@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 \
--cc=yang.jie@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.