From: Kai Vehmanen <kai.vehmanen@linux.intel.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: Takashi Iwai <tiwai@suse.de>,
ALSA development <alsa-devel@alsa-project.org>,
Mark Brown <broonie@kernel.org>,
Kai Vehmanen <kai.vehmanen@linux.intel.com>
Subject: Re: [alsa-devel] UCM extensions
Date: Wed, 6 Nov 2019 13:50:30 +0200 (EET) [thread overview]
Message-ID: <alpine.DEB.2.21.1911061327470.16459@zeliteleevi> (raw)
In-Reply-To: <6dcc3e0d-0df5-90cf-220f-59253d3b5c7c@perex.cz>
Hi Jaroslav,
On Tue, 5 Nov 2019, Jaroslav Kysela wrote:
> I make some internal ucm code cleanups in alsa-lib and added three
> major extensions to allow more complex configurations which we require for the
> SOF kernel driver.
looks very good and pragmatic way to tackle some of the issues you hit
with current UCM.
E.g. the If block would be also sufficient to tackle the recent HDMI codec
driver change (with a single UCM file) -- i.e. use existence of the
hdac-hdmi driver controls to select which enable-sequences to run. Hmm, I
like this better than trying to select a whole different UCM file based on
which drivers are used.
And same usage pattern can be applied to other mixer control name changes
(like you already did for the HDA mic control).
That of course leads to the question do we soon need mechanisms to
choose between more than two conditions (e.g. if mixer controls have
changed multiple times in recent kernels, so covering for this
in UCM would need a Switch, If-Else, or similar). But yeah, one can
always define another UCM, so keeping-it-simple might be the right
choice here.
> I added everything to keep the interface backward compatible, so the
> current applications should not observe any different behavior. The
> applications like pulseaudio should use the 'hw:CARD_INDEX' specifier for the
> open call in the future and snd_use_case_parse_ctl_elem_id() helper for the
> element control names.
This sounds good as well. Some testing with common versions of
e.g. Pulseaudio is probably in order to sanity check how this
works.
Br, Kai
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-11-06 11:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 19:36 [alsa-devel] UCM extensions Jaroslav Kysela
2019-11-05 19:52 ` Pierre-Louis Bossart
2019-11-05 20:19 ` Jaroslav Kysela
2019-11-05 20:27 ` Pierre-Louis Bossart
2019-11-06 11:50 ` Kai Vehmanen [this message]
2019-11-06 13:10 ` Jaroslav Kysela
2019-11-06 13:51 ` Jaska Uimonen
2019-11-06 17:04 ` Jaroslav Kysela
2019-11-07 6:48 ` Takashi Iwai
2019-11-07 8:33 ` Jaroslav Kysela
2019-11-07 9:23 ` Takashi Iwai
2019-11-07 11:08 ` Jaroslav Kysela
2019-11-07 11:16 ` Takashi Iwai
2019-11-07 13:14 ` Jaroslav Kysela
2019-11-07 10:18 ` Cezary Rojewski
2019-11-07 11:01 ` Jaroslav Kysela
2019-11-07 11:54 ` Kai Vehmanen
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=alpine.DEB.2.21.1911061327470.16459@zeliteleevi \
--to=kai.vehmanen@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=perex@perex.cz \
--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.