From: Mark Brown <broonie@kernel.org>
To: Dmitry Osipenko <digetx@gmail.com>
Cc: Jaroslav Kysela <perex@perex.cz>,
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: Re: Question about Tegra UCMs
Date: Wed, 19 May 2021 12:38:05 +0100 [thread overview]
Message-ID: <20210519113805.GA4224@sirena.org.uk> (raw)
In-Reply-To: <92cef674-c454-e08c-b44d-d8c08b1e8ccf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 972 bytes --]
On Wed, May 19, 2021 at 01:31:28AM +0300, Dmitry Osipenko wrote:
> Mark, could you please help me to understand the UCM naming scheme that ALSA uses..
I have no real idea, sorry. Most of my userspace work has been with
Android which doesn't use UCM.
> 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.
Could you elaborate on the way in which it simply doesn't work at all?
I'd expect there to be something in there that first tries to match on
something to do with the specific hardware platform to take account of
plastics differences but that'd be a userspace change.
Please fix your mail client to word wrap within paragraphs at something
substantially less than 80 columns. Doing this makes your messages much
easier to read and reply to.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2021-05-19 11:38 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 ` Question about Tegra UCMs Dmitry Osipenko
2021-05-19 11:13 ` Jaroslav Kysela
2021-05-19 13:15 ` Dmitry Osipenko
2021-05-19 11:38 ` Mark Brown [this message]
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=20210519113805.GA4224@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=clamor95@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=digetx@gmail.com \
--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).