Received-SPF: pass (google.com: domain of linux-kernel+bounces-122989-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Date: Thu, 28 Mar 2024 13:45:28 +0000
From: Mark Brown <broonie@kernel.org>
To: Conor Dooley <conor@kernel.org>
Cc: Mihai Sain <mihai.sain@microchip.com>, robh@kernel.org,
	krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
	nicolas.ferre@microchip.com, alexandre.belloni@bootlin.com,
	claudiu.beznea@tuxon.dev, lgirdwood@gmail.com,
	andrei.simion@microchip.com, devicetree@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 7/7] regulator: mcp16502: Update the names from buck
 regulators
Message-ID: <aed9c6f0-a33f-4d2d-ad5c-2a5589483afa@sirena.org.uk>
References: <20240327101724.2982-1-mihai.sain@microchip.com>
 <20240327101724.2982-8-mihai.sain@microchip.com>
 <20240327-agreed-routine-0cc60186876b@spud>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="3xvy50Unb7ZcoSWS"
Content-Disposition: inline
In-Reply-To: <20240327-agreed-routine-0cc60186876b@spud>


--3xvy50Unb7ZcoSWS
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Wed, Mar 27, 2024 at 04:28:49PM +0000, Conor Dooley wrote:
> On Wed, Mar 27, 2024 at 12:17:24PM +0200, Mihai Sain wrote:

> > Use generic names for buck regulators to avoid any confusion.
> > Update the names from buck regulators in order to match
> > the datasheet block diagram for the buck regulators.

> I know the regulator core will create dummy regulators when they are not
> provided in the devicetree, so I am not 100% on how backwards
> compatibility works here.
> You'll end up with a bunch of dummies and therefore the regulator-names
> and constraints on the regulator will be lost, no?
> Can you explain how is this backwards compatible with the old
> devicetrees?

It quite simply isn't backwards compatible.  The original driver looks
to be pretty broken but this breaks compatibility, we'd need a
transition plan of some kind which probably needs some core work to cope
with fallback names.

--3xvy50Unb7ZcoSWS
Content-Type: application/pgp-signature; name="signature.asc"

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

iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmYFdHcACgkQJNaLcl1U
h9BZ6Qf7BKNHdl8v6RMF5pRZyZ7vMKhs3CzyTeHe56lT/zejkrG4sHEsOQmV0dEG
gVWKyDlpXzD+z5yrfTxadrPb3u72NEnFS0PEMBh0WgyuJ6YSVy8QaQe6jvKeJlMY
+jsh7bXzm9YKiBVya1gudts97wrILFiI54yEpsHt+hAyVHiQkaoceEAwMRoprUJR
3nxMQIn/fUIAsXCtEjPHHFGDCu6EjsHVS7pU0D/6gasATd++yCdnWgSk3GBR6HOV
ahuAjSBE09Nws1mo275I83sFix1FyemBdxvual2iRBekMpTyl4hsz3EhuhU6o6bW
My2Qzamr67YowDrsd2oEqYGVTJuBoQ==
=t1ua
-----END PGP SIGNATURE-----

--3xvy50Unb7ZcoSWS--