]> bbs.cooldavid.org Git - net-next-2.6.git/blame - drivers/spi/Kconfig
block/cciss.c: remove pointless curr_queue calculation
[net-next-2.6.git] / drivers / spi / Kconfig
CommitLineData
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 8menuconfig 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
29if SPI
30
8ae12a0d
DB
31config SPI_DEBUG
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
42config 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
52if SPI_MASTER
53
8ae12a0d 54comment "SPI Master Controller Drivers"
8ae12a0d 55
754ce4f2
HS
56config SPI_ATMEL
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
63config SPI_BFIN
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
69config SPI_AU1550
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
DB
80config SPI_BITBANG
81 tristate "Bitbanging SPI master"
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
93config SPI_BUTTERFLY
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
69c202af
AP
103config SPI_IMX
104 tristate "Freescale iMX SPI controller"
6291fe2a 105 depends on ARCH_IMX && EXPERIMENTAL
69c202af
AP
106 help
107 This enables using the Freescale iMX SPI controller in master
108 mode.
109
78961a57
KB
110config SPI_LM70_LLP
111 tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
6291fe2a 112 depends on PARPORT && EXPERIMENTAL
78961a57
KB
113 select SPI_BITBANG
114 help
115 This driver supports the NS LM70 LLP Evaluation Board,
116 which interfaces to an LM70 temperature sensor using
117 a parallel port.
118
00b8fd23
DC
119config SPI_MPC52xx_PSC
120 tristate "Freescale MPC52xx PSC SPI controller"
6291fe2a 121 depends on PPC_MPC52xx && EXPERIMENTAL
00b8fd23
DC
122 help
123 This enables using the Freescale MPC52xx Programmable Serial
124 Controller in master SPI mode.
125
ccf06998 126config SPI_MPC83xx
328329a7 127 tristate "Freescale MPC83xx/QUICC Engine SPI controller"
6291fe2a 128 depends on (PPC_83xx || QUICC_ENGINE) && EXPERIMENTAL
ccf06998 129 help
328329a7
AV
130 This enables using the Freescale MPC83xx and QUICC Engine SPI
131 controllers in master mode.
ccf06998
KG
132
133 Note, this driver uniquely supports the SPI controller on the MPC83xx
328329a7
AV
134 family of PowerPC processors, plus processors with QUICC Engine
135 technology. This driver uses a simple set of shift registers for data
136 (opposed to the CPM based descriptor model).
ccf06998 137
fdb3c18d
DB
138config SPI_OMAP_UWIRE
139 tristate "OMAP1 MicroWire"
6291fe2a 140 depends on ARCH_OMAP1
fdb3c18d
DB
141 select SPI_BITBANG
142 help
143 This hooks up to the MicroWire controller on OMAP1 chips.
144
ccdc7bf9 145config SPI_OMAP24XX
ccc7baed 146 tristate "McSPI driver for OMAP24xx/OMAP34xx"
6291fe2a 147 depends on ARCH_OMAP24XX || ARCH_OMAP34XX
ccdc7bf9 148 help
ccc7baed 149 SPI master controller for OMAP24xx/OMAP34xx Multichannel SPI
ccdc7bf9 150 (McSPI) modules.
69c202af 151
e0c9905e
SS
152config SPI_PXA2XX
153 tristate "PXA2xx SSP SPI master"
6291fe2a 154 depends on ARCH_PXA && EXPERIMENTAL
2f1a74e5 155 select PXA_SSP
e0c9905e
SS
156 help
157 This enables using a PXA2xx SSP port as a SPI master controller.
158 The driver can be configured to use any SSP port and additional
159 documentation can be found a Documentation/spi/pxa2xx.
160
85abfaa7
DB
161config SPI_S3C24XX
162 tristate "Samsung S3C24XX series SPI"
6291fe2a 163 depends on ARCH_S3C2410 && EXPERIMENTAL
da0abc27 164 select SPI_BITBANG
85abfaa7
DB
165 help
166 SPI driver for Samsung S3C24XX series ARM SoCs
167
1fc7547d
BD
168config SPI_S3C24XX_GPIO
169 tristate "Samsung S3C24XX series SPI by GPIO"
6291fe2a 170 depends on ARCH_S3C2410 && EXPERIMENTAL
da0abc27 171 select SPI_BITBANG
1fc7547d
BD
172 help
173 SPI driver for Samsung S3C24XX series ARM SoCs using
174 GPIO lines to provide the SPI bus. This can be used where
175 the inbuilt hardware cannot provide the transfer mode, or
176 where the board is using non hardware connected pins.
ae918c02 177
37e46640
MD
178config SPI_SH_SCI
179 tristate "SuperH SCI SPI controller"
6291fe2a 180 depends on SUPERH
37e46640
MD
181 select SPI_BITBANG
182 help
183 SPI driver for SuperH SCI blocks.
184
f2cac67d
AN
185config SPI_TXX9
186 tristate "Toshiba TXx9 SPI controller"
6291fe2a 187 depends on GENERIC_GPIO && CPU_TX49XX
f2cac67d
AN
188 help
189 SPI driver for Toshiba TXx9 MIPS SoCs
190
ae918c02
AK
191config SPI_XILINX
192 tristate "Xilinx SPI controller"
6291fe2a 193 depends on XILINX_VIRTEX && EXPERIMENTAL
ae918c02
AK
194 select SPI_BITBANG
195 help
196 This exposes the SPI controller IP from the Xilinx EDK.
197
198 See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
199 Product Specification document (DS464) for hardware details.
200
8ae12a0d
DB
201#
202# Add new SPI master controllers in alphabetical order above this line
203#
204
8ae12a0d
DB
205#
206# There are lots of SPI device types, with sensors and memory
207# being probably the most widely used ones.
208#
209comment "SPI Protocol Masters"
8ae12a0d 210
b587b13a
DB
211config SPI_AT25
212 tristate "SPI EEPROMs from most vendors"
6291fe2a 213 depends on SYSFS
b587b13a
DB
214 help
215 Enable this driver to get read/write support to most SPI EEPROMs,
216 after you configure the board init code to know about each eeprom
217 on your target board.
218
219 This driver can also be built as a module. If so, the module
220 will be called at25.
8ae12a0d 221
814a8d50
AP
222config SPI_SPIDEV
223 tristate "User mode SPI device driver support"
6291fe2a 224 depends on EXPERIMENTAL
814a8d50
AP
225 help
226 This supports user mode SPI protocol drivers.
227
228 Note that this application programming interface is EXPERIMENTAL
229 and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
230
447aef1a
BD
231config SPI_TLE62X0
232 tristate "Infineon TLE62X0 (for power switching)"
6291fe2a 233 depends on SYSFS
447aef1a
BD
234 help
235 SPI driver for Infineon TLE62X0 series line driver chips,
236 such as the TLE6220, TLE6230 and TLE6240. This provides a
237 sysfs interface, with each line presented as a kind of GPIO
238 exposing both switch control and diagnostic feedback.
239
8ae12a0d
DB
240#
241# Add new SPI protocol masters in alphabetical order above this line
242#
243
6291fe2a
RD
244endif # SPI_MASTER
245
8ae12a0d
DB
246# (slave support would go here)
247
79d8c7a8 248endif # SPI