linux-kernel - Re: [PATCH v1 2/2] ASoC: meson: implement link-name optional property in meson card utils

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <412306b3-e428-45ac-8bf5-6121f638272d@sirena.org.uk>
Date: Mon, 8 Apr 2024 19:53:15 +0100
From: Mark Brown <broonie@...nel.org>
To: Dmitry Rokosov <ddrokosov@...utedevices.com>
Cc: Jerome Brunet <jbrunet@...libre.com>, neil.armstrong@...aro.org,
	lgirdwood@...il.com, conor+dt@...nel.org, robh+dt@...nel.org,
	krzysztof.kozlowski+dt@...aro.org, perex@...ex.cz, tiwai@...e.com,
	khilman@...libre.com, martin.blumenstingl@...glemail.com,
	kernel@...utedevices.com, rockosov@...il.com,
	linux-amlogic@...ts.infradead.org, alsa-devel@...a-project.org,
	linux-sound@...r.kernel.org, devicetree@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v1 2/2] ASoC: meson: implement link-name optional
 property in meson card utils

On Mon, Apr 08, 2024 at 09:47:44PM +0300, Dmitry Rokosov wrote:
> On Mon, Apr 08, 2024 at 07:45:00PM +0100, Mark Brown wrote:

> > I would expect that the place to fix names based on the userspace
> > configuration is in whatever userspace is using to define it's
> > configurations, like a UCM config.

> Honestly, I have tried to find a way to rename the PCM device name or
> mark it in some way (such as using a metainformation tag or any other
> method), but unfortunately, my search has been unsuccessful.

I'd not be at all surprised if there's no such facility yet in whatever
userspace you're using and that it would need implementing, I'm just
saying that that seems like a better place to solve the problem you're
seeing.

Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)