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] [thread-next>] [day] [month] [year] [list]
Message-ID: <a1278046-038e-4825-b029-1b478f28cb7c@sirena.org.uk>
Date: Tue, 26 Nov 2024 13:56:20 +0000
From: Mark Brown <broonie@...nel.org>
To: Vishwaroop A <va@...dia.com>
Cc: robh@...nel.org, jonathanh@...dia.com, krzk+dt@...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, Nov 26, 2024 at 01:45:28PM +0000, Vishwaroop A wrote:

> +            # NVIDIA Tegra SPIDEV Controller device
> +          - nvidia,tegra-spidev

All the issues with having spidev nodes directly in the DT also apply if
you add a prefix onto it.  Whatever is attached to the SPI controller
needs to be described, not just a placeholder like this.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ