[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
|
|
|
#
|
|
|
|
|
# Makefile for kernel SPI drivers.
|
|
|
|
|
#
|
|
|
|
|
|
|
|
|
|
ifeq ($(CONFIG_SPI_DEBUG),y)
|
|
|
|
|
EXTRA_CFLAGS += -DDEBUG
|
|
|
|
|
endif
|
|
|
|
|
|
|
|
|
|
# small core, mostly translating board-specific
|
|
|
|
|
# config declarations into driver model code
|
|
|
|
|
obj-$(CONFIG_SPI_MASTER) += spi.o
|
|
|
|
|
|
|
|
|
|
# SPI master controller drivers (bus)
|
2007-02-14 11:33:09 +03:00
|
|
|
obj-$(CONFIG_SPI_ATMEL) += atmel_spi.o
|
2007-05-07 01:50:34 +04:00
|
|
|
obj-$(CONFIG_SPI_BFIN) += spi_bfin5xx.o
|
|
|
|
|
obj-$(CONFIG_SPI_BITBANG) += spi_bitbang.o
|
2007-05-08 11:32:25 +04:00
|
|
|
obj-$(CONFIG_SPI_AU1550) += au1550_spi.o
|
2006-01-09 00:34:29 +03:00
|
|
|
obj-$(CONFIG_SPI_BUTTERFLY) += spi_butterfly.o
|
2007-02-12 11:52:39 +03:00
|
|
|
obj-$(CONFIG_SPI_IMX) += spi_imx.o
|
2007-07-17 15:04:05 +04:00
|
|
|
obj-$(CONFIG_SPI_LM70_LLP) += spi_lm70llp.o
|
2006-03-08 10:53:24 +03:00
|
|
|
obj-$(CONFIG_SPI_PXA2XX) += pxa2xx_spi.o
|
2007-02-12 11:52:37 +03:00
|
|
|
obj-$(CONFIG_SPI_OMAP_UWIRE) += omap_uwire.o
|
2007-07-17 15:04:13 +04:00
|
|
|
obj-$(CONFIG_SPI_OMAP24XX) += omap2_mcspi.o
|
2007-05-11 09:22:52 +04:00
|
|
|
obj-$(CONFIG_SPI_MPC52xx_PSC) += mpc52xx_psc_spi.o
|
2006-05-21 02:00:15 +04:00
|
|
|
obj-$(CONFIG_SPI_MPC83xx) += spi_mpc83xx.o
|
2006-05-21 02:00:17 +04:00
|
|
|
obj-$(CONFIG_SPI_S3C24XX_GPIO) += spi_s3c24xx_gpio.o
|
2006-05-21 02:00:18 +04:00
|
|
|
obj-$(CONFIG_SPI_S3C24XX) += spi_s3c24xx.o
|
2007-07-17 15:04:15 +04:00
|
|
|
obj-$(CONFIG_SPI_TXX9) += spi_txx9.o
|
2007-07-17 15:04:11 +04:00
|
|
|
obj-$(CONFIG_SPI_XILINX) += xilinx_spi.o
|
[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 above this line ...
|
|
|
|
|
|
|
|
|
|
# SPI protocol drivers (device/link on bus)
|
2007-02-12 11:52:48 +03:00
|
|
|
obj-$(CONFIG_SPI_AT25) += at25.o
|
2007-05-08 11:32:15 +04:00
|
|
|
obj-$(CONFIG_SPI_SPIDEV) += spidev.o
|
2007-07-17 15:04:10 +04:00
|
|
|
obj-$(CONFIG_SPI_TLE62X0) += tle62x0.o
|
[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 above this line ...
|
|
|
|
|
|
|
|
|
|
# SPI slave controller drivers (upstream link)
|
|
|
|
|
# ... add above this line ...
|
|
|
|
|
|
|
|
|
|
# SPI slave drivers (protocol for that link)
|
|
|
|
|
# ... add above this line ...
|
