linux-kernel - Re: [DISCUSSION] spi multi chipselect support

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: <20180719132512.GA27938@sirena.org.uk>
Date:   Thu, 19 Jul 2018 14:25:12 +0100
From:   Mark Brown <broonie@...nel.org>
To:     Lars-Peter Clausen <lars@...afoo.de>
Cc:     Sebastian Reichel <sebastian.reichel@...labora.co.uk>,
        Rob Herring <robh@...nel.org>, linux-kernel@...r.kernel.org,
        linux-spi@...r.kernel.org, devicetree@...r.kernel.org,
        kernel@...labora.com
Subject: Re: [DISCUSSION] spi multi chipselect support

On Wed, Jul 18, 2018 at 07:19:19PM +0200, Lars-Peter Clausen wrote:

> My preferred solution would to have something like
> i2c_new_secondary_device(), but for SPI. This way the driver that binds to
> the compatible string can allocate devices for additional chip selects as
> necessary. Also make use of the reg-names property the same way as in I2C.

Yes, that's at least the most consistent way forwards if nothing else.
I don't really have any more appealing ideas anyway.

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