linux-kernel - Re: [PATCH] [RFC] spi: spidev: Add support for Dual/Quad SPI Transfers

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20140224013542.GS25940@sirena.org.uk>
Date:	Mon, 24 Feb 2014 10:35:42 +0900
From:	Mark Brown <broonie@...nel.org>
To:	Geert Uytterhoeven <geert@...ux-m68k.org>
Cc:	linux-spi@...r.kernel.org, linux-kernel@...r.kernel.org,
	Geert Uytterhoeven <geert+renesas@...ux-m68k.org>
Subject: Re: [PATCH] [RFC] spi: spidev: Add support for Dual/Quad SPI
 Transfers

On Fri, Feb 21, 2014 at 05:14:53PM +0100, Geert Uytterhoeven wrote:

> The Kconfig entry for SPI_SPIDEV states:

>     Note that this application programming interface is EXPERIMENTAL
>     and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.

> So it's OK to break binary compatibility?
> Or should we introduce PI_IOC_RD_MODE16 and SPI_IOC_WR_MODE16 instead?

I think it's been experimental for so long that it has become a stable
interface I'm afraid - the new calls would be better.  Why not go for 32
bits instead of 16 bits for the new calls, that way it'll take longer to
fill up again?

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