From: Dmitry Osipenko <digetx@gmail.com>
To: Mark Brown <broonie@kernel.org>, Jaroslav Kysela <perex@perex.cz>
Cc: Thierry Reding <thierry.reding@gmail.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Takashi Iwai <tiwai@suse.com>, Ion Agorria <ion@agorria.com>,
Svyatoslav Ryhel <clamor95@gmail.com>,
Frank Rowand <frowand.list@gmail.com>,
Liam Girdwood <lgirdwood@gmail.com>,
linux-tegra@vger.kernel.org, devicetree@vger.kernel.org,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Rob Herring <robh@kernel.org>
Subject: Question about Tegra UCMs
Date: Wed, 19 May 2021 01:31:28 +0300 [thread overview]
Message-ID: <92cef674-c454-e08c-b44d-d8c08b1e8ccf@gmail.com> (raw)
In-Reply-To: <20210518183455.GE4358@sirena.org.uk>
Mark, could you please help me to understand the UCM naming scheme that ALSA uses..
About a year ago I tried to complain to Jaroslav Kysela in a comment to the UCM change [1] that it should be breaking the naming scheme of Tegra UCMs, but haven't got a meaningful reply and moved on to other things.
[1] https://github.com/alsa-project/alsa-ucm-conf/commit/8ff2d50745efbb6959324f672460e413f0b618b8
Today I noticed that the naming scheme changed again and I still don't understand what to do about it.
I have two devices:
1. Acer Picasso tablet that uses "Acer Iconia Tab A500 WM8903" for the card model name.
2. Google Nexus 7 that uses "ASUS Google Nexus 7 ALC5642".
Previously UCMs were picked up by pulseaudio from these paths:
1. /usr/share/alsa/ucm2/Acer Iconia Tab A500 WM8903/
2. /usr/share/alsa/ucm2/ASUS Google Nexus 7 ALC5642/
Now the lookup paths are changed to:
1. /usr/share/alsa/ucm2/Acer_Iconia_Tab/
2. /usr/share/alsa/ucm2/ASUS_Google_Nex/
Strace shows that pulseaudio searches UCMs only at these paths.
The output of /proc/asound/cards:
0 [WM8903 ]: Acer_Iconia_Tab - Acer Iconia Tab A500 WM8903
Acer Iconia Tab A500 WM8903
0 [ALC5642 ]: ASUS_Google_Nex - ASUS Google Nexus 7 ALC5642
ASUS Google Nexus 7 ALC5642
IIUC, the "ucm2/Tegra/codec_name" scheme [2] that the current ALSA UCM uses simply doesn't work at all. Is there anything on the kernel side that I could change to get a working naming scheme? If yes, I may try to do something about it in the v2, thanks in advance.
[2] https://github.com/alsa-project/alsa-ucm-conf/tree/master/ucm2/Tegra
next prev parent reply other threads:[~2021-05-18 22:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 0:13 [PATCH v1 0/2] Unify NVIDIA Tegra ASoC machine drivers Dmitry Osipenko
2021-05-18 0:13 ` [PATCH v1 1/2] of: base: Export of_device_compatible_match() Dmitry Osipenko
2021-05-18 18:14 ` Rob Herring
2021-05-18 0:13 ` [PATCH v1 2/2] ASoC: tegra: Unify ASoC machine drivers Dmitry Osipenko
2021-05-18 18:09 ` Rob Herring
2021-05-18 18:34 ` Mark Brown
2021-05-18 20:16 ` Dmitry Osipenko
2021-05-19 20:09 ` Mark Brown
2021-05-18 22:31 ` Dmitry Osipenko [this message]
2021-05-19 11:13 ` Question about Tegra UCMs Jaroslav Kysela
2021-05-19 13:15 ` Dmitry Osipenko
2021-05-19 11:38 ` Mark Brown
2021-05-19 13:19 ` Dmitry Osipenko
2021-05-18 20:11 ` [PATCH v1 2/2] ASoC: tegra: Unify ASoC machine drivers Dmitry Osipenko
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=92cef674-c454-e08c-b44d-d8c08b1e8ccf@gmail.com \
--to=digetx@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=clamor95@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=frowand.list@gmail.com \
--cc=ion@agorria.com \
--cc=jonathanh@nvidia.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=perex@perex.cz \
--cc=robh@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).