linux-kernel - Re: [PATCH 2/3] dt-bindings: spi: Add DT schema for Tegra SPIDEV controller

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: <48248165-c800-484f-be62-7c48b3c6829b@sirena.org.uk>
Date: Tue, 25 Mar 2025 12:10:19 +0000
From: Mark Brown <broonie@...nel.org>
To: Jon Hunter <jonathanh@...dia.com>
Cc: Vishwaroop A <va@...dia.com>, krzk+dt@...nel.org, robh@...nel.org,
	conor+dt@...nel.org, thierry.reding@...il.com,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-tegra@...r.kernel.org, linux-spi@...r.kernel.org
Subject: Re: [PATCH 2/3] dt-bindings: spi: Add DT schema for Tegra SPIDEV
 controller

On Tue, Mar 25, 2025 at 10:36:29AM +0000, Jon Hunter wrote:
> On 27/11/2024 17:31, Mark Brown wrote:

> > You can put 'spidev' in as the compatible and get the warning, we don't
> > require specific compatibles if the Linux device ID is good enough.  If
> > you genuinely just have bare wires you're probably able to cope with the
> > warning.  If something is actually connected you should use the
> > compatible for whatever that is, if spidev makes sense for it then
> > that'd be OK to add to spidev.

> We finally got back to this. Looks like just having 'spidev' as the
> compatible does not work. Apparently, it use to work and yes you would get
> the warning, but that no longer seems to be the case. I see a few others
> have been doing similar things and hacking their device-trees in different
> ways [0].

Huh, OK.  I don't recall any deliberate SPI change for that.

> I completely agree that ideally we would have a proper compatible string for
> this because after all device-tree describes the hardware. One use-case that
> we use is external loop back for verifying SPI by simply connecting MOSI to
> the MISO. Would it be acceptable to have a compatible string for external
> loopback connections?

That sounds fine.

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