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: <20160418121430.GA3217@sirena.org.uk>
Date:	Mon, 18 Apr 2016 13:14:30 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Bhuvanchandra DV <bhuvanchandra.dv@...adex.com>
Cc:	gregkh@...uxfoundation.org, stefan@...er.ch,
	linux-kernel@...r.kernel.org, linux-spi@...r.kernel.org,
	Stefan Agner <stefan.agner@...adex.com>
Subject: Re: [RFC 2/2] spi core: Add new sysfs 'num_chipselect' file

On Mon, Apr 18, 2016 at 04:48:28PM +0530, Bhuvanchandra DV wrote:
> Add new sysfs 'num_chipselect' file to expose the maximum number
> of chipselects a SPI master can support.
> This allows to create a script in user space which automatically
> creates a new spidev instance for every chipselect on a bus.

This does not seem like a good idea, even if a chip select is supported
in the IP that doesn't mean it's brought out safely on a board and
pinmuxing may mean that the set of chip selects that can be used is
sparse.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ