[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210519113805.GA4224@sirena.org.uk>
Date: Wed, 19 May 2021 12:38:05 +0100
From: Mark Brown <broonie@...nel.org>
To: Dmitry Osipenko <digetx@...il.com>
Cc: Jaroslav Kysela <perex@...ex.cz>,
Thierry Reding <thierry.reding@...il.com>,
Jonathan Hunter <jonathanh@...dia.com>,
Takashi Iwai <tiwai@...e.com>, Ion Agorria <ion@...rria.com>,
Svyatoslav Ryhel <clamor95@...il.com>,
Frank Rowand <frowand.list@...il.com>,
Liam Girdwood <lgirdwood@...il.com>,
linux-tegra@...r.kernel.org, devicetree@...r.kernel.org,
alsa-devel@...a-project.org, linux-kernel@...r.kernel.org,
Rob Herring <robh@...nel.org>
Subject: Re: Question about Tegra UCMs
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.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists