linux-kernel - Re: [PATCH 1/6] SPI: add ability to say we want a cs change after every transfer.

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:	Wed, 7 Sep 2011 11:12:37 -0700
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Jonathan Cameron <jic23@....ac.uk>
Cc:	linux-kernel@...r.kernel.org, Michael.Hennerich@...log.com,
	linux-iio@...r.kernel.org
Subject: Re: [PATCH 1/6] SPI: add ability to say we want a cs change after
 every transfer.

On Wed, Sep 07, 2011 at 07:14:15PM +0100, Jonathan Cameron wrote:
> On 09/07/11 18:35, Mark Brown wrote:

> > We could add this in regmap if required.

> Makes more sense in spi and has been in their 'may be needed comment'
> from the first.  Also, lots of other users who don't fit into regmap
> (because they don't have any registers to speak of :)

Right, but obviously anything doing SPI transfers can just set the flag
in the transfers anyway.  It looked like you were adding this to the
core due to other intervening abstractions, probably this is just a
problem with your changelog.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/