Received-SPF: pass (google.com: domain of linux-kernel+bounces-135843-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Date: Mon, 8 Apr 2024 19:53:15 +0100
From: Mark Brown <broonie@kernel.org>
To: Dmitry Rokosov <ddrokosov@salutedevices.com>
Cc: Jerome Brunet <jbrunet@baylibre.com>, neil.armstrong@linaro.org,
	lgirdwood@gmail.com, conor+dt@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, perex@perex.cz, tiwai@suse.com,
	khilman@baylibre.com, martin.blumenstingl@googlemail.com,
	kernel@salutedevices.com, rockosov@gmail.com,
	linux-amlogic@lists.infradead.org, alsa-devel@alsa-project.org,
	linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v1 2/2] ASoC: meson: implement link-name optional
 property in meson card utils
Message-ID: <412306b3-e428-45ac-8bf5-6121f638272d@sirena.org.uk>
References: <20240408164947.30717-1-ddrokosov@salutedevices.com>
 <20240408164947.30717-3-ddrokosov@salutedevices.com>
 <1j1q7fpv1n.fsf@starbuckisacylon.baylibre.com>
 <20240408184041.3jcav5tabxiblpn4@CAB-WSD-L081021>
 <51b39153-d1a4-4e7f-9b30-8c77fc4ee46f@sirena.org.uk>
 <20240408184744.nfktcppdqewurmgg@CAB-WSD-L081021>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="HWk5+hm8t/wej2SK"
Content-Disposition: inline
In-Reply-To: <20240408184744.nfktcppdqewurmgg@CAB-WSD-L081021>


--HWk5+hm8t/wej2SK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

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.

--HWk5+hm8t/wej2SK
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmYUPRoACgkQJNaLcl1U
h9DJUgf+PtNQ01uTKkXCzFIX0QP1JVOK6eTnelaoRvequ7E9jlgWqkpwcmnmHGcG
7JaIcW2gK6BEj0kLODIrk5HrWWvPmPzVkTYOanJ7FWeTtCV8bXJSpU3Y79Ywy5VI
+Z3BPEH11EeIFF0PwWIH4p/oeUIJ4bgZ6p6IRujoBP1hY0bMlrkAlh6u4nOAM26O
6vdyVjM1Tt1JU8OSBBwu8Yi7LwrjWkLve4fY+kr0ZmNBCpDWNzNW8SYc9Ruusjae
rINMvZMEz886w85mpZ9km4tSVJmOUg1cEUBcQuhXufjdwHvk1L0QgcvbDG/5g0ai
0q5+Vy4UezOdjjATWlHxdZEIEOh1HQ==
=AHCz
-----END PGP SIGNATURE-----

--HWk5+hm8t/wej2SK--