Merge git://git.kernel.org/pub/scm/linux/kernel/git/jejb/scsi-misc-2.6
[deliverable/linux.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 80config 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
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
34b8c661
SK
103config SPI_COLDFIRE_QSPI
104 tristate "Freescale Coldfire QSPI controller"
105 depends on (M520x || M523x || M5249 || M527x || M528x || M532x)
106 help
107 This enables support for the Coldfire QSPI controller in master
108 mode.
109
110 This driver can also be built as a module. If so, the module
111 will be called coldfire_qspi.
112
358934a6
SP
113config SPI_DAVINCI
114 tristate "SPI controller driver for DaVinci/DA8xx SoC's"
115 depends on SPI_MASTER && ARCH_DAVINCI
116 select SPI_BITBANG
117 help
118 SPI master controller for DaVinci and DA8xx SPI modules.
119
011f23a3
MW
120config SPI_EP93XX
121 tristate "Cirrus Logic EP93xx SPI controller"
122 depends on ARCH_EP93XX
123 help
124 This enables using the Cirrus EP93xx SPI controller in master
125 mode.
126
127 To compile this driver as a module, choose M here. The module will be
128 called ep93xx_spi.
129
d29389de
DB
130config SPI_GPIO
131 tristate "GPIO-based bitbanging SPI Master"
132 depends on GENERIC_GPIO
133 select SPI_BITBANG
134 help
135 This simple GPIO bitbanging SPI master uses the arch-neutral GPIO
136 interface to manage MOSI, MISO, SCK, and chipselect signals. SPI
137 slaves connected to a bus using this driver are configured as usual,
138 except that the spi_board_info.controller_data holds the GPIO number
139 for the chipselect used by this controller driver.
140
141 Note that this driver often won't achieve even 1 Mbit/sec speeds,
142 making it unusually slow for SPI. If your platform can inline
143 GPIO operations, you should be able to leverage that for better
144 speed with a custom version of this driver; see the source code.
145
b5f3294f
SH
146config SPI_IMX
147 tristate "Freescale i.MX SPI controllers"
148 depends on ARCH_MXC
149 select SPI_BITBANG
150 help
151 This enables using the Freescale i.MX SPI controllers in master
152 mode.
153
78961a57
KB
154config SPI_LM70_LLP
155 tristate "Parallel port adapter for LM70 eval board (DEVELOPMENT)"
6291fe2a 156 depends on PARPORT && EXPERIMENTAL
78961a57
KB
157 select SPI_BITBANG
158 help
159 This driver supports the NS LM70 LLP Evaluation Board,
160 which interfaces to an LM70 temperature sensor using
161 a parallel port.
162
42bbb709
GL
163config SPI_MPC52xx
164 tristate "Freescale MPC52xx SPI (non-PSC) controller support"
165 depends on PPC_MPC52xx && SPI
166 select SPI_MASTER_OF
167 help
168 This drivers supports the MPC52xx SPI controller in master SPI
169 mode.
170
00b8fd23
DC
171config SPI_MPC52xx_PSC
172 tristate "Freescale MPC52xx PSC SPI controller"
6291fe2a 173 depends on PPC_MPC52xx && EXPERIMENTAL
00b8fd23
DC
174 help
175 This enables using the Freescale MPC52xx Programmable Serial
176 Controller in master SPI mode.
177
6e27388f
AG
178config SPI_MPC512x_PSC
179 tristate "Freescale MPC512x PSC SPI controller"
180 depends on SPI_MASTER && PPC_MPC512x
181 help
182 This enables using the Freescale MPC5121 Programmable Serial
183 Controller in SPI master mode.
184
575c5807 185config SPI_MPC8xxx
9e04b333
AV
186 tristate "Freescale MPC8xxx SPI controller"
187 depends on FSL_SOC
ccf06998 188 help
9e04b333
AV
189 This enables using the Freescale MPC8xxx SPI controllers in master
190 mode.
ccf06998 191
fdb3c18d
DB
192config SPI_OMAP_UWIRE
193 tristate "OMAP1 MicroWire"
6291fe2a 194 depends on ARCH_OMAP1
fdb3c18d
DB
195 select SPI_BITBANG
196 help
197 This hooks up to the MicroWire controller on OMAP1 chips.
198
ccdc7bf9 199config SPI_OMAP24XX
8ebeb545
SR
200 tristate "McSPI driver for OMAP"
201 depends on ARCH_OMAP2PLUS
ccdc7bf9 202 help
8ebeb545 203 SPI master controller for OMAP24XX and later Multichannel SPI
ccdc7bf9 204 (McSPI) modules.
69c202af 205
35c9049b
CM
206config SPI_OMAP_100K
207 tristate "OMAP SPI 100K"
208 depends on SPI_MASTER && (ARCH_OMAP850 || ARCH_OMAP730)
209 help
210 OMAP SPI 100K master controller for omap7xx boards.
211
60cadec9
SA
212config SPI_ORION
213 tristate "Orion SPI master (EXPERIMENTAL)"
214 depends on PLAT_ORION && EXPERIMENTAL
215 help
216 This enables using the SPI master controller on the Orion chips.
217
b43d65f7
LW
218config SPI_PL022
219 tristate "ARM AMBA PL022 SSP controller (EXPERIMENTAL)"
220 depends on ARM_AMBA && EXPERIMENTAL
221 default y if MACH_U300
f33b29ee 222 default y if ARCH_REALVIEW
223 default y if INTEGRATOR_IMPD1
224 default y if ARCH_VERSATILE
b43d65f7
LW
225 help
226 This selects the ARM(R) AMBA(R) PrimeCell PL022 SSP
227 controller. If you have an embedded system with an AMBA(R)
228 bus and a PL022 controller, say Y or M here.
229
44dab88e
SF
230config SPI_PPC4xx
231 tristate "PPC4xx SPI Controller"
232 depends on PPC32 && 4xx && SPI_MASTER
233 select SPI_BITBANG
234 help
235 This selects a driver for the PPC4xx SPI Controller.
236
e0c9905e
SS
237config SPI_PXA2XX
238 tristate "PXA2xx SSP SPI master"
6291fe2a 239 depends on ARCH_PXA && EXPERIMENTAL
2f1a74e5 240 select PXA_SSP
e0c9905e
SS
241 help
242 This enables using a PXA2xx SSP port as a SPI master controller.
243 The driver can be configured to use any SSP port and additional
244 documentation can be found a Documentation/spi/pxa2xx.
245
85abfaa7
DB
246config SPI_S3C24XX
247 tristate "Samsung S3C24XX series SPI"
6291fe2a 248 depends on ARCH_S3C2410 && EXPERIMENTAL
da0abc27 249 select SPI_BITBANG
85abfaa7
DB
250 help
251 SPI driver for Samsung S3C24XX series ARM SoCs
252
bec0806c
BD
253config SPI_S3C24XX_FIQ
254 bool "S3C24XX driver with FIQ pseudo-DMA"
255 depends on SPI_S3C24XX
256 select FIQ
257 help
258 Enable FIQ support for the S3C24XX SPI driver to provide pseudo
259 DMA by using the fast-interrupt request framework, This allows
260 the driver to get DMA-like performance when there are either
261 no free DMA channels, or when doing transfers that required both
262 TX and RX data paths.
263
1fc7547d
BD
264config SPI_S3C24XX_GPIO
265 tristate "Samsung S3C24XX series SPI by GPIO"
6291fe2a 266 depends on ARCH_S3C2410 && EXPERIMENTAL
da0abc27 267 select SPI_BITBANG
1fc7547d
BD
268 help
269 SPI driver for Samsung S3C24XX series ARM SoCs using
270 GPIO lines to provide the SPI bus. This can be used where
271 the inbuilt hardware cannot provide the transfer mode, or
272 where the board is using non hardware connected pins.
ae918c02 273
230d42d4
JB
274config SPI_S3C64XX
275 tristate "Samsung S3C64XX series type SPI"
276 depends on ARCH_S3C64XX && EXPERIMENTAL
277 select S3C64XX_DMA
278 help
279 SPI driver for Samsung S3C64XX and newer SoCs.
280
8051effc
MD
281config SPI_SH_MSIOF
282 tristate "SuperH MSIOF SPI controller"
283 depends on SUPERH && HAVE_CLK
284 select SPI_BITBANG
285 help
286 SPI driver for SuperH MSIOF blocks.
287
37e46640
MD
288config SPI_SH_SCI
289 tristate "SuperH SCI SPI controller"
6291fe2a 290 depends on SUPERH
37e46640
MD
291 select SPI_BITBANG
292 help
293 SPI driver for SuperH SCI blocks.
294
0644c486 295config SPI_STMP3XXX
296 tristate "Freescale STMP37xx/378x SPI/SSP controller"
297 depends on ARCH_STMP3XXX && SPI_MASTER
298 help
299 SPI driver for Freescale STMP37xx/378x SoC SSP interface
300
f2cac67d
AN
301config SPI_TXX9
302 tristate "Toshiba TXx9 SPI controller"
6291fe2a 303 depends on GENERIC_GPIO && CPU_TX49XX
f2cac67d
AN
304 help
305 SPI driver for Toshiba TXx9 MIPS SoCs
306
ae918c02 307config SPI_XILINX
c9da2e12 308 tristate "Xilinx SPI controller common module"
86fc5935 309 depends on HAS_IOMEM && EXPERIMENTAL
ae918c02 310 select SPI_BITBANG
d5af91a1 311 select SPI_XILINX_OF if (XILINX_VIRTEX || MICROBLAZE)
ae918c02
AK
312 help
313 This exposes the SPI controller IP from the Xilinx EDK.
314
315 See the "OPB Serial Peripheral Interface (SPI) (v1.00e)"
316 Product Specification document (DS464) for hardware details.
317
c9da2e12
RR
318 Or for the DS570, see "XPS Serial Peripheral Interface (SPI) (v2.00b)"
319
d5af91a1
RR
320config SPI_XILINX_OF
321 tristate "Xilinx SPI controller OF device"
322 depends on SPI_XILINX && (XILINX_VIRTEX || MICROBLAZE)
323 help
324 This is the OF driver for the SPI controller IP from the Xilinx EDK.
325
77166934
RR
326config SPI_XILINX_PLTFM
327 tristate "Xilinx SPI controller platform device"
328 depends on SPI_XILINX
329 help
330 This is the platform driver for the SPI controller IP
331 from the Xilinx EDK.
332
30eaed05
WZ
333config SPI_NUC900
334 tristate "Nuvoton NUC900 series SPI"
335 depends on ARCH_W90X900 && EXPERIMENTAL
336 select SPI_BITBANG
337 help
338 SPI driver for Nuvoton NUC900 series ARM SoCs
339
8ae12a0d
DB
340#
341# Add new SPI master controllers in alphabetical order above this line
342#
343
e24c7452 344config SPI_DESIGNWARE
8ca8d15a 345 tristate "DesignWare SPI controller core support"
e24c7452
FT
346 depends on SPI_MASTER
347 help
348 general driver for SPI controller core from DesignWare
349
350config SPI_DW_PCI
351 tristate "PCI interface driver for DW SPI core"
352 depends on SPI_DESIGNWARE && PCI
353
f7b6fd6d
JHD
354config SPI_DW_MMIO
355 tristate "Memory-mapped io interface driver for DW SPI core"
212b3c8b 356 depends on SPI_DESIGNWARE && HAVE_CLK
f7b6fd6d 357
8ae12a0d
DB
358#
359# There are lots of SPI device types, with sensors and memory
360# being probably the most widely used ones.
361#
362comment "SPI Protocol Masters"
8ae12a0d 363
814a8d50
AP
364config SPI_SPIDEV
365 tristate "User mode SPI device driver support"
6291fe2a 366 depends on EXPERIMENTAL
814a8d50
AP
367 help
368 This supports user mode SPI protocol drivers.
369
370 Note that this application programming interface is EXPERIMENTAL
371 and hence SUBJECT TO CHANGE WITHOUT NOTICE while it stabilizes.
372
447aef1a
BD
373config SPI_TLE62X0
374 tristate "Infineon TLE62X0 (for power switching)"
6291fe2a 375 depends on SYSFS
447aef1a
BD
376 help
377 SPI driver for Infineon TLE62X0 series line driver chips,
378 such as the TLE6220, TLE6230 and TLE6240. This provides a
379 sysfs interface, with each line presented as a kind of GPIO
380 exposing both switch control and diagnostic feedback.
381
8ae12a0d
DB
382#
383# Add new SPI protocol masters in alphabetical order above this line
384#
385
6291fe2a
RD
386endif # SPI_MASTER
387
8ae12a0d
DB
388# (slave support would go here)
389
79d8c7a8 390endif # SPI
This page took 0.509676 seconds and 5 git commands to generate.