[net-next-2.6.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.
#
menuconfig SPI
	bool "SPI support"
	depends on HAS_IOMEM
	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.

if SPI

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

if SPI_MASTER

comment "SPI Master Controller Drivers"

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

config SPI_BFIN
	tristate "SPI controller driver for ADI Blackfin5xx"
	depends on BLACKFIN
	help
	  This is the SPI controller master driver for Blackfin 5xx processor.

config SPI_AU1550
	tristate "Au1550/Au12x0 SPI Controller"
	depends on (SOC_AU1550 || SOC_AU1200) && EXPERIMENTAL
	select SPI_BITBANG
	help
	  If you say yes to this option, support will be included for the
	  Au1550 SPI controller (may also work with Au1200,Au1210,Au1250).

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

config SPI_BITBANG
	tristate "Utilities for Bitbanging SPI masters"
	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 PARPORT
	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_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.

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

config SPI_LM70_LLP
	tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
	depends on PARPORT && EXPERIMENTAL
	select SPI_BITBANG
	help
	  This driver supports the NS LM70 LLP Evaluation Board,
	  which interfaces to an LM70 temperature sensor using
	  a parallel port.

config SPI_MPC52xx_PSC
	tristate "Freescale MPC52xx PSC SPI controller"
	depends on PPC_MPC52xx && EXPERIMENTAL
	help
	  This enables using the Freescale MPC52xx Programmable Serial
	  Controller in master SPI mode.

config SPI_MPC83xx
	tristate "Freescale MPC83xx/QUICC Engine SPI controller"
	depends on (PPC_83xx || QUICC_ENGINE) && EXPERIMENTAL
	help
	  This enables using the Freescale MPC83xx and QUICC Engine SPI
	  controllers in master mode.

	  Note, this driver uniquely supports the SPI controller on the MPC83xx
	  family of PowerPC processors, plus processors with QUICC Engine
	  technology. This driver 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 ARCH_OMAP1
	select SPI_BITBANG
	help
	  This hooks up to the MicroWire controller on OMAP1 chips.

config SPI_OMAP24XX
	tristate "McSPI driver for OMAP24xx/OMAP34xx"
	depends on ARCH_OMAP24XX || ARCH_OMAP34XX
	help
	  SPI master controller for OMAP24xx/OMAP34xx Multichannel SPI
	  (McSPI) modules.

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.

config SPI_PXA2XX
	tristate "PXA2xx SSP SPI master"
	depends on ARCH_PXA && EXPERIMENTAL
	select PXA_SSP
	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 ARCH_S3C2410 && EXPERIMENTAL
	select SPI_BITBANG
	help
	  SPI driver for Samsung S3C24XX series ARM SoCs

config SPI_S3C24XX_GPIO
	tristate "Samsung S3C24XX series SPI by GPIO"
	depends on ARCH_S3C2410 && EXPERIMENTAL
	select SPI_BITBANG
	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.

config SPI_SH_SCI
	tristate "SuperH SCI SPI controller"
	depends on SUPERH
	select SPI_BITBANG
	help
	  SPI driver for SuperH SCI blocks.

config SPI_TXX9
	tristate "Toshiba TXx9 SPI controller"
	depends on GENERIC_GPIO && CPU_TX49XX
	help
	  SPI driver for Toshiba TXx9 MIPS SoCs

config SPI_XILINX
	tristate "Xilinx SPI controller"
	depends on XILINX_VIRTEX && EXPERIMENTAL
	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.

#
# 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"

config SPI_SPIDEV
	tristate "User mode SPI device driver support"
	depends on EXPERIMENTAL
	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.

config SPI_TLE62X0
	tristate "Infineon TLE62X0 (for power switching)"
	depends on SYSFS
	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.

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

endif # SPI_MASTER

# (slave support would go here)

endif # SPI
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	#
79d8c7a8	8	menuconfig SPI
8ae12a0d	9	bool "SPI support"
79d8c7a8	10	depends on HAS_IOMEM
8ae12a0d DB	11	help
	12	The "Serial Peripheral Interface" is a low level synchronous
	13	protocol. Chips that support SPI can have data transfer rates
	14	up to several tens of Mbit/sec. Chips are addressed with a
	15	controller and a chipselect. Most SPI slaves don't support
	16	dynamic device discovery; some are even write-only or read-only.
	17
3cb2fccc	18	SPI is widely used by microcontrollers to talk with sensors,
8ae12a0d DB	19	eeprom and flash memory, codecs and various other controller
	20	chips, analog to digital (and d-to-a) converters, and more.
	21	MMC and SD cards can be accessed using SPI protocol; and for
	22	DataFlash cards used in MMC sockets, SPI must always be used.
	23
	24	SPI is one of a family of similar protocols using a four wire
	25	interface (select, clock, data in, data out) including Microwire
	26	(half duplex), SSP, SSI, and PSP. This driver framework should
	27	work with most such devices and controllers.
	28
79d8c7a8 AG	29	if SPI
79d8c7a8 AG	30
8ae12a0d DB	31	config SPI_DEBUG
8ae12a0d DB	32	boolean "Debug support for SPI drivers"
79d8c7a8	33	depends on DEBUG_KERNEL
8ae12a0d DB	34	help
	35	Say "yes" to enable debug messaging (like dev_dbg and pr_debug),
	36	sysfs, and debugfs support in SPI controller and protocol drivers.
	37
	38	#
	39	# MASTER side ... talking to discrete SPI slave chips including microcontrollers
	40	#
	41
	42	config SPI_MASTER
	43	# boolean "SPI Master Support"
	44	boolean
	45	default SPI
	46	help
	47	If your system has an master-capable SPI controller (which
	48	provides the clock and chipselect), you can enable that
	49	controller and the protocol drivers for the SPI slave chips
	50	that are connected.
	51
6291fe2a RD	52	if SPI_MASTER
6291fe2a RD	53
8ae12a0d	54	comment "SPI Master Controller Drivers"
8ae12a0d	55
754ce4f2 HS	56	config SPI_ATMEL
754ce4f2 HS	57	tristate "Atmel SPI Controller"
6291fe2a	58	depends on (ARCH_AT91 \|\| AVR32)
754ce4f2 HS	59	help
	60	This selects a driver for the Atmel SPI Controller, present on
	61	many AT32 (AVR32) and AT91 (ARM) chips.
	62
a5f6abd4 WB	63	config SPI_BFIN
a5f6abd4 WB	64	tristate "SPI controller driver for ADI Blackfin5xx"
6291fe2a	65	depends on BLACKFIN
a5f6abd4 WB	66	help
	67	This is the SPI controller master driver for Blackfin 5xx processor.
	68
63bd2359 JN	69	config SPI_AU1550
63bd2359 JN	70	tristate "Au1550/Au12x0 SPI Controller"
6291fe2a	71	depends on (SOC_AU1550 \|\| SOC_AU1200) && EXPERIMENTAL
63bd2359 JN	72	select SPI_BITBANG
	73	help
	74	If you say yes to this option, support will be included for the
	75	Au1550 SPI controller (may also work with Au1200,Au1210,Au1250).
	76
	77	This driver can also be built as a module. If so, the module
	78	will be called au1550_spi.
	79
9904f22a	80	config SPI_BITBANG
d29389de	81	tristate "Utilities for Bitbanging SPI masters"
9904f22a DB	82	help
	83	With a few GPIO pins, your system can bitbang the SPI protocol.
	84	Select this to get SPI support through I/O pins (GPIO, parallel
	85	port, etc). Or, some systems' SPI master controller drivers use
	86	this code to manage the per-word or per-transfer accesses to the
	87	hardware shift registers.
	88
	89	This is library code, and is automatically selected by drivers that
	90	need it. You only need to select this explicitly to support driver
	91	modules that aren't part of this kernel tree.
8ae12a0d	92
7111763d DB	93	config SPI_BUTTERFLY
7111763d DB	94	tristate "Parallel port adapter for AVR Butterfly (DEVELOPMENT)"
6291fe2a	95	depends on PARPORT
7111763d DB	96	select SPI_BITBANG
	97	help
	98	This uses a custom parallel port cable to connect to an AVR
	99	Butterfly <http://www.atmel.com/products/avr/butterfly>, an
	100	inexpensive battery powered microcontroller evaluation board.
	101	This same cable can be used to flash new firmware.
	102
d29389de DB	103	config SPI_GPIO
	104	tristate "GPIO-based bitbanging SPI Master"
	105	depends on GENERIC_GPIO
	106	select SPI_BITBANG
	107	help
	108	This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
	109	interface to manage MOSI, MISO, SCK, and chipselect signals. SPI
	110	slaves connected to a bus using this driver are configured as usual,
	111	except that the spi_board_info.controller_data holds the GPIO number
	112	for the chipselect used by this controller driver.
	113
	114	Note that this driver often won't achieve even 1 Mbit/sec speeds,
	115	making it unusually slow for SPI. If your platform can inline
	116	GPIO operations, you should be able to leverage that for better
	117	speed with a custom version of this driver; see the source code.
	118
69c202af AP	119	config SPI_IMX
69c202af AP	120	tristate "Freescale iMX SPI controller"
6291fe2a	121	depends on ARCH_IMX && EXPERIMENTAL
69c202af AP	122	help
	123	This enables using the Freescale iMX SPI controller in master
	124	mode.
	125
78961a57 KB	126	config SPI_LM70_LLP
78961a57 KB	127	tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
6291fe2a	128	depends on PARPORT && EXPERIMENTAL
78961a57 KB	129	select SPI_BITBANG
	130	help
	131	This driver supports the NS LM70 LLP Evaluation Board,
	132	which interfaces to an LM70 temperature sensor using
	133	a parallel port.
	134
00b8fd23 DC	135	config SPI_MPC52xx_PSC
00b8fd23 DC	136	tristate "Freescale MPC52xx PSC SPI controller"
6291fe2a	137	depends on PPC_MPC52xx && EXPERIMENTAL
00b8fd23 DC	138	help
	139	This enables using the Freescale MPC52xx Programmable Serial
	140	Controller in master SPI mode.
	141
ccf06998	142	config SPI_MPC83xx
328329a7	143	tristate "Freescale MPC83xx/QUICC Engine SPI controller"
6291fe2a	144	depends on (PPC_83xx \|\| QUICC_ENGINE) && EXPERIMENTAL
ccf06998	145	help
328329a7 AV	146	This enables using the Freescale MPC83xx and QUICC Engine SPI
328329a7 AV	147	controllers in master mode.
ccf06998 KG	148
ccf06998 KG	149	Note, this driver uniquely supports the SPI controller on the MPC83xx
328329a7 AV	150	family of PowerPC processors, plus processors with QUICC Engine
	151	technology. This driver uses a simple set of shift registers for data
	152	(opposed to the CPM based descriptor model).
ccf06998	153
fdb3c18d DB	154	config SPI_OMAP_UWIRE
fdb3c18d DB	155	tristate "OMAP1 MicroWire"
6291fe2a	156	depends on ARCH_OMAP1
fdb3c18d DB	157	select SPI_BITBANG
	158	help
	159	This hooks up to the MicroWire controller on OMAP1 chips.
	160
ccdc7bf9	161	config SPI_OMAP24XX
ccc7baed	162	tristate "McSPI driver for OMAP24xx/OMAP34xx"
6291fe2a	163	depends on ARCH_OMAP24XX \|\| ARCH_OMAP34XX
ccdc7bf9	164	help
ccc7baed	165	SPI master controller for OMAP24xx/OMAP34xx Multichannel SPI
ccdc7bf9	166	(McSPI) modules.
69c202af	167
60cadec9 SA	168	config SPI_ORION
	169	tristate "Orion SPI master (EXPERIMENTAL)"
	170	depends on PLAT_ORION && EXPERIMENTAL
	171	help
	172	This enables using the SPI master controller on the Orion chips.
	173
e0c9905e SS	174	config SPI_PXA2XX
e0c9905e SS	175	tristate "PXA2xx SSP SPI master"
6291fe2a	176	depends on ARCH_PXA && EXPERIMENTAL
2f1a74e5	177	select PXA_SSP
e0c9905e SS	178	help
	179	This enables using a PXA2xx SSP port as a SPI master controller.
	180	The driver can be configured to use any SSP port and additional
	181	documentation can be found a Documentation/spi/pxa2xx.
	182
85abfaa7 DB	183	config SPI_S3C24XX
85abfaa7 DB	184	tristate "Samsung S3C24XX series SPI"
6291fe2a	185	depends on ARCH_S3C2410 && EXPERIMENTAL
da0abc27	186	select SPI_BITBANG
85abfaa7 DB	187	help
	188	SPI driver for Samsung S3C24XX series ARM SoCs
	189
1fc7547d BD	190	config SPI_S3C24XX_GPIO
1fc7547d BD	191	tristate "Samsung S3C24XX series SPI by GPIO"
6291fe2a	192	depends on ARCH_S3C2410 && EXPERIMENTAL
da0abc27	193	select SPI_BITBANG
1fc7547d BD	194	help
	195	SPI driver for Samsung S3C24XX series ARM SoCs using
	196	GPIO lines to provide the SPI bus. This can be used where
	197	the inbuilt hardware cannot provide the transfer mode, or
	198	where the board is using non hardware connected pins.
ae918c02	199
37e46640 MD	200	config SPI_SH_SCI
37e46640 MD	201	tristate "SuperH SCI SPI controller"
6291fe2a	202	depends on SUPERH
37e46640 MD	203	select SPI_BITBANG
	204	help
	205	SPI driver for SuperH SCI blocks.
	206
f2cac67d AN	207	config SPI_TXX9
f2cac67d AN	208	tristate "Toshiba TXx9 SPI controller"
6291fe2a	209	depends on GENERIC_GPIO && CPU_TX49XX
f2cac67d AN	210	help
	211	SPI driver for Toshiba TXx9 MIPS SoCs
	212
ae918c02 AK	213	config SPI_XILINX
ae918c02 AK	214	tristate "Xilinx SPI controller"
6291fe2a	215	depends on XILINX_VIRTEX && EXPERIMENTAL
ae918c02 AK	216	select SPI_BITBANG
	217	help
	218	This exposes the SPI controller IP from the Xilinx EDK.
	219
	220	See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
	221	Product Specification document (DS464) for hardware details.
	222
8ae12a0d DB	223	#
	224	# Add new SPI master controllers in alphabetical order above this line
	225	#
	226
8ae12a0d DB	227	#
	228	# There are lots of SPI device types, with sensors and memory
	229	# being probably the most widely used ones.
	230	#
	231	comment "SPI Protocol Masters"
8ae12a0d	232
814a8d50 AP	233	config SPI_SPIDEV
814a8d50 AP	234	tristate "User mode SPI device driver support"
6291fe2a	235	depends on EXPERIMENTAL
814a8d50 AP	236	help
	237	This supports user mode SPI protocol drivers.
	238
	239	Note that this application programming interface is EXPERIMENTAL
	240	and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
	241
447aef1a BD	242	config SPI_TLE62X0
447aef1a BD	243	tristate "Infineon TLE62X0 (for power switching)"
6291fe2a	244	depends on SYSFS
447aef1a BD	245	help
	246	SPI driver for Infineon TLE62X0 series line driver chips,
	247	such as the TLE6220, TLE6230 and TLE6240. This provides a
	248	sysfs interface, with each line presented as a kind of GPIO
	249	exposing both switch control and diagnostic feedback.
	250
8ae12a0d DB	251	#
	252	# Add new SPI protocol masters in alphabetical order above this line
	253	#
	254
6291fe2a RD	255	endif # SPI_MASTER
6291fe2a RD	256
8ae12a0d DB	257	# (slave support would go here)
8ae12a0d DB	258
79d8c7a8	259	endif # SPI