linux-kernel - Re: [PATCH v2] spidev: Introduce "linux,spidev-name" property for device tree of spidev.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20240607-upcoming-tidiness-401e5d0a8af0@spud>
Date: Fri, 7 Jun 2024 17:07:23 +0100
From: Conor Dooley <conor@...nel.org>
To: Szőke Benjamin <egyszeregy@...email.hu>
Cc: Mark Brown <broonie@...nel.org>, linux-spi@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] spidev: Introduce "linux,spidev-name" property for
 device tree of spidev.

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

>     spidev@0 {
>         reg = <0>;
>         compatible = "rohm,dh2228fv";
>         spi-max-frequency = <1000000>;
> 
>         // via my kernel patch -> /dev/spidev-mysensor
>         // linux,spidev-name = "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...

Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)