[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
#
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
2014-12-20 23:41:11 +03:00
bool "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
2014-12-20 23:41:11 +03:00
# bool "SPI Master Support"
bool
[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
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"
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"
2013-03-28 15:34:56 +04:00
depends on ATH79 && GPIOLIB
2011-01-04 23:28:22 +03:00
select SPI_BITBANG
help
This enables support for the SPI controller present on the
Atheros AR71XX/AR724X/AR913X SoCs.
2016-12-08 17:58:44 +03:00
config SPI_ARMADA_3700
tristate "Marvell Armada 3700 SPI Controller"
depends on (ARCH_MVEBU && OF) || COMPILE_TEST
help
This enables support for the SPI controller present on the
Marvell Armada 3700 SoCs.
2007-02-14 11:33:09 +03:00
config SPI_ATMEL
tristate "Atmel SPI Controller"
2014-08-29 20:10:31 +04:00
depends on HAS_DMA
2018-03-08 01:30:54 +03:00
depends on ARCH_AT91 || COMPILE_TEST
2007-02-14 11:33:09 +03:00
help
This selects a driver for the Atmel SPI Controller, present on
2018-03-08 01:30:54 +03:00
many AT91 ARM chips.
2007-02-14 11:33:09 +03:00
2016-02-02 14:27:42 +03:00
config SPI_AU1550
tristate "Au1550/Au1200/Au1300 SPI Controller"
depends on MIPS_ALCHEMY
select SPI_BITBANG
help
If you say yes to this option, support will be included for the
PSC SPI controller found on Au1550, Au1200 and Au1300 series.
2016-02-04 19:13:30 +03:00
config SPI_AXI_SPI_ENGINE
tristate "Analog Devices AXI SPI Engine controller"
depends on HAS_IOMEM
help
This enables support for the Analog Devices AXI SPI Engine SPI controller.
It is part of the SPI Engine framework that is used in some Analog Devices
reference designs for FPGAs.
2013-03-12 07:38:24 +04:00
config SPI_BCM2835
tristate "BCM2835 SPI controller"
2015-05-03 18:16:36 +03:00
depends on GPIOLIB
2013-07-05 22:42:58 +04:00
depends on ARCH_BCM2835 || COMPILE_TEST
2013-03-12 07:38:24 +04:00
help
This selects a driver for the Broadcom BCM2835 SPI master.
The BCM2835 contains two types of SPI master controller; the
"universal SPI master", and the regular SPI controller. This driver
is for the regular SPI controller. Slave mode operation is not also
not supported.
2015-09-11 14:22:04 +03:00
config SPI_BCM2835AUX
tristate "BCM2835 SPI auxiliary controller"
2016-02-07 17:12:29 +03:00
depends on (ARCH_BCM2835 && GPIOLIB) || COMPILE_TEST
2015-09-11 14:22:04 +03:00
help
This selects a driver for the Broadcom BCM2835 SPI aux master.
The BCM2835 contains two types of SPI master controller; the
"universal SPI master", and the regular SPI controller.
This driver is for the universal/auxiliary SPI controller.
2014-08-17 20:33:38 +04:00
config SPI_BCM53XX
tristate "Broadcom BCM53xx SPI controller"
depends on ARCH_BCM_5301X
2014-09-26 10:18:31 +04:00
depends on BCMA_POSSIBLE
select BCMA
2014-08-17 20:33:38 +04:00
help
Enable support for the SPI controller on Broadcom BCM53xx ARM SoCs.
2012-02-01 14:14:09 +04:00
config SPI_BCM63XX
tristate "Broadcom BCM63xx SPI controller"
2015-10-12 13:24:23 +03:00
depends on BCM63XX || COMPILE_TEST
2012-02-01 14:14:09 +04:00
help
Enable support for the SPI controller on the Broadcom BCM63xx SoCs.
2013-11-30 15:42:06 +04:00
config SPI_BCM63XX_HSSPI
tristate "Broadcom BCM63XX HS SPI controller driver"
depends on BCM63XX || COMPILE_TEST
help
This enables support for the High Speed SPI controller present on
newer Broadcom BCM63XX SoCs.
2016-08-25 01:04:23 +03:00
config SPI_BCM_QSPI
tristate "Broadcom BSPI and MSPI controller support"
2016-12-30 09:30:00 +03:00
depends on ARCH_BRCMSTB || ARCH_BCM || ARCH_BCM_IPROC || \
BMIPS_GENERIC || COMPILE_TEST
2016-08-25 01:04:23 +03:00
default ARCH_BCM_IPROC
help
Enables support for the Broadcom SPI flash and MSPI controller.
Select this option for any one of BRCMSTB, iProc NSP and NS2 SoCs
based platforms. This driver works for both SPI master for spi-nor
flash device as well as MSPI device.
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.
2014-04-14 13:06:53 +04:00
config SPI_CADENCE
tristate "Cadence SPI controller"
help
This selects the Cadence SPI controller master driver
2015-03-09 11:46:15 +03:00
used by Xilinx Zynq and ZynqMP.
2014-04-14 13:06:53 +04:00
2012-11-07 21:30:29 +04:00
config SPI_CLPS711X
tristate "CLPS711X host SPI controller"
2014-03-26 12:53:18 +04:00
depends on ARCH_CLPS711X || COMPILE_TEST
2012-11-07 21:30:29 +04:00
help
This enables dedicated general purpose SPI/Microwire1-compatible
master mode interface (SSI1) for CLPS711X-based CPUs.
2010-01-20 23:49:44 +03:00
config SPI_COLDFIRE_QSPI
tristate "Freescale Coldfire QSPI controller"
2012-06-05 20:24:59 +04:00
depends on (M520x || M523x || M5249 || M525x || M527x || M528x || M532x)
2010-01-20 23:49:44 +03:00
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"
2013-07-25 04:31:37 +04:00
depends on ARCH_DAVINCI || ARCH_KEYSTONE
2009-12-17 01:02:18 +03:00
select SPI_BITBANG
help
2010-10-12 10:28:02 +04:00
SPI master controller for DaVinci/DA8x/OMAP-L/AM1x SPI modules.
2016-02-02 14:27:42 +03:00
config SPI_DESIGNWARE
tristate "DesignWare SPI controller core support"
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
config SPI_DW_MID_DMA
bool "DMA support for DW SPI controller on Intel MID platform"
depends on SPI_DW_PCI && DW_DMAC_PCI
config SPI_DW_MMIO
tristate "Memory-mapped io interface driver for DW SPI core"
depends on SPI_DESIGNWARE
2014-12-08 16:52:29 +03:00
config SPI_DLN2
tristate "Diolan DLN-2 USB SPI adapter"
depends on MFD_DLN2
help
If you say yes to this option, support will be included for Diolan
DLN2, a USB to SPI interface.
This driver can also be built as a module. If so, the module
will be called spi-dln2.
2013-08-08 18:09:50 +04:00
config SPI_EFM32
tristate "EFM32 SPI controller"
depends on OF && ARM && (ARCH_EFM32 || COMPILE_TEST)
select SPI_BITBANG
help
Driver for the spi controller found on Energy Micro's EFM32 SoCs.
2010-05-06 08:47:04 +04:00
config SPI_EP93XX
tristate "Cirrus Logic EP93xx SPI controller"
2014-08-29 20:10:31 +04:00
depends on HAS_DMA
2013-07-05 22:42:58 +04:00
depends on ARCH_EP93XX || COMPILE_TEST
2010-05-06 08:47:04 +04:00
help
This enables using the Cirrus EP93xx SPI controller in master
mode.
2012-05-20 17:46:19 +04:00
config SPI_FALCON
2017-01-03 20:04:27 +03:00
bool "Falcon SPI controller support"
2012-05-20 17:46:19 +04:00
depends on SOC_FALCON
help
The external bus unit (EBU) found on the FALC-ON SoC has SPI
emulation that is designed for serial flash access. This driver
has only been tested with m25p80 type chips. The hardware has no
support for other types of SPI peripherals.
2016-11-22 16:52:17 +03:00
config SPI_FSL_LPSPI
tristate "Freescale i.MX LPSPI controller"
depends on ARCH_MXC || COMPILE_TEST
help
This enables Freescale i.MX LPSPI controllers in master mode.
2009-01-07 01:41:41 +03:00
config SPI_GPIO
tristate "GPIO-based bitbanging SPI Master"
2015-05-05 19:32:33 +03:00
depends on GPIOLIB || COMPILE_TEST
2009-01-07 01:41:41 +03:00
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.
2014-11-14 21:48:32 +03:00
config SPI_IMG_SPFI
tristate "IMG SPFI controller"
depends on MIPS || COMPILE_TEST
help
This enables support for the SPFI master controller found on
IMG SoCs.
2009-09-23 03:46:02 +04:00
config SPI_IMX
tristate "Freescale i.MX SPI controllers"
2013-07-05 22:42:58 +04:00
depends on ARCH_MXC || COMPILE_TEST
2009-09-23 03:46:02 +04:00
select SPI_BITBANG
help
This enables using the Freescale i.MX SPI controllers in master
mode.
2016-08-04 07:30:37 +03:00
config SPI_JCORE
tristate "J-Core SPI Master"
depends on OF && (SUPERH || COMPILE_TEST)
help
This enables support for the SPI master controller in the J-Core
synthesizable, open source SoC.
2007-07-17 15:04:05 +04:00
config SPI_LM70_LLP
tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
2013-01-17 06:53:55 +04:00
depends on PARPORT
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.
2016-02-23 13:44:28 +03:00
config SPI_LP8841_RTC
tristate "ICP DAS LP-8841 SPI Controller for RTC"
depends on MACH_PXA27X_DT || COMPILE_TEST
help
This driver provides an SPI master device to drive Maxim
DS-1302 real time clock.
Say N here unless you plan to run the kernel on an ICP DAS
LP-8x4x industrial computer.
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"
2013-01-17 06:53:55 +04:00
depends on PPC_MPC52xx
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"
2012-02-23 13:37:55 +04:00
depends on PPC_MPC512x
2010-04-30 17:21:27 +04:00
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
2013-02-15 19:52:21 +04:00
tristate
depends on OF
config SPI_FSL_CPM
2010-10-12 14:18:31 +04:00
tristate
depends on FSL_SOC
2010-10-12 14:18:30 +04:00
config SPI_FSL_SPI
2015-01-06 16:07:34 +03:00
tristate "Freescale SPI controller and Aeroflex Gaisler GRLIB SPI controller"
2013-02-15 19:52:21 +04:00
depends on OF
2010-10-12 14:18:31 +04:00
select SPI_FSL_LIB
2013-02-15 19:52:21 +04:00
select SPI_FSL_CPM if FSL_SOC
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.
2013-02-15 19:52:26 +04:00
This also enables using the Aeroflex Gaisler GRLIB SPI controller in
master mode.
2006-05-21 02:00:15 +04:00
2013-08-16 07:08:55 +04:00
config SPI_FSL_DSPI
tristate "Freescale DSPI controller"
2014-02-12 11:29:05 +04:00
select REGMAP_MMIO
2016-12-14 15:28:05 +03:00
depends on HAS_DMA
2017-10-28 01:23:01 +03:00
depends on SOC_VF610 || SOC_LS1021A || ARCH_LAYERSCAPE || M5441x || COMPILE_TEST
2013-08-16 07:08:55 +04:00
help
This enables support for the Freescale DSPI controller in master
mode. VF610 platform uses the 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
config SPI_FSL_ESPI
2015-01-06 16:07:34 +03:00
tristate "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
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.
2017-05-23 16:39:33 +03:00
config SPI_MESON_SPICC
tristate "Amlogic Meson SPICC controller"
depends on ARCH_MESON || COMPILE_TEST
help
This enables master mode support for the SPICC (SPI communication
controller) available in Amlogic Meson SoCs.
2014-11-22 18:21:41 +03:00
config SPI_MESON_SPIFC
tristate "Amlogic Meson SPIFC controller"
depends on ARCH_MESON || COMPILE_TEST
2014-11-27 02:07:48 +03:00
select REGMAP_MMIO
2014-11-22 18:21:41 +03:00
help
This enables master mode support for the SPIFC (SPI flash
controller) available in Amlogic Meson SoCs.
2015-08-07 10:19:50 +03:00
config SPI_MT65XX
tristate "MediaTek SPI controller"
depends on ARCH_MEDIATEK || COMPILE_TEST
help
This selects the MediaTek(R) SPI bus driver.
If you want to use MediaTek(R) SPI interface,
say Y or M here.If you are not sure, say N.
SPI drivers for Mediatek MT65XX and MT81XX series ARM SoCs.
2016-02-02 14:27:42 +03:00
config SPI_NUC900
tristate "Nuvoton NUC900 series SPI"
depends on ARCH_W90X900
select SPI_BITBANG
help
SPI driver for Nuvoton NUC900 series ARM SoCs
2017-02-14 02:31:11 +03:00
config SPI_LANTIQ_SSC
tristate "Lantiq SSC SPI controller"
2017-02-18 19:06:48 +03:00
depends on LANTIQ || COMPILE_TEST
2017-02-14 02:31:11 +03:00
help
This driver supports the Lantiq SSC SPI controller in master
mode. This controller is found on Intel (former Lantiq) SoCs like
the Danube, Falcon, xRX200, xRX300.
2011-02-14 05:20:39 +03:00
config SPI_OC_TINY
tristate "OpenCores tiny SPI"
2015-05-05 19:32:33 +03:00
depends on GPIOLIB || COMPILE_TEST
2011-02-14 05:20:39 +03:00
select SPI_BITBANG
help
This is the driver for OpenCores tiny SPI master controller.
2012-08-22 23:25:07 +04:00
config SPI_OCTEON
tristate "Cavium OCTEON SPI controller"
2013-05-22 19:10:46 +04:00
depends on CAVIUM_OCTEON_SOC
2012-08-22 23:25:07 +04:00
help
SPI host driver for the hardware found on some Cavium OCTEON
SOCs.
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"
2014-08-29 20:10:31 +04:00
depends on HAS_DMA
2013-07-05 22:42:58 +04:00
depends on ARCH_OMAP2PLUS || COMPILE_TEST
2016-07-07 20:17:49 +03:00
select SG_SPLIT
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
2013-08-20 17:25:48 +04:00
config SPI_TI_QSPI
tristate "DRA7xxx QSPI controller support"
2017-05-04 10:37:18 +03:00
depends on HAS_DMA
2013-08-20 17:25:48 +04:00
depends on ARCH_OMAP2PLUS || COMPILE_TEST
help
QSPI master controller for DRA7xxx used for flash devices.
This device supports single, dual and quad read support, while
it only supports single write mode.
2009-12-13 11:02:11 +03:00
config SPI_OMAP_100K
tristate "OMAP SPI 100K"
2013-07-05 22:42:58 +04:00
depends on ARCH_OMAP850 || ARCH_OMAP730 || COMPILE_TEST
2009-12-13 11:02:11 +03:00
help
OMAP SPI 100K master controller for omap7xx boards.
2008-08-06 00:01:09 +04:00
config SPI_ORION
2013-01-17 06:53:55 +04:00
tristate "Orion SPI master"
2016-04-22 16:17:28 +03:00
depends on PLAT_ORION || ARCH_MVEBU || COMPILE_TEST
2008-08-06 00:01:09 +04:00
help
2016-11-30 13:47:44 +03:00
This enables using the SPI master controller on the Orion
and MVEBU chips.
2008-08-06 00:01:09 +04:00
2016-04-01 14:18:50 +03:00
config SPI_PIC32
tristate "Microchip PIC32 series SPI"
depends on MACH_PIC32 || COMPILE_TEST
help
SPI driver for Microchip PIC32 SPI master controller.
2016-04-15 14:27:19 +03:00
config SPI_PIC32_SQI
tristate "Microchip PIC32 Quad SPI driver"
depends on MACH_PIC32 || COMPILE_TEST
2016-05-13 11:42:53 +03:00
depends on HAS_DMA
2016-04-15 14:27:19 +03:00
help
SPI driver for PIC32 Quad SPI controller.
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"
2012-02-23 13:37:55 +04:00
depends on PPC32 && 4xx
2009-09-23 03:45:58 +04:00
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"
spi: fix building SPI_PXA on MMP
When the audio driver selects CONFIG_PXA_SSP on ARCH_MMP as a
loadable module, and the PXA SPI driver is built-in, we get
a link error in the SPI driver:
drivers/spi/spi-pxa2xx.o: In function `pxa2xx_spi_remove':
spi-pxa2xx.c:(.text+0x5f0): undefined reference to `pxa_ssp_free'
drivers/spi/spi-pxa2xx.o: In function `pxa2xx_spi_probe':
spi-pxa2xx.c:(.text+0xeac): undefined reference to `pxa_ssp_request'
spi-pxa2xx.c:(.text+0x1468): undefined reference to `pxa_ssp_free'
spi-pxa2xx.c:(.text+0x15bc): undefined reference to `pxa_ssp_free'
The problem is that the PXA SPI driver only uses 'select SSP'
specifically when building it for PXA, but we can also build it
for PCI, which is meant for Intel x86 SoCs that use the same SPI
block. When the sound driver forces the SSP to be a loadable
module, the IS_ENABLED() check in include/linux/pxa2xx_ssp.h
triggers but the spi driver can't reference the exported symbols.
I had a different approach before, making the PCI case depend
on X86, which fixed the problem by avoiding the MMP case.
This goes a different route, making the driver select PXA_SSP
also on MMP, which has an SSP that none of the boards in mainline
Linux use for SPI. There is no harm in always enabling the build
on MMP (PCI or not PCI), so I do that too, to document that this
hardware is actually available on MMP.
Link: https://patchwork.kernel.org/patch/8879921/
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Mark Brown <broonie@kernel.org>
2017-08-07 18:42:55 +03:00
depends on (ARCH_PXA || ARCH_MMP || PCI || ACPI)
select PXA_SSP if ARCH_PXA || ARCH_MMP
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
2014-07-24 21:10:54 +04:00
def_tristate SPI_PXA2XX && PCI && COMMON_CLK
2006-03-08 10:53:24 +03:00
2014-07-01 05:03:59 +04:00
config SPI_ROCKCHIP
tristate "Rockchip SPI controller driver"
help
This selects a driver for Rockchip SPI controller.
If you say yes to this option, support will be included for
RK3066, RK3188 and RK3288 families of SPI controller.
Rockchip SPI controller support DMA transport and PIO mode.
The main usecase of this controller is to use spi flash as boot
device.
2015-04-15 18:43:52 +03:00
config SPI_RB4XX
tristate "Mikrotik RB4XX SPI master"
depends on SPI_MASTER && ATH79
help
SPI controller driver for the Mikrotik RB4xx series boards.
2012-03-07 09:46:25 +04:00
config SPI_RSPI
2014-01-21 19:10:09 +04:00
tristate "Renesas RSPI/QSPI controller"
2016-02-18 04:47:52 +03:00
depends on SUPERH || ARCH_RENESAS || COMPILE_TEST
2012-03-07 09:46:25 +04:00
help
2014-01-21 19:10:09 +04:00
SPI driver for Renesas RSPI and QSPI blocks.
2012-03-07 09:46:25 +04:00
2014-02-13 20:21:38 +04:00
config SPI_QUP
tristate "Qualcomm SPI controller with QUP interface"
2014-04-07 18:15:45 +04:00
depends on ARCH_QCOM || (ARM && COMPILE_TEST)
2014-02-13 20:21:38 +04:00
help
Qualcomm Universal Peripheral (QUP) core is an AHB slave that
provides a common data path (an output FIFO and an input FIFO)
for serial peripheral interface (SPI) mini-core. SPI in master
mode supports up to 50MHz, up to four chip selects, programmable
data path from 4 bits to 32 bits and numerous protocol variants.
This driver can also be built as a module. If so, the module
will be called spi_qup.
2012-03-07 09:46:25 +04:00
2007-02-12 11:52:36 +03:00
config SPI_S3C24XX
tristate "Samsung S3C24XX series SPI"
2013-01-17 06:53:55 +04:00
depends on ARCH_S3C24XX
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"
2016-11-07 23:46:52 +03:00
depends on (PLAT_SAMSUNG || ARCH_EXYNOS || COMPILE_TEST)
2009-11-30 10:39:42 +03:00
help
SPI driver for Samsung S3C64XX and newer SoCs.
2012-08-18 20:06:27 +04:00
config SPI_SC18IS602
tristate "NXP SC18IS602/602B/603 I2C to SPI bridge"
depends on I2C
help
SPI driver for NXP SC18IS602/602B/603 I2C to SPI bridge.
2009-11-26 14:10:05 +03:00
config SPI_SH_MSIOF
tristate "SuperH MSIOF SPI controller"
2014-07-10 01:27:08 +04:00
depends on HAVE_CLK && HAS_DMA
2016-08-31 12:37:05 +03:00
depends on ARCH_SHMOBILE || ARCH_RENESAS || COMPILE_TEST
2009-11-26 14:10:05 +03:00
help
2012-11-07 15:40:05 +04:00
SPI driver for SuperH and SH Mobile MSIOF blocks.
2009-11-26 14:10:05 +03:00
2011-02-15 04:30:32 +03:00
config SPI_SH
tristate "SuperH SPI controller"
2013-07-05 22:42:58 +04:00
depends on SUPERH || COMPILE_TEST
2011-02-15 04:30:32 +03:00
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.
2012-03-02 05:10:17 +04:00
config SPI_SH_HSPI
tristate "SuperH HSPI controller"
2016-02-18 04:47:52 +03:00
depends on ARCH_RENESAS || COMPILE_TEST
2012-03-02 05:10:17 +04:00
help
SPI driver for SuperH HSPI blocks.
2012-02-13 13:45:38 +04:00
config SPI_SIRF
tristate "CSR SiRFprimaII SPI controller"
2013-08-06 14:37:32 +04:00
depends on SIRF_DMA
2012-02-13 13:45:38 +04:00
select SPI_BITBANG
help
SPI driver for CSR SiRFprimaII SoCs
2017-09-15 10:29:16 +03:00
config SPI_SPRD_ADI
tristate "Spreadtrum ADI controller"
depends on ARCH_SPRD || COMPILE_TEST
2017-10-05 23:39:37 +03:00
depends on HWSPINLOCK || (COMPILE_TEST && !HWSPINLOCK)
2017-09-15 10:29:16 +03:00
help
ADI driver based on SPI for Spreadtrum SoCs.
2017-06-21 17:32:06 +03:00
config SPI_STM32
tristate "STMicroelectronics STM32 SPI controller"
depends on ARCH_STM32 || COMPILE_TEST
help
SPI driver for STMicroelectonics STM32 SoCs.
STM32 SPI controller supports DMA and PIO modes. When DMA
is not available, the driver automatically falls back to
PIO mode.
2014-12-09 23:21:30 +03:00
config SPI_ST_SSC4
tristate "STMicroelectronics SPI SSC-based driver"
2016-04-29 08:38:41 +03:00
depends on ARCH_STI || COMPILE_TEST
2014-12-09 23:21:30 +03:00
help
STMicroelectronics SoCs support for SPI. If you say yes to
this option, support will be included for the SSC driven SPI.
spi: sunxi: Add Allwinner A10 SPI controller driver
The older Allwinner SoCs (A10, A13, A10s and A20) all have the same SPI
controller.
Unfortunately, this SPI controller, even though quite similar, is significantly
different from the recently supported A31 SPI controller (different registers
offset, split/merged registers, etc.). Supporting both controllers in a single
driver would be unreasonable, hence the addition of a new driver.
Like its more recent counterpart, it supports DMA, but the driver only does PIO
until we have a dmaengine driver for this platform.
Signed-off-by: Maxime Ripard <maxime.ripard@free-electrons.com>
Signed-off-by: Mark Brown <broonie@linaro.org>
2014-02-23 01:35:53 +04:00
config SPI_SUN4I
tristate "Allwinner A10 SoCs SPI controller"
depends on ARCH_SUNXI || COMPILE_TEST
help
SPI driver for Allwinner sun4i, sun5i and sun7i SoCs
2014-02-05 17:05:05 +04:00
config SPI_SUN6I
tristate "Allwinner A31 SPI controller"
depends on ARCH_SUNXI || COMPILE_TEST
2014-02-06 14:53:51 +04:00
depends on RESET_CONTROLLER
2014-02-05 17:05:05 +04:00
help
This enables using the SPI controller on the Allwinner A31 SoCs.
2012-08-03 19:26:11 +04:00
config SPI_MXS
tristate "Freescale MXS SPI controller"
depends on ARCH_MXS
select STMP_DEVICE
help
SPI driver for Freescale MXS devices.
2013-02-22 16:37:39 +04:00
config SPI_TEGRA114
tristate "NVIDIA Tegra114 SPI Controller"
2013-07-05 22:42:58 +04:00
depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST
2014-08-29 20:10:31 +04:00
depends on RESET_CONTROLLER && HAS_DMA
2013-02-22 16:37:39 +04:00
help
SPI driver for NVIDIA Tegra114 SPI Controller interface. This controller
is different than the older SoCs SPI controller and also register interface
get changed with this controller.
2012-11-14 04:24:47 +04:00
config SPI_TEGRA20_SFLASH
tristate "Nvidia Tegra20 Serial flash Controller"
2013-07-05 22:42:58 +04:00
depends on ARCH_TEGRA || COMPILE_TEST
2013-11-07 03:31:24 +04:00
depends on RESET_CONTROLLER
2012-11-14 04:24:47 +04:00
help
SPI driver for Nvidia Tegra20 Serial flash Controller interface.
The main usecase of this controller is to use spi flash as boot
device.
2012-10-30 11:04:05 +04:00
config SPI_TEGRA20_SLINK
tristate "Nvidia Tegra20/Tegra30 SLINK Controller"
2013-07-05 22:42:58 +04:00
depends on (ARCH_TEGRA && TEGRA20_APB_DMA) || COMPILE_TEST
2014-08-29 20:10:31 +04:00
depends on RESET_CONTROLLER && HAS_DMA
2012-10-30 11:04:05 +04:00
help
SPI driver for Nvidia Tegra20/Tegra30 SLINK Controller interface.
2016-08-19 17:03:20 +03:00
config SPI_THUNDERX
tristate "Cavium ThunderX SPI controller"
depends on PCI && 64BIT && (ARM64 || COMPILE_TEST)
help
SPI host driver for the hardware found on Cavium ThunderX
SOCs.
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"
2015-11-30 19:21:42 +03:00
depends on PCI && (X86_32 || MIPS || COMPILE_TEST)
2010-10-08 22:44:49 +04:00
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"
2013-07-05 22:42:58 +04:00
depends on GPIOLIB && (CPU_TX49XX || COMPILE_TEST)
2007-07-17 15:04:15 +04:00
help
SPI driver for Toshiba TXx9 MIPS SoCs
2012-07-19 20:44:07 +04:00
config SPI_XCOMM
tristate "Analog Devices AD-FMCOMMS1-EBZ SPI-I2C-bridge driver"
depends on I2C
help
Support for the SPI-I2C bridge found on the Analog Devices
AD-FMCOMMS1-EBZ board.
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"
2013-01-17 06:53:55 +04:00
depends on HAS_IOMEM
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)"
2015-08-27 15:19:28 +03:00
config SPI_XLP
tristate "Netlogic XLP SPI controller driver"
2017-03-12 14:11:43 +03:00
depends on CPU_XLP || ARCH_THUNDER2 || COMPILE_TEST
2015-08-27 15:19:28 +03:00
help
Enable support for the SPI controller on the Netlogic XLP SoCs.
Currently supported XLP variants are XLP8XX, XLP3XX, XLP2XX, XLP9XX
and XLP5XX.
If you have a Netlogic XLP platform say Y here.
If unsure, say N.
2014-03-12 21:55:24 +04:00
config SPI_XTENSA_XTFPGA
tristate "Xtensa SPI controller for xtfpga"
2014-03-20 14:08:04 +04:00
depends on (XTENSA && XTENSA_PLATFORM_XTFPGA) || COMPILE_TEST
2014-03-12 21:55:24 +04:00
select SPI_BITBANG
help
SPI driver for xtfpga SPI master controller.
This simple SPI master controller is built into xtfpga bitstreams
and is used to control daughterboard audio codec. It always transfers
16 bit words in SPI mode 0, automatically asserting CS on transfer
start and deasserting on end.
2015-06-10 13:38:21 +03:00
config SPI_ZYNQMP_GQSPI
tristate "Xilinx ZynqMP GQSPI controller"
2015-06-26 15:07:12 +03:00
depends on SPI_MASTER && HAS_DMA
2015-06-10 13:38:21 +03:00
help
Enables Xilinx GQSPI controller driver for Zynq UltraScale+ MPSoC.
[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
#
#
# 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"
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.
2015-11-27 19:17:21 +03:00
config SPI_LOOPBACK_TEST
tristate "spi loopback test framework support"
depends on m
help
This enables the SPI loopback testing framework driver
primarily used for development of spi_master drivers
and to detect regressions
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
2017-05-22 16:11:41 +03:00
#
# SLAVE side ... listening to other SPI masters
#
config SPI_SLAVE
bool "SPI slave protocol handlers"
help
If your system has a slave-capable SPI controller, you can enable
slave protocol handlers.
if SPI_SLAVE
2017-05-22 16:11:44 +03:00
config SPI_SLAVE_TIME
tristate "SPI slave handler reporting boot up time"
help
SPI slave handler responding with the time of reception of the last
SPI message.
2017-05-22 16:11:45 +03:00
config SPI_SLAVE_SYSTEM_CONTROL
tristate "SPI slave handler controlling system state"
help
SPI slave handler to allow remote control of system reboot, power
off, halt, and suspend.
2017-05-22 16:11:41 +03:00
endif # SPI_SLAVE
[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
2008-04-28 13:14:16 +04:00
endif # SPI
