[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
- It's still less than 2KB of ".text" (ARM). If there's got to be a
mid-layer for something so simple, that's the right size budget. :)
- The guts use board-specific SPI device tables to build the driver
model tree. (Hardware probing is rarely an option.)
- This version of Kconfig includes no drivers. At this writing there
are two known master controller drivers (PXA/SSP, OMAP MicroWire)
and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
mentions of other drivers in development.
- No userspace API. There are several implementations to compare.
Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
- One bugfix (removes a FIXME), with the visible effect of making device
names be "spiB.C" where B is the bus number and C is the chipselect.
- The "caller provides DMA mappings" mechanism now has kerneldoc, for
DMA drivers that want to be fancy.
- Hey, the framework init can be subsys_init. Even though board init
logic fires earlier, at arch_init ... since the framework init is
for driver support, and the board init support uses static init.
- Various additional spec/doc clarifications based on discussions
with other folk. It adds a brief "thank you" at the end, for folk
who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
Update the SPI framework to remove a potential priority inversion case by
reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-01-09 00:34:19 +03:00
|
|
|
#
|
|
|
|
|
# SPI driver configuration
|
|
|
|
|
#
|
|
|
|
|
# NOTE: the reason this doesn't show SPI slave support is mostly that
|
|
|
|
|
# nobody's needed a slave side API yet. The master-role API is not
|
|
|
|
|
# fully appropriate there, so it'd need some thought to do well.
|
|
|
|
|
#
|
2008-04-28 13:14:16 +04:00
|
|
|
menuconfig SPI
|
[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
- It's still less than 2KB of ".text" (ARM). If there's got to be a
mid-layer for something so simple, that's the right size budget. :)
- The guts use board-specific SPI device tables to build the driver
model tree. (Hardware probing is rarely an option.)
- This version of Kconfig includes no drivers. At this writing there
are two known master controller drivers (PXA/SSP, OMAP MicroWire)
and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
mentions of other drivers in development.
- No userspace API. There are several implementations to compare.
Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
- One bugfix (removes a FIXME), with the visible effect of making device
names be "spiB.C" where B is the bus number and C is the chipselect.
- The "caller provides DMA mappings" mechanism now has kerneldoc, for
DMA drivers that want to be fancy.
- Hey, the framework init can be subsys_init. Even though board init
logic fires earlier, at arch_init ... since the framework init is
for driver support, and the board init support uses static init.
- Various additional spec/doc clarifications based on discussions
with other folk. It adds a brief "thank you" at the end, for folk
who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
Update the SPI framework to remove a potential priority inversion case by
reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-01-09 00:34:19 +03:00
|
|
|
bool "SPI support"
|
2008-04-28 13:14:16 +04:00
|
|
|
depends on HAS_IOMEM
|
[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
- It's still less than 2KB of ".text" (ARM). If there's got to be a
mid-layer for something so simple, that's the right size budget. :)
- The guts use board-specific SPI device tables to build the driver
model tree. (Hardware probing is rarely an option.)
- This version of Kconfig includes no drivers. At this writing there
are two known master controller drivers (PXA/SSP, OMAP MicroWire)
and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
mentions of other drivers in development.
- No userspace API. There are several implementations to compare.
Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
- One bugfix (removes a FIXME), with the visible effect of making device
names be "spiB.C" where B is the bus number and C is the chipselect.
- The "caller provides DMA mappings" mechanism now has kerneldoc, for
DMA drivers that want to be fancy.
- Hey, the framework init can be subsys_init. Even though board init
logic fires earlier, at arch_init ... since the framework init is
for driver support, and the board init support uses static init.
- Various additional spec/doc clarifications based on discussions
with other folk. It adds a brief "thank you" at the end, for folk
who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
Update the SPI framework to remove a potential priority inversion case by
reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-01-09 00:34:19 +03:00
|
|
|
help
|
|
|
|
|
The "Serial Peripheral Interface" is a low level synchronous
|
|
|
|
|
protocol. Chips that support SPI can have data transfer rates
|
|
|
|
|
up to several tens of Mbit/sec. Chips are addressed with a
|
|
|
|
|
controller and a chipselect. Most SPI slaves don't support
|
|
|
|
|
dynamic device discovery; some are even write-only or read-only.
|
|
|
|
|
|
2006-11-30 07:22:59 +03:00
|
|
|
SPI is widely used by microcontrollers to talk with sensors,
|
[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
- It's still less than 2KB of ".text" (ARM). If there's got to be a
mid-layer for something so simple, that's the right size budget. :)
- The guts use board-specific SPI device tables to build the driver
model tree. (Hardware probing is rarely an option.)
- This version of Kconfig includes no drivers. At this writing there
are two known master controller drivers (PXA/SSP, OMAP MicroWire)
and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
mentions of other drivers in development.
- No userspace API. There are several implementations to compare.
Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
- One bugfix (removes a FIXME), with the visible effect of making device
names be "spiB.C" where B is the bus number and C is the chipselect.
- The "caller provides DMA mappings" mechanism now has kerneldoc, for
DMA drivers that want to be fancy.
- Hey, the framework init can be subsys_init. Even though board init
logic fires earlier, at arch_init ... since the framework init is
for driver support, and the board init support uses static init.
- Various additional spec/doc clarifications based on discussions
with other folk. It adds a brief "thank you" at the end, for folk
who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
Update the SPI framework to remove a potential priority inversion case by
reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-01-09 00:34:19 +03:00
|
|
|
eeprom and flash memory, codecs and various other controller
|
|
|
|
|
chips, analog to digital (and d-to-a) converters, and more.
|
|
|
|
|
MMC and SD cards can be accessed using SPI protocol; and for
|
|
|
|
|
DataFlash cards used in MMC sockets, SPI must always be used.
|
|
|
|
|
|
|
|
|
|
SPI is one of a family of similar protocols using a four wire
|
|
|
|
|
interface (select, clock, data in, data out) including Microwire
|
|
|
|
|
(half duplex), SSP, SSI, and PSP. This driver framework should
|
|
|
|
|
work with most such devices and controllers.
|
|
|
|
|
|
2008-04-28 13:14:16 +04:00
|
|
|
if SPI
|
|
|
|
|
|
[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
- It's still less than 2KB of ".text" (ARM). If there's got to be a
mid-layer for something so simple, that's the right size budget. :)
- The guts use board-specific SPI device tables to build the driver
model tree. (Hardware probing is rarely an option.)
- This version of Kconfig includes no drivers. At this writing there
are two known master controller drivers (PXA/SSP, OMAP MicroWire)
and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
mentions of other drivers in development.
- No userspace API. There are several implementations to compare.
Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
- One bugfix (removes a FIXME), with the visible effect of making device
names be "spiB.C" where B is the bus number and C is the chipselect.
- The "caller provides DMA mappings" mechanism now has kerneldoc, for
DMA drivers that want to be fancy.
- Hey, the framework init can be subsys_init. Even though board init
logic fires earlier, at arch_init ... since the framework init is
for driver support, and the board init support uses static init.
- Various additional spec/doc clarifications based on discussions
with other folk. It adds a brief "thank you" at the end, for folk
who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
Update the SPI framework to remove a potential priority inversion case by
reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-01-09 00:34:19 +03:00
|
|
|
config SPI_DEBUG
|
|
|
|
|
boolean "Debug support for SPI drivers"
|
2008-04-28 13:14:16 +04:00
|
|
|
depends on DEBUG_KERNEL
|
[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
- It's still less than 2KB of ".text" (ARM). If there's got to be a
mid-layer for something so simple, that's the right size budget. :)
- The guts use board-specific SPI device tables to build the driver
model tree. (Hardware probing is rarely an option.)
- This version of Kconfig includes no drivers. At this writing there
are two known master controller drivers (PXA/SSP, OMAP MicroWire)
and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
mentions of other drivers in development.
- No userspace API. There are several implementations to compare.
Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
- One bugfix (removes a FIXME), with the visible effect of making device
names be "spiB.C" where B is the bus number and C is the chipselect.
- The "caller provides DMA mappings" mechanism now has kerneldoc, for
DMA drivers that want to be fancy.
- Hey, the framework init can be subsys_init. Even though board init
logic fires earlier, at arch_init ... since the framework init is
for driver support, and the board init support uses static init.
- Various additional spec/doc clarifications based on discussions
with other folk. It adds a brief "thank you" at the end, for folk
who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
Update the SPI framework to remove a potential priority inversion case by
reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-01-09 00:34:19 +03:00
|
|
|
help
|
|
|
|
|
Say "yes" to enable debug messaging (like dev_dbg and pr_debug),
|
|
|
|
|
sysfs, and debugfs support in SPI controller and protocol drivers.
|
|
|
|
|
|
|
|
|
|
#
|
|
|
|
|
# MASTER side ... talking to discrete SPI slave chips including microcontrollers
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
config SPI_MASTER
|
|
|
|
|
# boolean "SPI Master Support"
|
|
|
|
|
boolean
|
|
|
|
|
default SPI
|
|
|
|
|
help
|
|
|
|
|
If your system has an master-capable SPI controller (which
|
|
|
|
|
provides the clock and chipselect), you can enable that
|
|
|
|
|
controller and the protocol drivers for the SPI slave chips
|
|
|
|
|
that are connected.
|
|
|
|
|
|
2008-07-24 08:29:53 +04:00
|
|
|
if SPI_MASTER
|
|
|
|
|
|
[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
- It's still less than 2KB of ".text" (ARM). If there's got to be a
mid-layer for something so simple, that's the right size budget. :)
- The guts use board-specific SPI device tables to build the driver
model tree. (Hardware probing is rarely an option.)
- This version of Kconfig includes no drivers. At this writing there
are two known master controller drivers (PXA/SSP, OMAP MicroWire)
and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
mentions of other drivers in development.
- No userspace API. There are several implementations to compare.
Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
- One bugfix (removes a FIXME), with the visible effect of making device
names be "spiB.C" where B is the bus number and C is the chipselect.
- The "caller provides DMA mappings" mechanism now has kerneldoc, for
DMA drivers that want to be fancy.
- Hey, the framework init can be subsys_init. Even though board init
logic fires earlier, at arch_init ... since the framework init is
for driver support, and the board init support uses static init.
- Various additional spec/doc clarifications based on discussions
with other folk. It adds a brief "thank you" at the end, for folk
who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
Update the SPI framework to remove a potential priority inversion case by
reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-01-09 00:34:19 +03:00
|
|
|
comment "SPI Master Controller Drivers"
|
|
|
|
|
|
2011-02-14 05:10:43 +03:00
|
|
|
config SPI_ALTERA
|
|
|
|
|
tristate "Altera SPI Controller"
|
|
|
|
|
select SPI_BITBANG
|
|
|
|
|
help
|
|
|
|
|
This is the driver for the Altera SPI Controller.
|
|
|
|
|
|
2011-01-04 23:28:22 +03:00
|
|
|
config SPI_ATH79
|
|
|
|
|
tristate "Atheros AR71XX/AR724X/AR913X SPI controller driver"
|
|
|
|
|
depends on ATH79 && GENERIC_GPIO
|
|
|
|
|
select SPI_BITBANG
|
|
|
|
|
help
|
|
|
|
|
This enables support for the SPI controller present on the
|
|
|
|
|
Atheros AR71XX/AR724X/AR913X SoCs.
|
|
|
|
|
|
2007-02-14 11:33:09 +03:00
|
|
|
config SPI_ATMEL
|
|
|
|
|
tristate "Atmel SPI Controller"
|
2008-07-24 08:29:53 +04:00
|
|
|
depends on (ARCH_AT91 || AVR32)
|
2007-02-14 11:33:09 +03:00
|
|
|
help
|
|
|
|
|
This selects a driver for the Atmel SPI Controller, present on
|
|
|
|
|
many AT32 (AVR32) and AT91 (ARM) chips.
|
|
|
|
|
|
2007-05-07 01:50:34 +04:00
|
|
|
config SPI_BFIN
|
|
|
|
|
tristate "SPI controller driver for ADI Blackfin5xx"
|
2008-07-24 08:29:53 +04:00
|
|
|
depends on BLACKFIN
|
2007-05-07 01:50:34 +04:00
|
|
|
help
|
|
|
|
|
This is the SPI controller master driver for Blackfin 5xx processor.
|
|
|
|
|
|
2011-03-28 12:57:11 +04:00
|
|
|
config SPI_BFIN_SPORT
|
|
|
|
|
tristate "SPI bus via Blackfin SPORT"
|
|
|
|
|
depends on BLACKFIN
|
|
|
|
|
help
|
|
|
|
|
Enable support for a SPI bus via the Blackfin SPORT peripheral.
|
|
|
|
|
|
2007-05-08 11:32:25 +04:00
|
|
|
config SPI_AU1550
|
2011-11-01 23:03:30 +04:00
|
|
|
tristate "Au1550/Au1200/Au1300 SPI Controller"
|
2011-08-12 13:39:45 +04:00
|
|
|
depends on MIPS_ALCHEMY && EXPERIMENTAL
|
2007-05-08 11:32:25 +04:00
|
|
|
select SPI_BITBANG
|
|
|
|
|
help
|
|
|
|
|
If you say yes to this option, support will be included for the
|
2011-11-01 23:03:30 +04:00
|
|
|
PSC SPI controller found on Au1550, Au1200 and Au1300 series.
|
2007-05-08 11:32:25 +04:00
|
|
|
|
2006-01-09 00:34:26 +03:00
|
|
|
config SPI_BITBANG
|
2009-01-07 01:41:41 +03:00
|
|
|
tristate "Utilities for Bitbanging SPI masters"
|
2006-01-09 00:34:26 +03:00
|
|
|
help
|
|
|
|
|
With a few GPIO pins, your system can bitbang the SPI protocol.
|
|
|
|
|
Select this to get SPI support through I/O pins (GPIO, parallel
|
|
|
|
|
port, etc). Or, some systems' SPI master controller drivers use
|
|
|
|
|
this code to manage the per-word or per-transfer accesses to the
|
|
|
|
|
hardware shift registers.
|
|
|
|
|
|
|
|
|
|
This is library code, and is automatically selected by drivers that
|
|
|
|
|
need it. You only need to select this explicitly to support driver
|
|
|
|
|
modules that aren't part of this kernel tree.
|
[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
- It's still less than 2KB of ".text" (ARM). If there's got to be a
mid-layer for something so simple, that's the right size budget. :)
- The guts use board-specific SPI device tables to build the driver
model tree. (Hardware probing is rarely an option.)
- This version of Kconfig includes no drivers. At this writing there
are two known master controller drivers (PXA/SSP, OMAP MicroWire)
and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
mentions of other drivers in development.
- No userspace API. There are several implementations to compare.
Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
- One bugfix (removes a FIXME), with the visible effect of making device
names be "spiB.C" where B is the bus number and C is the chipselect.
- The "caller provides DMA mappings" mechanism now has kerneldoc, for
DMA drivers that want to be fancy.
- Hey, the framework init can be subsys_init. Even though board init
logic fires earlier, at arch_init ... since the framework init is
for driver support, and the board init support uses static init.
- Various additional spec/doc clarifications based on discussions
with other folk. It adds a brief "thank you" at the end, for folk
who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
Update the SPI framework to remove a potential priority inversion case by
reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-01-09 00:34:19 +03:00
|
|
|
|
2006-01-09 00:34:29 +03:00
|
|
|
config SPI_BUTTERFLY
|
|
|
|
|
tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
|
2008-07-24 08:29:53 +04:00
|
|
|
depends on PARPORT
|
2006-01-09 00:34:29 +03:00
|
|
|
select SPI_BITBANG
|
|
|
|
|
help
|
|
|
|
|
This uses a custom parallel port cable to connect to an AVR
|
|
|
|
|
Butterfly <http://www.atmel.com/products/avr/butterfly>, an
|
|
|
|
|
inexpensive battery powered microcontroller evaluation board.
|
|
|
|
|
This same cable can be used to flash new firmware.
|
|
|
|
|
|
2010-01-20 23:49:44 +03:00
|
|
|
config SPI_COLDFIRE_QSPI
|
|
|
|
|
tristate "Freescale Coldfire QSPI controller"
|
|
|
|
|
depends on (M520x || M523x || M5249 || M527x || M528x || M532x)
|
|
|
|
|
help
|
|
|
|
|
This enables support for the Coldfire QSPI controller in master
|
|
|
|
|
mode.
|
|
|
|
|
|
2009-12-17 01:02:18 +03:00
|
|
|
config SPI_DAVINCI
|
2010-10-12 10:28:02 +04:00
|
|
|
tristate "Texas Instruments DaVinci/DA8x/OMAP-L/AM1x SoC SPI controller"
|
2009-12-17 01:02:18 +03:00
|
|
|
depends on SPI_MASTER && ARCH_DAVINCI
|
|
|
|
|
select SPI_BITBANG
|
|
|
|
|
help
|
2010-10-12 10:28:02 +04:00
|
|
|
SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules.
|
|
|
|
|
|
2010-05-06 08:47:04 +04:00
|
|
|
config SPI_EP93XX
|
|
|
|
|
tristate "Cirrus Logic EP93xx SPI controller"
|
|
|
|
|
depends on ARCH_EP93XX
|
|
|
|
|
help
|
|
|
|
|
This enables using the Cirrus EP93xx SPI controller in master
|
|
|
|
|
mode.
|
|
|
|
|
|
2009-01-07 01:41:41 +03:00
|
|
|
config SPI_GPIO
|
|
|
|
|
tristate "GPIO-based bitbanging SPI Master"
|
|
|
|
|
depends on GENERIC_GPIO
|
|
|
|
|
select SPI_BITBANG
|
|
|
|
|
help
|
|
|
|
|
This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
|
|
|
|
|
interface to manage MOSI, MISO, SCK, and chipselect signals. SPI
|
|
|
|
|
slaves connected to a bus using this driver are configured as usual,
|
|
|
|
|
except that the spi_board_info.controller_data holds the GPIO number
|
|
|
|
|
for the chipselect used by this controller driver.
|
|
|
|
|
|
|
|
|
|
Note that this driver often won't achieve even 1 Mbit/sec speeds,
|
|
|
|
|
making it unusually slow for SPI. If your platform can inline
|
|
|
|
|
GPIO operations, you should be able to leverage that for better
|
|
|
|
|
speed with a custom version of this driver; see the source code.
|
|
|
|
|
|
2009-09-23 03:46:02 +04:00
|
|
|
config SPI_IMX
|
|
|
|
|
tristate "Freescale i.MX SPI controllers"
|
|
|
|
|
depends on ARCH_MXC
|
|
|
|
|
select SPI_BITBANG
|
2010-09-09 13:12:12 +04:00
|
|
|
default m if IMX_HAVE_PLATFORM_SPI_IMX
|
2009-09-23 03:46:02 +04:00
|
|
|
help
|
|
|
|
|
This enables using the Freescale i.MX SPI controllers in master
|
|
|
|
|
mode.
|
|
|
|
|
|
2007-07-17 15:04:05 +04:00
|
|
|
config SPI_LM70_LLP
|
|
|
|
|
tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
|
2008-07-24 08:29:53 +04:00
|
|
|
depends on PARPORT && EXPERIMENTAL
|
2007-07-17 15:04:05 +04:00
|
|
|
select SPI_BITBANG
|
|
|
|
|
help
|
|
|
|
|
This driver supports the NS LM70 LLP Evaluation Board,
|
|
|
|
|
which interfaces to an LM70 temperature sensor using
|
|
|
|
|
a parallel port.
|
|
|
|
|
|
2009-11-05 01:34:18 +03:00
|
|
|
config SPI_MPC52xx
|
|
|
|
|
tristate "Freescale MPC52xx SPI (non-PSC) controller support"
|
2011-11-14 01:52:40 +04:00
|
|
|
depends on PPC_MPC52xx
|
2009-11-05 01:34:18 +03:00
|
|
|
help
|
|
|
|
|
This drivers supports the MPC52xx SPI controller in master SPI
|
|
|
|
|
mode.
|
|
|
|
|
|
2007-05-11 09:22:52 +04:00
|
|
|
config SPI_MPC52xx_PSC
|
|
|
|
|
tristate "Freescale MPC52xx PSC SPI controller"
|
2008-07-24 08:29:53 +04:00
|
|
|
depends on PPC_MPC52xx && EXPERIMENTAL
|
2007-05-11 09:22:52 +04:00
|
|
|
help
|
|
|
|
|
This enables using the Freescale MPC52xx Programmable Serial
|
|
|
|
|
Controller in master SPI mode.
|
|
|
|
|
|
2010-04-30 17:21:27 +04:00
|
|
|
config SPI_MPC512x_PSC
|
|
|
|
|
tristate "Freescale MPC512x PSC SPI controller"
|
|
|
|
|
depends on SPI_MASTER && PPC_MPC512x
|
|
|
|
|
help
|
|
|
|
|
This enables using the Freescale MPC5121 Programmable Serial
|
|
|
|
|
Controller in SPI master mode.
|
|
|
|
|
|
2010-10-12 14:18:31 +04:00
|
|
|
config SPI_FSL_LIB
|
|
|
|
|
tristate
|
|
|
|
|
depends on FSL_SOC
|
|
|
|
|
|
2010-10-12 14:18:30 +04:00
|
|
|
config SPI_FSL_SPI
|
2011-12-08 00:18:16 +04:00
|
|
|
bool "Freescale SPI controller"
|
2009-06-19 03:48:59 +04:00
|
|
|
depends on FSL_SOC
|
2010-10-12 14:18:31 +04:00
|
|
|
select SPI_FSL_LIB
|
2006-05-21 02:00:15 +04:00
|
|
|
help
|
2010-10-12 14:18:30 +04:00
|
|
|
This enables using the Freescale SPI controllers in master mode.
|
|
|
|
|
MPC83xx platform uses the controller in cpu mode or CPM/QE mode.
|
|
|
|
|
MPC8569 uses the controller in QE mode, MPC8610 in cpu mode.
|
2006-05-21 02:00:15 +04:00
|
|
|
|
spi/fsl_spi: add eSPI controller support
Add eSPI controller support based on the library code spi_fsl_lib.c.
The eSPI controller is newer controller 85xx/Pxxx devices supported.
There're some differences comparing to the SPI controller:
1. Has different register map and different bit definition
So leave the code operated the register to the driver code, not
the common code.
2. Support 4 dedicated chip selects
The software can't controll the chip selects directly, The SPCOM[CS]
field is used to select which chip selects is used, and the
SPCOM[TRANLEN] field is set to tell the controller how long the CS
signal need to be asserted. So the driver doesn't need the chipselect
related function when transfering data, just set corresponding register
fields to controll the chipseclect.
3. Different Transmit/Receive FIFO access register behavior
For SPI controller, the Tx/Rx FIFO access register can hold only
one character regardless of the character length, but for eSPI
controller, the register can hold 4 or 2 characters according to
the character lengths. Access the Tx/Rx FIFO access register of the
eSPI controller will shift out/in 4/2 characters one time. For SPI
subsystem, the command and data are put into different transfers, so
we need to combine all the transfers to one transfer in order to pass
the transfer to eSPI controller.
4. The max transaction length limitation
The max transaction length one time is limitted by the SPCOM[TRANSLEN]
field which is 0xFFFF. When used mkfs.ext2 command to create ext2
filesystem on the flash, the read length will exceed the max value of
the SPCOM[TRANSLEN] field.
Signed-off-by: Mingkai Hu <Mingkai.hu@freescale.com>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
2010-10-12 14:18:32 +04:00
|
|
|
config SPI_FSL_ESPI
|
2011-12-08 00:18:16 +04:00
|
|
|
bool "Freescale eSPI controller"
|
spi/fsl_spi: add eSPI controller support
Add eSPI controller support based on the library code spi_fsl_lib.c.
The eSPI controller is newer controller 85xx/Pxxx devices supported.
There're some differences comparing to the SPI controller:
1. Has different register map and different bit definition
So leave the code operated the register to the driver code, not
the common code.
2. Support 4 dedicated chip selects
The software can't controll the chip selects directly, The SPCOM[CS]
field is used to select which chip selects is used, and the
SPCOM[TRANLEN] field is set to tell the controller how long the CS
signal need to be asserted. So the driver doesn't need the chipselect
related function when transfering data, just set corresponding register
fields to controll the chipseclect.
3. Different Transmit/Receive FIFO access register behavior
For SPI controller, the Tx/Rx FIFO access register can hold only
one character regardless of the character length, but for eSPI
controller, the register can hold 4 or 2 characters according to
the character lengths. Access the Tx/Rx FIFO access register of the
eSPI controller will shift out/in 4/2 characters one time. For SPI
subsystem, the command and data are put into different transfers, so
we need to combine all the transfers to one transfer in order to pass
the transfer to eSPI controller.
4. The max transaction length limitation
The max transaction length one time is limitted by the SPCOM[TRANSLEN]
field which is 0xFFFF. When used mkfs.ext2 command to create ext2
filesystem on the flash, the read length will exceed the max value of
the SPCOM[TRANSLEN] field.
Signed-off-by: Mingkai Hu <Mingkai.hu@freescale.com>
Signed-off-by: Grant Likely <grant.likely@secretlab.ca>
2010-10-12 14:18:32 +04:00
|
|
|
depends on FSL_SOC
|
|
|
|
|
select SPI_FSL_LIB
|
|
|
|
|
help
|
|
|
|
|
This enables using the Freescale eSPI controllers in master mode.
|
|
|
|
|
From MPC8536, 85xx platform uses the controller, and all P10xx,
|
|
|
|
|
P20xx, P30xx,P40xx, P50xx uses this controller.
|
|
|
|
|
|
2011-02-14 05:20:39 +03:00
|
|
|
config SPI_OC_TINY
|
|
|
|
|
tristate "OpenCores tiny SPI"
|
|
|
|
|
depends on GENERIC_GPIO
|
|
|
|
|
select SPI_BITBANG
|
|
|
|
|
help
|
|
|
|
|
This is the driver for OpenCores tiny SPI master controller.
|
|
|
|
|
|
2007-02-12 11:52:37 +03:00
|
|
|
config SPI_OMAP_UWIRE
|
|
|
|
|
tristate "OMAP1 MicroWire"
|
2008-07-24 08:29:53 +04:00
|
|
|
depends on ARCH_OMAP1
|
2007-02-12 11:52:37 +03:00
|
|
|
select SPI_BITBANG
|
|
|
|
|
help
|
|
|
|
|
This hooks up to the MicroWire controller on OMAP1 chips.
|
|
|
|
|
|
2007-07-17 15:04:13 +04:00
|
|
|
config SPI_OMAP24XX
|
2010-05-14 23:05:25 +04:00
|
|
|
tristate "McSPI driver for OMAP"
|
|
|
|
|
depends on ARCH_OMAP2PLUS
|
2007-07-17 15:04:13 +04:00
|
|
|
help
|
2010-05-14 23:05:25 +04:00
|
|
|
SPI master controller for OMAP24XX and later Multichannel SPI
|
2007-07-17 15:04:13 +04:00
|
|
|
(McSPI) modules.
|
2007-02-12 11:52:39 +03:00
|
|
|
|
2009-12-13 11:02:11 +03:00
|
|
|
config SPI_OMAP_100K
|
|
|
|
|
tristate "OMAP SPI 100K"
|
|
|
|
|
depends on SPI_MASTER && (ARCH_OMAP850 || ARCH_OMAP730)
|
|
|
|
|
help
|
|
|
|
|
OMAP SPI 100K master controller for omap7xx boards.
|
|
|
|
|
|
2008-08-06 00:01:09 +04:00
|
|
|
config SPI_ORION
|
|
|
|
|
tristate "Orion SPI master (EXPERIMENTAL)"
|
|
|
|
|
depends on PLAT_ORION && EXPERIMENTAL
|
|
|
|
|
help
|
|
|
|
|
This enables using the SPI master controller on the Orion chips.
|
|
|
|
|
|
2009-06-09 11:11:42 +04:00
|
|
|
config SPI_PL022
|
2011-05-19 16:13:19 +04:00
|
|
|
tristate "ARM AMBA PL022 SSP controller"
|
|
|
|
|
depends on ARM_AMBA
|
2009-06-09 11:11:42 +04:00
|
|
|
default y if MACH_U300
|
2009-09-23 03:46:01 +04:00
|
|
|
default y if ARCH_REALVIEW
|
|
|
|
|
default y if INTEGRATOR_IMPD1
|
|
|
|
|
default y if ARCH_VERSATILE
|
2009-06-09 11:11:42 +04:00
|
|
|
help
|
|
|
|
|
This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
|
|
|
|
|
controller. If you have an embedded system with an AMBA(R)
|
|
|
|
|
bus and a PL022 controller, say Y or M here.
|
|
|
|
|
|
2009-09-23 03:45:58 +04:00
|
|
|
config SPI_PPC4xx
|
|
|
|
|
tristate "PPC4xx SPI Controller"
|
|
|
|
|
depends on PPC32 && 4xx && SPI_MASTER
|
|
|
|
|
select SPI_BITBANG
|
|
|
|
|
help
|
|
|
|
|
This selects a driver for the PPC4xx SPI Controller.
|
|
|
|
|
|
2006-03-08 10:53:24 +03:00
|
|
|
config SPI_PXA2XX
|
|
|
|
|
tristate "PXA2xx SSP SPI master"
|
2010-11-24 12:17:14 +03:00
|
|
|
depends on (ARCH_PXA || (X86_32 && PCI)) && EXPERIMENTAL
|
|
|
|
|
select PXA_SSP if ARCH_PXA
|
2006-03-08 10:53:24 +03:00
|
|
|
help
|
2010-11-24 12:17:14 +03:00
|
|
|
This enables using a PXA2xx or Sodaville SSP port as a SPI master
|
|
|
|
|
controller. The driver can be configured to use any SSP port and
|
|
|
|
|
additional documentation can be found a Documentation/spi/pxa2xx.
|
|
|
|
|
|
|
|
|
|
config SPI_PXA2XX_PCI
|
|
|
|
|
def_bool SPI_PXA2XX && X86_32 && PCI
|
2006-03-08 10:53:24 +03:00
|
|
|
|
2007-02-12 11:52:36 +03:00
|
|
|
config SPI_S3C24XX
|
|
|
|
|
tristate "Samsung S3C24XX series SPI"
|
2008-07-24 08:29:53 +04:00
|
|
|
depends on ARCH_S3C2410 && EXPERIMENTAL
|
2007-07-17 15:04:09 +04:00
|
|
|
select SPI_BITBANG
|
2007-02-12 11:52:36 +03:00
|
|
|
help
|
|
|
|
|
SPI driver for Samsung S3C24XX series ARM SoCs
|
|
|
|
|
|
2009-12-15 09:20:24 +03:00
|
|
|
config SPI_S3C24XX_FIQ
|
|
|
|
|
bool "S3C24XX driver with FIQ pseudo-DMA"
|
|
|
|
|
depends on SPI_S3C24XX
|
|
|
|
|
select FIQ
|
|
|
|
|
help
|
|
|
|
|
Enable FIQ support for the S3C24XX SPI driver to provide pseudo
|
|
|
|
|
DMA by using the fast-interrupt request framework, This allows
|
|
|
|
|
the driver to get DMA-like performance when there are either
|
|
|
|
|
no free DMA channels, or when doing transfers that required both
|
|
|
|
|
TX and RX data paths.
|
|
|
|
|
|
2009-11-30 10:39:42 +03:00
|
|
|
config SPI_S3C64XX
|
|
|
|
|
tristate "Samsung S3C64XX series type SPI"
|
2012-01-25 20:20:59 +04:00
|
|
|
depends on (ARCH_S3C64XX || ARCH_S5P64X0 || ARCH_EXYNOS)
|
2011-01-12 09:00:23 +03:00
|
|
|
select S3C64XX_DMA if ARCH_S3C64XX
|
2009-11-30 10:39:42 +03:00
|
|
|
help
|
|
|
|
|
SPI driver for Samsung S3C64XX and newer SoCs.
|
|
|
|
|
|
2009-11-26 14:10:05 +03:00
|
|
|
config SPI_SH_MSIOF
|
|
|
|
|
tristate "SuperH MSIOF SPI controller"
|
|
|
|
|
depends on SUPERH && HAVE_CLK
|
|
|
|
|
select SPI_BITBANG
|
|
|
|
|
help
|
|
|
|
|
SPI driver for SuperH MSIOF blocks.
|
|
|
|
|
|
2011-02-15 04:30:32 +03:00
|
|
|
config SPI_SH
|
|
|
|
|
tristate "SuperH SPI controller"
|
|
|
|
|
depends on SUPERH
|
|
|
|
|
help
|
|
|
|
|
SPI driver for SuperH SPI blocks.
|
|
|
|
|
|
2008-02-06 12:38:15 +03:00
|
|
|
config SPI_SH_SCI
|
|
|
|
|
tristate "SuperH SCI SPI controller"
|
2008-07-24 08:29:53 +04:00
|
|
|
depends on SUPERH
|
2008-02-06 12:38:15 +03:00
|
|
|
select SPI_BITBANG
|
|
|
|
|
help
|
|
|
|
|
SPI driver for SuperH SCI blocks.
|
|
|
|
|
|
2009-09-23 03:46:15 +04:00
|
|
|
config SPI_STMP3XXX
|
|
|
|
|
tristate "Freescale STMP37xx/378x SPI/SSP controller"
|
|
|
|
|
depends on ARCH_STMP3XXX && SPI_MASTER
|
|
|
|
|
help
|
|
|
|
|
SPI driver for Freescale STMP37xx/378x SoC SSP interface
|
|
|
|
|
|
2010-04-23 02:58:25 +04:00
|
|
|
config SPI_TEGRA
|
|
|
|
|
tristate "Nvidia Tegra SPI controller"
|
2011-12-23 03:57:57 +04:00
|
|
|
depends on ARCH_TEGRA && TEGRA_SYSTEM_DMA
|
2010-04-23 02:58:25 +04:00
|
|
|
help
|
|
|
|
|
SPI driver for NVidia Tegra SoCs
|
|
|
|
|
|
2011-01-18 22:21:36 +03:00
|
|
|
config SPI_TI_SSP
|
|
|
|
|
tristate "TI Sequencer Serial Port - SPI Support"
|
|
|
|
|
depends on MFD_TI_SSP
|
|
|
|
|
help
|
|
|
|
|
This selects an SPI master implementation using a TI sequencer
|
|
|
|
|
serial port.
|
|
|
|
|
|
2010-10-08 22:44:49 +04:00
|
|
|
config SPI_TOPCLIFF_PCH
|
2011-10-28 04:35:21 +04:00
|
|
|
tristate "Intel EG20T PCH/LAPIS Semicon IOH(ML7213/ML7223/ML7831) SPI"
|
2010-10-08 22:44:49 +04:00
|
|
|
depends on PCI
|
|
|
|
|
help
|
2010-10-08 22:56:13 +04:00
|
|
|
SPI driver for the Topcliff PCH (Platform Controller Hub) SPI bus
|
|
|
|
|
used in some x86 embedded processors.
|
2010-10-08 22:44:49 +04:00
|
|
|
|
2011-10-28 04:35:21 +04:00
|
|
|
This driver also supports the ML7213/ML7223/ML7831, a companion chip
|
|
|
|
|
for the Atom E6xx series and compatible with the Intel EG20T PCH.
|
2011-06-07 09:50:10 +04:00
|
|
|
|
2007-07-17 15:04:15 +04:00
|
|
|
config SPI_TXX9
|
|
|
|
|
tristate "Toshiba TXx9 SPI controller"
|
2008-07-24 08:29:53 +04:00
|
|
|
depends on GENERIC_GPIO && CPU_TX49XX
|
2007-07-17 15:04:15 +04:00
|
|
|
help
|
|
|
|
|
SPI driver for Toshiba TXx9 MIPS SoCs
|
|
|
|
|
|
2007-07-17 15:04:11 +04:00
|
|
|
config SPI_XILINX
|
2009-11-13 14:28:55 +03:00
|
|
|
tristate "Xilinx SPI controller common module"
|
2009-11-13 14:28:49 +03:00
|
|
|
depends on HAS_IOMEM && EXPERIMENTAL
|
2007-07-17 15:04:11 +04:00
|
|
|
select SPI_BITBANG
|
|
|
|
|
help
|
|
|
|
|
This exposes the SPI controller IP from the Xilinx EDK.
|
|
|
|
|
|
|
|
|
|
See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
|
|
|
|
|
Product Specification document (DS464) for hardware details.
|
|
|
|
|
|
2009-11-13 14:28:55 +03:00
|
|
|
Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
|
|
|
|
|
|
2009-12-01 17:29:20 +03:00
|
|
|
config SPI_NUC900
|
|
|
|
|
tristate "Nuvoton NUC900 series SPI"
|
|
|
|
|
depends on ARCH_W90X900 && EXPERIMENTAL
|
|
|
|
|
select SPI_BITBANG
|
|
|
|
|
help
|
|
|
|
|
SPI driver for Nuvoton NUC900 series ARM SoCs
|
|
|
|
|
|
[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
- It's still less than 2KB of ".text" (ARM). If there's got to be a
mid-layer for something so simple, that's the right size budget. :)
- The guts use board-specific SPI device tables to build the driver
model tree. (Hardware probing is rarely an option.)
- This version of Kconfig includes no drivers. At this writing there
are two known master controller drivers (PXA/SSP, OMAP MicroWire)
and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
mentions of other drivers in development.
- No userspace API. There are several implementations to compare.
Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
- One bugfix (removes a FIXME), with the visible effect of making device
names be "spiB.C" where B is the bus number and C is the chipselect.
- The "caller provides DMA mappings" mechanism now has kerneldoc, for
DMA drivers that want to be fancy.
- Hey, the framework init can be subsys_init. Even though board init
logic fires earlier, at arch_init ... since the framework init is
for driver support, and the board init support uses static init.
- Various additional spec/doc clarifications based on discussions
with other folk. It adds a brief "thank you" at the end, for folk
who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
Update the SPI framework to remove a potential priority inversion case by
reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-01-09 00:34:19 +03:00
|
|
|
#
|
|
|
|
|
# Add new SPI master controllers in alphabetical order above this line
|
|
|
|
|
#
|
|
|
|
|
|
2009-12-15 01:20:22 +03:00
|
|
|
config SPI_DESIGNWARE
|
2010-01-21 19:55:54 +03:00
|
|
|
tristate "DesignWare SPI controller core support"
|
2009-12-15 01:20:22 +03:00
|
|
|
depends on SPI_MASTER
|
|
|
|
|
help
|
|
|
|
|
general driver for SPI controller core from DesignWare
|
|
|
|
|
|
|
|
|
|
config SPI_DW_PCI
|
|
|
|
|
tristate "PCI interface driver for DW SPI core"
|
|
|
|
|
depends on SPI_DESIGNWARE && PCI
|
|
|
|
|
|
2010-12-24 08:59:11 +03:00
|
|
|
config SPI_DW_MID_DMA
|
|
|
|
|
bool "DMA support for DW SPI controller on Intel Moorestown platform"
|
|
|
|
|
depends on SPI_DW_PCI && INTEL_MID_DMAC
|
|
|
|
|
|
2010-01-21 17:46:42 +03:00
|
|
|
config SPI_DW_MMIO
|
|
|
|
|
tristate "Memory-mapped io interface driver for DW SPI core"
|
2010-01-22 20:08:31 +03:00
|
|
|
depends on SPI_DESIGNWARE && HAVE_CLK
|
2010-01-21 17:46:42 +03:00
|
|
|
|
[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
- It's still less than 2KB of ".text" (ARM). If there's got to be a
mid-layer for something so simple, that's the right size budget. :)
- The guts use board-specific SPI device tables to build the driver
model tree. (Hardware probing is rarely an option.)
- This version of Kconfig includes no drivers. At this writing there
are two known master controller drivers (PXA/SSP, OMAP MicroWire)
and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
mentions of other drivers in development.
- No userspace API. There are several implementations to compare.
Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
- One bugfix (removes a FIXME), with the visible effect of making device
names be "spiB.C" where B is the bus number and C is the chipselect.
- The "caller provides DMA mappings" mechanism now has kerneldoc, for
DMA drivers that want to be fancy.
- Hey, the framework init can be subsys_init. Even though board init
logic fires earlier, at arch_init ... since the framework init is
for driver support, and the board init support uses static init.
- Various additional spec/doc clarifications based on discussions
with other folk. It adds a brief "thank you" at the end, for folk
who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
Update the SPI framework to remove a potential priority inversion case by
reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-01-09 00:34:19 +03:00
|
|
|
#
|
|
|
|
|
# There are lots of SPI device types, with sensors and memory
|
|
|
|
|
# being probably the most widely used ones.
|
|
|
|
|
#
|
|
|
|
|
comment "SPI Protocol Masters"
|
|
|
|
|
|
2007-05-08 11:32:15 +04:00
|
|
|
config SPI_SPIDEV
|
|
|
|
|
tristate "User mode SPI device driver support"
|
2008-07-24 08:29:53 +04:00
|
|
|
depends on EXPERIMENTAL
|
2007-05-08 11:32:15 +04:00
|
|
|
help
|
|
|
|
|
This supports user mode SPI protocol drivers.
|
|
|
|
|
|
|
|
|
|
Note that this application programming interface is EXPERIMENTAL
|
|
|
|
|
and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
|
|
|
|
|
|
2007-07-17 15:04:10 +04:00
|
|
|
config SPI_TLE62X0
|
|
|
|
|
tristate "Infineon TLE62X0 (for power switching)"
|
2008-07-24 08:29:53 +04:00
|
|
|
depends on SYSFS
|
2007-07-17 15:04:10 +04:00
|
|
|
help
|
|
|
|
|
SPI driver for Infineon TLE62X0 series line driver chips,
|
|
|
|
|
such as the TLE6220, TLE6230 and TLE6240. This provides a
|
|
|
|
|
sysfs interface, with each line presented as a kind of GPIO
|
|
|
|
|
exposing both switch control and diagnostic feedback.
|
|
|
|
|
|
[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
- It's still less than 2KB of ".text" (ARM). If there's got to be a
mid-layer for something so simple, that's the right size budget. :)
- The guts use board-specific SPI device tables to build the driver
model tree. (Hardware probing is rarely an option.)
- This version of Kconfig includes no drivers. At this writing there
are two known master controller drivers (PXA/SSP, OMAP MicroWire)
and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
mentions of other drivers in development.
- No userspace API. There are several implementations to compare.
Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
- One bugfix (removes a FIXME), with the visible effect of making device
names be "spiB.C" where B is the bus number and C is the chipselect.
- The "caller provides DMA mappings" mechanism now has kerneldoc, for
DMA drivers that want to be fancy.
- Hey, the framework init can be subsys_init. Even though board init
logic fires earlier, at arch_init ... since the framework init is
for driver support, and the board init support uses static init.
- Various additional spec/doc clarifications based on discussions
with other folk. It adds a brief "thank you" at the end, for folk
who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
Update the SPI framework to remove a potential priority inversion case by
reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-01-09 00:34:19 +03:00
|
|
|
#
|
|
|
|
|
# Add new SPI protocol masters in alphabetical order above this line
|
|
|
|
|
#
|
|
|
|
|
|
2008-07-24 08:29:53 +04:00
|
|
|
endif # SPI_MASTER
|
|
|
|
|
|
[PATCH] spi: simple SPI framework
This is the core of a small SPI framework, implementing the model of a
queue of messages which complete asynchronously (with thin synchronous
wrappers on top).
- It's still less than 2KB of ".text" (ARM). If there's got to be a
mid-layer for something so simple, that's the right size budget. :)
- The guts use board-specific SPI device tables to build the driver
model tree. (Hardware probing is rarely an option.)
- This version of Kconfig includes no drivers. At this writing there
are two known master controller drivers (PXA/SSP, OMAP MicroWire)
and three protocol drivers (CS8415a, ADS7846, DataFlash) with LKML
mentions of other drivers in development.
- No userspace API. There are several implementations to compare.
Implement them like any other driver, and bind them with sysfs.
The changes from last version posted to LKML (on 11-Nov-2005) are minor,
and include:
- One bugfix (removes a FIXME), with the visible effect of making device
names be "spiB.C" where B is the bus number and C is the chipselect.
- The "caller provides DMA mappings" mechanism now has kerneldoc, for
DMA drivers that want to be fancy.
- Hey, the framework init can be subsys_init. Even though board init
logic fires earlier, at arch_init ... since the framework init is
for driver support, and the board init support uses static init.
- Various additional spec/doc clarifications based on discussions
with other folk. It adds a brief "thank you" at the end, for folk
who've helped nudge this framework into existence.
As I've said before, I think that "protocol tweaking" is the main support
that this driver framework will need to evolve.
From: Mark Underwood <basicmark@yahoo.com>
Update the SPI framework to remove a potential priority inversion case by
reverting to kmalloc if the pre-allocated DMA-safe buffer isn't available.
Signed-off-by: David Brownell <dbrownell@users.sourceforge.net>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
2006-01-09 00:34:19 +03:00
|
|
|
# (slave support would go here)
|
|
|
|
|
|
2008-04-28 13:14:16 +04:00
|
|
|
endif # SPI
|
