linux-kernel - Re: [PATCH] spi: dw: Enable Slave Select with GPIO Chip Select.

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]

Date:   Thu, 6 Oct 2016 11:37:55 +0200
From:   Mark Brown <broonie@...nel.org>
To:     tthayer@...nsource.altera.com
Cc:     andriy.shevchenko@...ux.intel.com, jarkko.nikula@...ux.intel.com,
        jszhang@...vell.com, michael@...rt-africa.com, kernel@...idel.net,
        linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] spi: dw: Enable Slave Select with GPIO Chip Select.

On Wed, Oct 05, 2016 at 04:38:58PM -0500, tthayer@...nsource.altera.com wrote:

> This patch adds the Slave Select locally so that the transfer will
> start and complete. The GPIO CS is taken care of earlier in the SPI
> framework (spi_set_cs).

This seems like something that other devices might need - it's not the
first time I heard of a device with the data transfer start and chip
select being tied together.  Why not make this a generic feature that
the core implements and drivers can enable?

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