[deliverable/linux.git] / drivers / spi / Kconfig

#
# 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.
#
menu "SPI support"

config SPI
	bool "SPI support"
	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.

	  SPI is widely used by microcontrollers to talk with sensors,
	  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.

config SPI_DEBUG
	boolean "Debug support for SPI drivers"
	depends on SPI && DEBUG_KERNEL
	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.

comment "SPI Master Controller Drivers"
	depends on SPI_MASTER

config SPI_ATMEL
	tristate "Atmel SPI Controller"
	depends on (ARCH_AT91 || AVR32) && SPI_MASTER
	help
	  This selects a driver for the Atmel SPI Controller, present on
	  many AT32 (AVR32) and AT91 (ARM) chips.

config SPI_BITBANG
	tristate "Bitbanging SPI master"
	depends on SPI_MASTER && EXPERIMENTAL
	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.

config SPI_BUTTERFLY
	tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
	depends on SPI_MASTER && PARPORT && EXPERIMENTAL
	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.

config SPI_IMX
	tristate "Freescale iMX SPI controller"
	depends on SPI_MASTER && ARCH_IMX && EXPERIMENTAL
	help
	  This enables using the Freescale iMX SPI controller in master
	  mode.

config SPI_MPC83xx
	tristate "Freescale MPC83xx SPI controller"
	depends on SPI_MASTER && PPC_83xx && EXPERIMENTAL
	select SPI_BITBANG
	help
	  This enables using the Freescale MPC83xx SPI controller in master
	  mode.

	  Note, this driver uniquely supports the SPI controller on the MPC83xx
	  family of PowerPC processors.  The MPC83xx uses a simple set of shift
	  registers for data (opposed to the CPM based descriptor model).

config SPI_OMAP_UWIRE
	tristate "OMAP1 MicroWire"
	depends on SPI_MASTER && ARCH_OMAP1
	select SPI_BITBANG
	help
	  This hooks up to the MicroWire controller on OMAP1 chips.


config SPI_PXA2XX
	tristate "PXA2xx SSP SPI master"
	depends on SPI_MASTER && ARCH_PXA && EXPERIMENTAL
	help
	  This enables using a PXA2xx 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_S3C24XX
	tristate "Samsung S3C24XX series SPI"
	depends on SPI_MASTER && ARCH_S3C2410 && EXPERIMENTAL
	help
	  SPI driver for Samsung S3C24XX series ARM SoCs

config SPI_S3C24XX_GPIO
	tristate "Samsung S3C24XX series SPI by GPIO"
	depends on SPI_MASTER && ARCH_S3C2410 && SPI_BITBANG && EXPERIMENTAL
	help
	  SPI driver for Samsung S3C24XX series ARM SoCs using
	  GPIO lines to provide the SPI bus. This can be used where
	  the inbuilt hardware cannot provide the transfer mode, or
	  where the board is using non hardware connected pins.
#
# 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"
	depends on SPI_MASTER

config SPI_AT25
	tristate "SPI EEPROMs from most vendors"
	depends on SPI_MASTER && SYSFS
	help
	  Enable this driver to get read/write support to most SPI EEPROMs,
	  after you configure the board init code to know about each eeprom
	  on your target board.

	  This driver can also be built as a module.  If so, the module
	  will be called at25.

#
# Add new SPI protocol masters in alphabetical order above this line
#


# (slave support would go here)

endmenu # "SPI support"
Commit	Line	Data
8ae12a0d DB	1	#
	2	# SPI driver configuration
	3	#
	4	# NOTE: the reason this doesn't show SPI slave support is mostly that
	5	# nobody's needed a slave side API yet. The master-role API is not
	6	# fully appropriate there, so it'd need some thought to do well.
	7	#
	8	menu "SPI support"
	9
	10	config SPI
	11	bool "SPI support"
	12	help
	13	The "Serial Peripheral Interface" is a low level synchronous
	14	protocol. Chips that support SPI can have data transfer rates
	15	up to several tens of Mbit/sec. Chips are addressed with a
	16	controller and a chipselect. Most SPI slaves don't support
	17	dynamic device discovery; some are even write-only or read-only.
	18
3cb2fccc	19	SPI is widely used by microcontrollers to talk with sensors,
8ae12a0d DB	20	eeprom and flash memory, codecs and various other controller
	21	chips, analog to digital (and d-to-a) converters, and more.
	22	MMC and SD cards can be accessed using SPI protocol; and for
	23	DataFlash cards used in MMC sockets, SPI must always be used.
	24
	25	SPI is one of a family of similar protocols using a four wire
	26	interface (select, clock, data in, data out) including Microwire
	27	(half duplex), SSP, SSI, and PSP. This driver framework should
	28	work with most such devices and controllers.
	29
	30	config SPI_DEBUG
	31	boolean "Debug support for SPI drivers"
	32	depends on SPI && DEBUG_KERNEL
	33	help
	34	Say "yes" to enable debug messaging (like dev_dbg and pr_debug),
	35	sysfs, and debugfs support in SPI controller and protocol drivers.
	36
	37	#
	38	# MASTER side ... talking to discrete SPI slave chips including microcontrollers
	39	#
	40
	41	config SPI_MASTER
	42	# boolean "SPI Master Support"
	43	boolean
	44	default SPI
	45	help
	46	If your system has an master-capable SPI controller (which
	47	provides the clock and chipselect), you can enable that
	48	controller and the protocol drivers for the SPI slave chips
	49	that are connected.
	50
	51	comment "SPI Master Controller Drivers"
	52	depends on SPI_MASTER
	53
754ce4f2 HS	54	config SPI_ATMEL
	55	tristate "Atmel SPI Controller"
	56	depends on (ARCH_AT91 \|\| AVR32) && SPI_MASTER
	57	help
	58	This selects a driver for the Atmel SPI Controller, present on
	59	many AT32 (AVR32) and AT91 (ARM) chips.
	60
9904f22a DB	61	config SPI_BITBANG
	62	tristate "Bitbanging SPI master"
	63	depends on SPI_MASTER && EXPERIMENTAL
	64	help
	65	With a few GPIO pins, your system can bitbang the SPI protocol.
	66	Select this to get SPI support through I/O pins (GPIO, parallel
	67	port, etc). Or, some systems' SPI master controller drivers use
	68	this code to manage the per-word or per-transfer accesses to the
	69	hardware shift registers.
	70
	71	This is library code, and is automatically selected by drivers that
	72	need it. You only need to select this explicitly to support driver
	73	modules that aren't part of this kernel tree.
8ae12a0d	74
7111763d DB	75	config SPI_BUTTERFLY
	76	tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
	77	depends on SPI_MASTER && PARPORT && EXPERIMENTAL
	78	select SPI_BITBANG
	79	help
	80	This uses a custom parallel port cable to connect to an AVR
	81	Butterfly <http://www.atmel.com/products/avr/butterfly>, an
	82	inexpensive battery powered microcontroller evaluation board.
	83	This same cable can be used to flash new firmware.
	84
69c202af AP	85	config SPI_IMX
	86	tristate "Freescale iMX SPI controller"
	87	depends on SPI_MASTER && ARCH_IMX && EXPERIMENTAL
	88	help
	89	This enables using the Freescale iMX SPI controller in master
	90	mode.
	91
ccf06998 KG	92	config SPI_MPC83xx
	93	tristate "Freescale MPC83xx SPI controller"
	94	depends on SPI_MASTER && PPC_83xx && EXPERIMENTAL
	95	select SPI_BITBANG
	96	help
	97	This enables using the Freescale MPC83xx SPI controller in master
	98	mode.
	99
	100	Note, this driver uniquely supports the SPI controller on the MPC83xx
	101	family of PowerPC processors. The MPC83xx uses a simple set of shift
	102	registers for data (opposed to the CPM based descriptor model).
	103
fdb3c18d DB	104	config SPI_OMAP_UWIRE
	105	tristate "OMAP1 MicroWire"
	106	depends on SPI_MASTER && ARCH_OMAP1
	107	select SPI_BITBANG
	108	help
	109	This hooks up to the MicroWire controller on OMAP1 chips.
	110
69c202af	111
e0c9905e SS	112	config SPI_PXA2XX
	113	tristate "PXA2xx SSP SPI master"
	114	depends on SPI_MASTER && ARCH_PXA && EXPERIMENTAL
	115	help
	116	This enables using a PXA2xx SSP port as a SPI master controller.
	117	The driver can be configured to use any SSP port and additional
	118	documentation can be found a Documentation/spi/pxa2xx.
	119
85abfaa7 DB	120	config SPI_S3C24XX
	121	tristate "Samsung S3C24XX series SPI"
	122	depends on SPI_MASTER && ARCH_S3C2410 && EXPERIMENTAL
	123	help
	124	SPI driver for Samsung S3C24XX series ARM SoCs
	125
1fc7547d BD	126	config SPI_S3C24XX_GPIO
	127	tristate "Samsung S3C24XX series SPI by GPIO"
	128	depends on SPI_MASTER && ARCH_S3C2410 && SPI_BITBANG && EXPERIMENTAL
	129	help
	130	SPI driver for Samsung S3C24XX series ARM SoCs using
	131	GPIO lines to provide the SPI bus. This can be used where
	132	the inbuilt hardware cannot provide the transfer mode, or
	133	where the board is using non hardware connected pins.
8ae12a0d DB	134	#
	135	# Add new SPI master controllers in alphabetical order above this line
	136	#
	137
8ae12a0d DB	138	#
	139	# There are lots of SPI device types, with sensors and memory
	140	# being probably the most widely used ones.
	141	#
	142	comment "SPI Protocol Masters"
	143	depends on SPI_MASTER
	144
b587b13a DB	145	config SPI_AT25
	146	tristate "SPI EEPROMs from most vendors"
	147	depends on SPI_MASTER && SYSFS
	148	help
	149	Enable this driver to get read/write support to most SPI EEPROMs,
	150	after you configure the board init code to know about each eeprom
	151	on your target board.
	152
	153	This driver can also be built as a module. If so, the module
	154	will be called at25.
8ae12a0d DB	155
	156	#
	157	# Add new SPI protocol masters in alphabetical order above this line
	158	#
	159
	160
	161	# (slave support would go here)
	162
	163	endmenu # "SPI support"
	164