linux-kernel - Re: [PATCH] devicetree - document using aliases to set spi bus number.

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: <20160525180237.GB8206@sirena.org.uk>
Date:	Wed, 25 May 2016 19:02:37 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Mark Rutland <mark.rutland@....com>
Cc:	Frank Rowand <frowand.list@...il.com>,
	Christer Weinigel <christer@...nigel.se>,
	linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
	devicetree@...r.kernel.org
Subject: Re: [PATCH] devicetree - document using aliases to set spi bus
 number.

On Wed, May 25, 2016 at 04:59:50PM +0100, Mark Rutland wrote:

> e.g. stating that this describes a well-defined system-specific bus
> number as documented in a manual, with a note regarding Linux behaviour
> is better simply describing the Linux behaviour.

If it means anything it's really a system specific controller number but
even there it's at least as likely that the system will provide a
textual description as a number (eg, SPI_FLASH) and if it's supposed to
map onto something that can be abstracted between systems there's no
guarantee that if there's more than one SPI device to consider they'll
be provided by the same arrangement of controllers and chip selects on
different boards (which seems to be a use case here) so the spidev names
would still vary.

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