diff options
author | David Brownell <dbrownell@users.sourceforge.net> | 2009-06-30 11:41:26 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@linux-foundation.org> | 2009-06-30 18:56:00 -0700 |
commit | b55f627feeb9d48fdbde3835e18afbc76712e49b (patch) | |
tree | 1c6084d44f23c5e70040e5d62c93718f77ad09da /init | |
parent | c49568235dd7b4a2ffad63aa950562f4ffb9455f (diff) | |
download | linux-b55f627feeb9d48fdbde3835e18afbc76712e49b.tar.gz linux-b55f627feeb9d48fdbde3835e18afbc76712e49b.tar.bz2 linux-b55f627feeb9d48fdbde3835e18afbc76712e49b.zip |
spi: new spi->mode bits
Add two new spi_device.mode bits to accomodate more protocol options, and
pass them through to usermode drivers:
* SPI_NO_CS ... a second 3-wire variant, where the chipselect
line is removed instead of a data line; transfers are still
full duplex.
This obviously has STRONG protocol implications since the
chipselect transitions can't be used to synchronize state
transitions with the SPI master.
* SPI_READY ... defines open drain signal that's pulled low
to pause the clock. This defines a 5-wire variant (normal
4-wire SPI plus READY) and two 4-wire variants (READY plus
each of the 3-wire flavors).
Such hardware flow control can be a big win. There are ADC
converters and flash chips that expose READY signals, but not
many host controllers support it today.
The spi_bitbang code should be changed to use SPI_NO_CS instead of its
current nonportable hack. That's a mode most hardware can easily support
(unlike SPI_READY).
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Cc: "Paulraj, Sandeep" <s-paulraj@ti.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions