Received-SPF: pass (google.com: domain of linux-kernel+bounces-55323-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Date: Tue, 6 Feb 2024 16:35:17 +0000
From: Mark Brown <broonie@kernel.org>
To: Matthias Kaehlcke <mka@chromium.org>
Cc: Javier Carrasco <javier.carrasco@wolfvision.net>,
	Liam Girdwood <lgirdwood@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v3 6/7] ASoC: dt-bindings: xmos,xvf3500: add XMOS XVF3500
 voice processor
Message-ID: <ZcJfxRgysxLWAOIH@finisterre.sirena.org.uk>
References: <20240206-onboard_xvf3500-v3-0-f85b04116688@wolfvision.net>
 <20240206-onboard_xvf3500-v3-6-f85b04116688@wolfvision.net>
 <ZcJDFi+iIQOWzgYw@finisterre.sirena.org.uk>
 <7b472cb2-6658-446a-ae47-411d08798cca@wolfvision.net>
 <ZcJR0LrwaS5GAf5h@finisterre.sirena.org.uk>
 <ZcJVD4CGhlWRwgfM@google.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="ZQT/yRHuU/ihg6na"
Content-Disposition: inline
In-Reply-To: <ZcJVD4CGhlWRwgfM@google.com>


--ZQT/yRHuU/ihg6na
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Feb 06, 2024 at 03:49:35PM +0000, Matthias Kaehlcke wrote:

> Initially the driver targeted a device with a single supply, the name
> 'vdd' was kept generic since it was expected that other devices would be
> supported (except for a couple of minor bits the driver is not device
> specific). Later support for a device with two supplies was added, with
> the generic name 'vdd2' to support other devices with multiple regulators.

It's generally always going to be a problem to add generic names that
don't reflect the actual hardware names, you still end up needing to
define the mapping from the real names to the generic names that have
been define when you end up with the regulators being controllable.

> Using the correct naming would be doable, with the caveat that the old
> naming still needs to be supported for backwards compatibility.

Yes, the existing bindings need to be supported as a legacy/fallback
thing.

--ZQT/yRHuU/ihg6na
Content-Type: application/pgp-signature; name="signature.asc"

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

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmXCX8QACgkQJNaLcl1U
h9DdNwf9Gyj9Sld7yROz9aRLyvoxIR6qEWLHzv+LnbbvL4odas62FJj65Wxn3aun
MvYZguIF7TY8NpMlCLoSXQBkhCWECnBSe7ayBjXXW/fVGN6pQKX56bQFzG0K2GEe
Y31/cQ7J8iAdUHauvZJzihpekgsRZLCS2VOKyff9oxyllFyIjn+S3egZo1C+m82J
OwE8GBVceOPOzYusyZ5J5mPrR8nEQz+SOy9aThjfY9t3EvppfQqA6zt08fIPw2PZ
afz9T3F878AdZ2tkPIujPrfbCyI0dDuMRLLn5NfYGY42jqgBjQ/J4nwKstZwTJ5x
sg27o4dCPT0Z0UqF1o4NK9IKRo5rsw==
=Hkgg
-----END PGP SIGNATURE-----

--ZQT/yRHuU/ihg6na--