Received-SPF: pass (google.com: domain of linux-kernel+bounces-206457-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Date: Fri, 7 Jun 2024 17:07:23 +0100
From: Conor Dooley <conor@kernel.org>
To: =?utf-8?B?U3rFkWtl?= Benjamin <egyszeregy@freemail.hu>
Cc: Mark Brown <broonie@kernel.org>, linux-spi@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] spidev: Introduce "linux,spidev-name" property for
 device tree of spidev.
Message-ID: <20240607-upcoming-tidiness-401e5d0a8af0@spud>
References: <20240519211346.30323-1-egyszeregy@freemail.hu>
 <1ec9e8e5-0818-42b0-8776-d9cfb0585f42@sirena.org.uk>
 <9ae65e3c-f1fa-4ca9-8d74-12d92c51c5c6@freemail.hu>
 <e8837fe0-e93c-4133-aac1-f8f0a010f6de@sirena.org.uk>
 <30944fda-6d18-4fc1-8c73-bcda4814a417@freemail.hu>
Precedence: bulk
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="kswT3B/YF4mS8yoS"
Content-Disposition: inline
In-Reply-To: <30944fda-6d18-4fc1-8c73-bcda4814a417@freemail.hu>


--kswT3B/YF4mS8yoS
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Jun 02, 2024 at 05:31:10PM +0200, Sz=C5=91ke Benjamin wrote:

>     spidev@0 {
>         reg =3D <0>;
>         compatible =3D "rohm,dh2228fv";
>         spi-max-frequency =3D <1000000>;
>=20
>         // via my kernel patch -> /dev/spidev-mysensor
>         // linux,spidev-name =3D "mysensor";

Given you are describing a DAC as a "sensor", I doubt you actually even
have a dh2228fv*. You're looking to have a consistent name here, but you
can't even rely on Linux even continuing to bind the spidev driver
against this compatible if somebody comes along and writes an IIO driver
for this DAC!

That said, google seems to return no results for a dh2228fv, only for a
bh2228fv. Makes me wonder if this device actually even exists...


--kswT3B/YF4mS8yoS
Content-Type: application/pgp-signature; name="signature.asc"

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

iHUEABYIAB0WIQRh246EGq/8RLhDjO14tDGHoIJi0gUCZmMwOwAKCRB4tDGHoIJi
0pOqAP9GO4kepCashO7Y3AjkXVJoHS4PoLhigibXkEbYlB3eQAEAuLd0e5h4rldi
MPTdtfAutdaysEwujDWjtqdtU4LhfwI=
=8StO
-----END PGP SIGNATURE-----

--kswT3B/YF4mS8yoS--