Received-SPF: pass (google.com: domain of linux-kernel+bounces-38597-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Date: Thu, 25 Jan 2024 12:53:38 +0000
From: Conor Dooley <conor.dooley@microchip.com>
To: Andrew Lunn <andrew@lunn.ch>
CC: Conor Dooley <conor@kernel.org>, Philippe Schenker <dev@pschenker.ch>,
	<netdev@vger.kernel.org>, Paolo Abeni <pabeni@redhat.com>, Conor Dooley
	<conor+dt@kernel.org>, Woojung Huh <woojung.huh@microchip.com>, "Vladimir
 Oltean" <olteanv@gmail.com>, <linux-kernel@vger.kernel.org>,
	<UNGLinuxDriver@microchip.com>, Marek Vasut <marex@denx.de>, Florian Fainelli
	<f.fainelli@gmail.com>, <devicetree@vger.kernel.org>, Eric Dumazet
	<edumazet@google.com>, "David S . Miller" <davem@davemloft.net>, "Krzysztof
 Kozlowski" <krzysztof.kozlowski+dt@linaro.org>, Jakub Kicinski
	<kuba@kernel.org>, Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCH net-next v1 1/2] dt-bindings: net: dsa: Add KSZ8567
 switch support
Message-ID: <20240125-crouch-decay-5b149b60e9f3@wendy>
References: <20240123135014.614858-1-dev@pschenker.ch>
 <20240123-ripening-tabby-b97785375990@spud>
 <b2e232de11cee47a5932fccc2d151a9c7c276784.camel@pschenker.ch>
 <20240123-atlas-dart-7e955e7e24e5@spud>
 <979b1e77b5bb62463d52e7b9d3f9ca1415f4006a.camel@pschenker.ch>
 <20240123-carpool-avatar-c1e51ab3cc32@spud>
 <359c32a1-3ffb-4bb2-9a46-802dff3812c4@lunn.ch>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="FasY058SMp5+ll7F"
Content-Disposition: inline
In-Reply-To: <359c32a1-3ffb-4bb2-9a46-802dff3812c4@lunn.ch>

--FasY058SMp5+ll7F
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Jan 24, 2024 at 07:08:29PM +0100, Andrew Lunn wrote:
> > That sounds counter productive to be honest. Why does the driver not
> > trust that the dt is correct? I saw this recently in some IIO drivers,
> > but it was shot down for this sort of reason.
>=20
> DT is software, therefore it contains bugs.
>=20
> Say we ignore that the compatible does not match the hardware on the
> board and just accept the DT has a bug in it and keep going.
>=20
> That then makes the compatible pointless, and unusable for anything,
> since there are boards out in the wild with incorrect compatibles. If
> we later actually use the compatible for something, it might cause
> regressions for those buggy DT blobs.
>=20
> By erroring out then the compatible does not match the hardware avoids
> such bugs.

It also makes fallback compatibles useless, which is what I see as being
counter productive, since you'll have to add support to the driver even
if (other than the id) the change is imperceptible to software.
If you have your reasons why you do not trust the compatibles for these
devices, then it is your prerogative as a driver author to cross check it
and fail if they don't match.

That said, it does not prevent the fallback being accurately described
in the binding itself, which at the end of the day is what I am more
interested it.

> The marvell mv88e6xxx driver takes a different approach. All the
> compatible does is tell the driver where to find the ID
> register. Marvell keeps moving it around, so there are three different
> compatibles for the three different locations. If you use the wrong
> compatible, its not going to find a device is knows about and errors
> out. So this also avoids bugs in the compatible.
>=20
>      Andrew

--FasY058SMp5+ll7F
Content-Type: application/pgp-signature; name="signature.asc"

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

iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZbJZ0gAKCRB4tDGHoIJi
0kQ+AQC8bfXwu4cS2q0UdokiptXIHP0dNFYEDpmgxeF19Tpo+wEAlrHaYMrYkfJH
CKM8cpf8KpQLdoE/xhPrfS1a1YBYBQU=
=aa2K
-----END PGP SIGNATURE-----

--FasY058SMp5+ll7F--