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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <ZmgpvimPgEugxJk4@surfacebook.localdomain>
Date: Tue, 11 Jun 2024 13:41:02 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Matti Vaittinen <mazziesaccount@...il.com>,
	Conor Dooley <conor@...nel.org>
Cc: Szőke Benjamin <egyszeregy@...email.hu>,
	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.

Fri, Jun 07, 2024 at 05:07:23PM +0100, Conor Dooley kirjoitti:
> 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...

Why not summon Matti?

-- 
With Best Regards,
Andy Shevchenko