xref: /openbmc/linux/drivers/mmc/host/Kconfig (revision 171f1bc7)
1#
2# MMC/SD host controller drivers
3#
4
5comment "MMC/SD/SDIO Host Controller Drivers"
6
7config MMC_ARMMMCI
8	tristate "ARM AMBA Multimedia Card Interface support"
9	depends on ARM_AMBA
10	help
11	  This selects the ARM(R) AMBA(R) PrimeCell Multimedia Card
12	  Interface (PL180 and PL181) support.  If you have an ARM(R)
13	  platform with a Multimedia Card slot, say Y or M here.
14
15	  If unsure, say N.
16
17config MMC_PXA
18	tristate "Intel PXA25x/26x/27x Multimedia Card Interface support"
19	depends on ARCH_PXA
20	help
21	  This selects the Intel(R) PXA(R) Multimedia card Interface.
22	  If you have a PXA(R) platform with a Multimedia Card slot,
23	  say Y or M here.
24
25	  If unsure, say N.
26
27config MMC_SDHCI
28	tristate "Secure Digital Host Controller Interface support"
29	depends on HAS_DMA
30	help
31	  This selects the generic Secure Digital Host Controller Interface.
32	  It is used by manufacturers such as Texas Instruments(R), Ricoh(R)
33	  and Toshiba(R). Most controllers found in laptops are of this type.
34
35	  If you have a controller with this interface, say Y or M here. You
36	  also need to enable an appropriate bus interface.
37
38	  If unsure, say N.
39
40config MMC_SDHCI_IO_ACCESSORS
41	bool
42	depends on MMC_SDHCI
43	help
44	  This is silent Kconfig symbol that is selected by the drivers that
45	  need to overwrite SDHCI IO memory accessors.
46
47config MMC_SDHCI_BIG_ENDIAN_32BIT_BYTE_SWAPPER
48	bool
49	select MMC_SDHCI_IO_ACCESSORS
50	help
51	  This option is selected by drivers running on big endian hosts
52	  and performing I/O to a SDHCI controller through a bus that
53	  implements a hardware byte swapper using a 32-bit datum.
54	  This endian mapping mode is called "data invariance" and
55	  has the effect of scrambling the addresses and formats of data
56	  accessed in sizes other than the datum size.
57
58	  This is the case for the Freescale eSDHC and Nintendo Wii SDHCI.
59
60config MMC_SDHCI_PCI
61	tristate "SDHCI support on PCI bus"
62	depends on MMC_SDHCI && PCI
63	help
64	  This selects the PCI Secure Digital Host Controller Interface.
65	  Most controllers found today are PCI devices.
66
67	  If you have a controller with this interface, say Y or M here.
68
69	  If unsure, say N.
70
71config MMC_RICOH_MMC
72	bool "Ricoh MMC Controller Disabler  (EXPERIMENTAL)"
73	depends on MMC_SDHCI_PCI
74	help
75	  This adds a pci quirk to disable Ricoh MMC Controller. This
76	  proprietary controller is unnecessary because the SDHCI driver
77	  supports MMC cards on the SD controller, but if it is not
78	  disabled, it will steal the MMC cards away - rendering them
79	  useless. It is safe to select this even if you don't
80	  have a Ricoh based card reader.
81
82	  If unsure, say Y.
83
84config MMC_SDHCI_PLTFM
85	tristate "SDHCI platform and OF driver helper"
86	depends on MMC_SDHCI
87	help
88	  This selects the common helper functions support for Secure Digital
89	  Host Controller Interface based platform and OF drivers.
90
91	  If you have a controller with this interface, say Y or M here.
92
93	  If unsure, say N.
94
95config MMC_SDHCI_OF_ESDHC
96	tristate "SDHCI OF support for the Freescale eSDHC controller"
97	depends on MMC_SDHCI_PLTFM
98	depends on PPC_OF
99	select MMC_SDHCI_BIG_ENDIAN_32BIT_BYTE_SWAPPER
100	help
101	  This selects the Freescale eSDHC controller support.
102
103	  If you have a controller with this interface, say Y or M here.
104
105	  If unsure, say N.
106
107config MMC_SDHCI_OF_HLWD
108	tristate "SDHCI OF support for the Nintendo Wii SDHCI controllers"
109	depends on MMC_SDHCI_PLTFM
110	depends on PPC_OF
111	select MMC_SDHCI_BIG_ENDIAN_32BIT_BYTE_SWAPPER
112	help
113	  This selects the Secure Digital Host Controller Interface (SDHCI)
114	  found in the "Hollywood" chipset of the Nintendo Wii video game
115	  console.
116
117	  If you have a controller with this interface, say Y or M here.
118
119	  If unsure, say N.
120
121config MMC_SDHCI_CNS3XXX
122	tristate "SDHCI support on the Cavium Networks CNS3xxx SoC"
123	depends on ARCH_CNS3XXX
124	depends on MMC_SDHCI_PLTFM
125	help
126	  This selects the SDHCI support for CNS3xxx System-on-Chip devices.
127
128	  If you have a controller with this interface, say Y or M here.
129
130	  If unsure, say N.
131
132config MMC_SDHCI_ESDHC_IMX
133	tristate "SDHCI support for the Freescale eSDHC/uSDHC i.MX controller"
134	depends on ARCH_MXC
135	depends on MMC_SDHCI_PLTFM
136	select MMC_SDHCI_IO_ACCESSORS
137	help
138	  This selects the Freescale eSDHC/uSDHC controller support
139	  found on i.MX25, i.MX35 i.MX5x and i.MX6x.
140
141	  If you have a controller with this interface, say Y or M here.
142
143	  If unsure, say N.
144
145config MMC_SDHCI_DOVE
146	tristate "SDHCI support on Marvell's Dove SoC"
147	depends on ARCH_DOVE
148	depends on MMC_SDHCI_PLTFM
149	select MMC_SDHCI_IO_ACCESSORS
150	help
151	  This selects the Secure Digital Host Controller Interface in
152	  Marvell's Dove SoC.
153
154	  If you have a controller with this interface, say Y or M here.
155
156	  If unsure, say N.
157
158config MMC_SDHCI_TEGRA
159	tristate "SDHCI platform support for the Tegra SD/MMC Controller"
160	depends on ARCH_TEGRA
161	depends on MMC_SDHCI_PLTFM
162	select MMC_SDHCI_IO_ACCESSORS
163	help
164	  This selects the Tegra SD/MMC controller. If you have a Tegra
165	  platform with SD or MMC devices, say Y or M here.
166
167	  If unsure, say N.
168
169config MMC_SDHCI_S3C
170	tristate "SDHCI support on Samsung S3C SoC"
171	depends on MMC_SDHCI && PLAT_SAMSUNG
172	help
173	  This selects the Secure Digital Host Controller Interface (SDHCI)
174	  often referrered to as the HSMMC block in some of the Samsung S3C
175	  range of SoC.
176
177	  Note, due to the problems with DMA, the DMA support is only
178	  available with CONFIG_EXPERIMENTAL is selected.
179
180	  If you have a controller with this interface, say Y or M here.
181
182	  If unsure, say N.
183
184config MMC_SDHCI_PXAV3
185	tristate "Marvell MMP2 SD Host Controller support (PXAV3)"
186	depends on CLKDEV_LOOKUP
187	select MMC_SDHCI
188	select MMC_SDHCI_PLTFM
189	default CPU_MMP2
190	help
191	  This selects the Marvell(R) PXAV3 SD Host Controller.
192	  If you have a MMP2 platform with SD Host Controller
193	  and a card slot, say Y or M here.
194
195	  If unsure, say N.
196
197config MMC_SDHCI_PXAV2
198	tristate "Marvell PXA9XX SD Host Controller support (PXAV2)"
199	depends on CLKDEV_LOOKUP
200	select MMC_SDHCI
201	select MMC_SDHCI_PLTFM
202	default CPU_PXA910
203	help
204	  This selects the Marvell(R) PXAV2 SD Host Controller.
205	  If you have a PXA9XX platform with SD Host Controller
206	  and a card slot, say Y or M here.
207
208	  If unsure, say N.
209
210config MMC_SDHCI_SPEAR
211	tristate "SDHCI support on ST SPEAr platform"
212	depends on MMC_SDHCI && PLAT_SPEAR
213	help
214	  This selects the Secure Digital Host Controller Interface (SDHCI)
215	  often referrered to as the HSMMC block in some of the ST SPEAR range
216	  of SoC
217
218	  If you have a controller with this interface, say Y or M here.
219
220	  If unsure, say N.
221
222config MMC_SDHCI_S3C_DMA
223	bool "DMA support on S3C SDHCI"
224	depends on MMC_SDHCI_S3C && EXPERIMENTAL
225	help
226	  Enable DMA support on the Samsung S3C SDHCI glue. The DMA
227	  has proved to be problematic if the controller encounters
228	  certain errors, and thus should be treated with care.
229
230	  YMMV.
231
232config MMC_OMAP
233	tristate "TI OMAP Multimedia Card Interface support"
234	depends on ARCH_OMAP
235	select TPS65010 if MACH_OMAP_H2
236	help
237	  This selects the TI OMAP Multimedia card Interface.
238	  If you have an OMAP board with a Multimedia Card slot,
239	  say Y or M here.
240
241	  If unsure, say N.
242
243config MMC_OMAP_HS
244	tristate "TI OMAP High Speed Multimedia Card Interface support"
245	depends on SOC_OMAP2430 || ARCH_OMAP3 || ARCH_OMAP4
246	help
247	  This selects the TI OMAP High Speed Multimedia card Interface.
248	  If you have an OMAP2430 or OMAP3 board or OMAP4 board with a
249	  Multimedia Card slot, say Y or M here.
250
251	  If unsure, say N.
252
253config MMC_WBSD
254	tristate "Winbond W83L51xD SD/MMC Card Interface support"
255	depends on ISA_DMA_API
256	help
257	  This selects the Winbond(R) W83L51xD Secure digital and
258          Multimedia card Interface.
259	  If you have a machine with a integrated W83L518D or W83L519D
260	  SD/MMC card reader, say Y or M here.
261
262	  If unsure, say N.
263
264config MMC_AU1X
265	tristate "Alchemy AU1XX0 MMC Card Interface support"
266	depends on MIPS_ALCHEMY
267	help
268	  This selects the AMD Alchemy(R) Multimedia card interface.
269	  If you have a Alchemy platform with a MMC slot, say Y or M here.
270
271	  If unsure, say N.
272
273choice
274	prompt "Atmel SD/MMC Driver"
275	depends on AVR32 || ARCH_AT91
276	default MMC_ATMELMCI if AVR32
277	help
278	  Choose which driver to use for the Atmel MCI Silicon
279
280config MMC_AT91
281	tristate "AT91 SD/MMC Card Interface support"
282	depends on ARCH_AT91
283	help
284	  This selects the AT91 MCI controller.
285
286	  If unsure, say N.
287
288config MMC_ATMELMCI
289	tristate "Atmel Multimedia Card Interface support"
290	depends on AVR32 || ARCH_AT91
291	help
292	  This selects the Atmel Multimedia Card Interface driver. If
293	  you have an AT32 (AVR32) or AT91 platform with a Multimedia
294	  Card slot, say Y or M here.
295
296	  If unsure, say N.
297
298endchoice
299
300config MMC_ATMELMCI_DMA
301	bool "Atmel MCI DMA support"
302	depends on MMC_ATMELMCI && (AVR32 || ARCH_AT91SAM9G45) && DMA_ENGINE
303	help
304	  Say Y here to have the Atmel MCI driver use a DMA engine to
305	  do data transfers and thus increase the throughput and
306	  reduce the CPU utilization.
307
308	  If unsure, say N.
309
310config MMC_IMX
311	tristate "Motorola i.MX Multimedia Card Interface support"
312	depends on ARCH_MX1
313	help
314	  This selects the Motorola i.MX Multimedia card Interface.
315	  If you have a i.MX platform with a Multimedia Card slot,
316	  say Y or M here.
317
318	  If unsure, say N.
319
320config MMC_MSM
321	tristate "Qualcomm SDCC Controller Support"
322	depends on MMC && ARCH_MSM
323	help
324	  This provides support for the SD/MMC cell found in the
325	  MSM and QSD SOCs from Qualcomm. The controller also has
326	  support for SDIO devices.
327
328config MMC_MXC
329	tristate "Freescale i.MX21/27/31 Multimedia Card Interface support"
330	depends on ARCH_MXC
331	help
332	  This selects the Freescale i.MX21, i.MX27 and i.MX31 Multimedia card
333	  Interface. If you have a i.MX platform with a Multimedia Card slot,
334	  say Y or M here.
335
336	  If unsure, say N.
337
338config MMC_MXS
339	tristate "Freescale MXS Multimedia Card Interface support"
340	depends on ARCH_MXS && MXS_DMA
341	help
342	  This selects the Freescale SSP MMC controller found on MXS based
343	  platforms like mx23/28.
344
345	  If unsure, say N.
346
347config MMC_TIFM_SD
348	tristate "TI Flash Media MMC/SD Interface support  (EXPERIMENTAL)"
349	depends on EXPERIMENTAL && PCI
350	select TIFM_CORE
351	help
352	  Say Y here if you want to be able to access MMC/SD cards with
353	  the Texas Instruments(R) Flash Media card reader, found in many
354	  laptops.
355	  This option 'selects' (turns on, enables) 'TIFM_CORE', but you
356	  probably also need appropriate card reader host adapter, such as
357	  'Misc devices: TI Flash Media PCI74xx/PCI76xx host adapter support
358	  (TIFM_7XX1)'.
359
360          To compile this driver as a module, choose M here: the
361	  module will be called tifm_sd.
362
363config MMC_MVSDIO
364	tristate "Marvell MMC/SD/SDIO host driver"
365	depends on PLAT_ORION
366	---help---
367	  This selects the Marvell SDIO host driver.
368	  SDIO may currently be found on the Kirkwood 88F6281 and 88F6192
369	  SoC controllers.
370
371	  To compile this driver as a module, choose M here: the
372	  module will be called mvsdio.
373
374config MMC_DAVINCI
375        tristate "TI DAVINCI Multimedia Card Interface support"
376        depends on ARCH_DAVINCI
377        help
378          This selects the TI DAVINCI Multimedia card Interface.
379          If you have an DAVINCI board with a Multimedia Card slot,
380          say Y or M here.  If unsure, say N.
381
382config MMC_SPI
383	tristate "MMC/SD/SDIO over SPI"
384	depends on SPI_MASTER && !HIGHMEM && HAS_DMA
385	select CRC7
386	select CRC_ITU_T
387	help
388	  Some systems access MMC/SD/SDIO cards using a SPI controller
389	  instead of using a "native" MMC/SD/SDIO controller.  This has a
390	  disadvantage of being relatively high overhead, but a compensating
391	  advantage of working on many systems without dedicated MMC/SD/SDIO
392	  controllers.
393
394	  If unsure, or if your system has no SPI master driver, say N.
395
396config MMC_S3C
397	tristate "Samsung S3C SD/MMC Card Interface support"
398	depends on ARCH_S3C2410
399	help
400	  This selects a driver for the MCI interface found in
401          Samsung's S3C2410, S3C2412, S3C2440, S3C2442 CPUs.
402	  If you have a board based on one of those and a MMC/SD
403	  slot, say Y or M here.
404
405	  If unsure, say N.
406
407config MMC_S3C_HW_SDIO_IRQ
408       bool "Hardware support for SDIO IRQ"
409       depends on MMC_S3C
410       help
411         Enable the hardware support for SDIO interrupts instead of using
412	 the generic polling code.
413
414choice
415	prompt "Samsung S3C SD/MMC transfer code"
416	depends on MMC_S3C
417
418config MMC_S3C_PIO
419	bool "Use PIO transfers only"
420	help
421	  Use PIO to transfer data between memory and the hardware.
422
423	  PIO is slower than DMA as it requires CPU instructions to
424	  move the data. This has been the traditional default for
425	  the S3C MCI driver.
426
427config MMC_S3C_DMA
428	bool "Use DMA transfers only (EXPERIMENTAL)"
429	depends on EXPERIMENTAL
430	help
431	  Use DMA to transfer data between memory and the hardare.
432
433	  Currently, the DMA support in this driver seems to not be
434	  working properly and needs to be debugged before this
435	  option is useful.
436
437config MMC_S3C_PIODMA
438	bool "Support for both PIO and DMA (EXPERIMENTAL)"
439	help
440	  Compile both the PIO and DMA transfer routines into the
441	  driver and let the platform select at run-time which one
442	  is best.
443
444	  See notes for the DMA option.
445
446endchoice
447
448config MMC_SDRICOH_CS
449	tristate "MMC/SD driver for Ricoh Bay1Controllers (EXPERIMENTAL)"
450	depends on EXPERIMENTAL && PCI && PCMCIA
451	help
452	  Say Y here if your Notebook reports a Ricoh Bay1Controller PCMCIA
453	  card whenever you insert a MMC or SD card into the card slot.
454
455	  To compile this driver as a module, choose M here: the
456	  module will be called sdricoh_cs.
457
458config MMC_TMIO_CORE
459	tristate
460
461config MMC_TMIO
462	tristate "Toshiba Mobile IO Controller (TMIO) MMC/SD function support"
463	depends on MFD_TMIO || MFD_ASIC3
464	select MMC_TMIO_CORE
465	help
466	  This provides support for the SD/MMC cell found in TC6393XB,
467	  T7L66XB and also HTC ASIC3
468
469config MMC_SDHI
470	tristate "SH-Mobile SDHI SD/SDIO controller support"
471	depends on SUPERH || ARCH_SHMOBILE
472	select MMC_TMIO_CORE
473	help
474	  This provides support for the SDHI SD/SDIO controller found in
475	  SuperH and ARM SH-Mobile SoCs
476
477config MMC_CB710
478	tristate "ENE CB710 MMC/SD Interface support"
479	depends on PCI
480	select MISC_DEVICES
481	select CB710_CORE
482	help
483	  This option enables support for MMC/SD part of ENE CB710/720 Flash
484	  memory card reader found in some laptops (ie. some versions of
485	  HP Compaq nx9500).
486
487	  This driver can also be built as a module. If so, the module
488	  will be called cb710-mmc.
489
490config MMC_VIA_SDMMC
491	tristate "VIA SD/MMC Card Reader Driver"
492	depends on PCI
493	help
494	  This selects the VIA SD/MMC Card Reader driver, say Y or M here.
495	  VIA provides one multi-functional card reader which integrated into
496	  some motherboards manufactured by VIA. This card reader supports
497	  SD/MMC/SDHC.
498	  If you have a controller with this interface, say Y or M here.
499
500	  If unsure, say N.
501
502config SDH_BFIN
503	tristate "Blackfin Secure Digital Host support"
504	depends on (BF54x && !BF544) || (BF51x && !BF512)
505	help
506	  If you say yes here you will get support for the Blackfin on-chip
507	  Secure Digital Host interface.  This includes support for MMC and
508	  SD cards.
509
510	  To compile this driver as a module, choose M here: the
511	  module will be called bfin_sdh.
512
513	  If unsure, say N.
514
515config SDH_BFIN_MISSING_CMD_PULLUP_WORKAROUND
516	bool "Blackfin EZkit Missing SDH_CMD Pull Up Resistor Workaround"
517	depends on SDH_BFIN
518	help
519	  If you say yes here SD-Cards may work on the EZkit.
520
521config MMC_DW
522	tristate "Synopsys DesignWare Memory Card Interface"
523	depends on ARM
524	help
525	  This selects support for the Synopsys DesignWare Mobile Storage IP
526	  block, this provides host support for SD and MMC interfaces, in both
527	  PIO and external DMA modes.
528
529config MMC_DW_IDMAC
530	bool "Internal DMAC interface"
531	depends on MMC_DW
532	help
533	  This selects support for the internal DMAC block within the Synopsys
534	  Designware Mobile Storage IP block. This disables the external DMA
535	  interface.
536
537config MMC_SH_MMCIF
538	tristate "SuperH Internal MMCIF support"
539	depends on MMC_BLOCK && (SUPERH || ARCH_SHMOBILE)
540	help
541	  This selects the MMC Host Interface controller (MMCIF).
542
543	  This driver supports MMCIF in sh7724/sh7757/sh7372.
544
545config MMC_JZ4740
546	tristate "JZ4740 SD/Multimedia Card Interface support"
547	depends on MACH_JZ4740
548	help
549	  This selects support for the SD/MMC controller on Ingenic JZ4740
550	  SoCs.
551	  If you have a board based on such a SoC and with a SD/MMC slot,
552	  say Y or M here.
553
554config MMC_VUB300
555	tristate "VUB300 USB to SDIO/SD/MMC Host Controller support"
556	depends on USB
557	help
558	  This selects support for Elan Digital Systems' VUB300 chip.
559
560	  The VUB300 is a USB-SDIO Host Controller Interface chip
561	  that enables the host computer to use SDIO/SD/MMC cards
562	  via a USB 2.0 or USB 1.1 host.
563
564	  The VUB300 chip will be found in both physically separate
565	  USB to SDIO/SD/MMC adapters and embedded on some motherboards.
566
567	  The VUB300 chip supports SD and MMC memory cards in addition
568	  to single and multifunction SDIO cards.
569
570	  Some SDIO cards will need a firmware file to be loaded and
571	  sent to VUB300 chip in order to achieve better data throughput.
572	  Download these "Offload Pseudocode" from Elan Digital Systems'
573	  web-site http://www.elandigitalsystems.com/support/downloads.php
574	  and put them in /lib/firmware. Note that without these additional
575	  firmware files the VUB300 chip will still function, but not at
576	  the best obtainable data rate.
577
578	  To compile this mmc host controller driver as a module,
579	  choose M here: the module will be called vub300.
580
581	  If you have a computer with an embedded VUB300 chip
582	  or if you intend connecting a USB adapter based on a
583	  VUB300 chip say Y or M here.
584
585config MMC_USHC
586	tristate "USB SD Host Controller (USHC) support"
587	depends on USB
588	help
589	  This selects support for USB SD Host Controllers based on
590	  the Cypress Astoria chip with firmware compliant with CSR's
591	  USB SD Host Controller specification (CS-118793-SP).
592
593	  CSR boards with this device include: USB<>SDIO (M1985v2),
594	  and Ultrasira.
595
596	  Note: These controllers only support SDIO cards and do not
597	  support MMC or SD memory cards.
598