From: Mark Brown <broonie@kernel.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@linux-m68k.org>
Subject: Re: [PATCH] [RFC] spi: spidev: Add support for Dual/Quad SPI Transfers
Date: Mon, 24 Feb 2014 10:35:42 +0900 [thread overview]
Message-ID: <20140224013542.GS25940@sirena.org.uk> (raw)
In-Reply-To: <1392999293-5015-1-git-send-email-geert@linux-m68k.org>
[-- Attachment #1: Type: text/plain, Size: 605 bytes --]
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?
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2014-02-24 5:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-21 16:14 Geert Uytterhoeven
2014-02-24 1:35 ` Mark Brown [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140224013542.GS25940@sirena.org.uk \
--to=broonie@kernel.org \
--cc=geert+renesas@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®