2 # MMC/SD host controller drivers
5 comment "MMC/SD/SDIO Host Controller Drivers"
8 tristate "ARM AMBA Multimedia Card Interface support"
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.
18 tristate "Intel PXA25x/26x/27x Multimedia Card Interface support"
21 This selects the Intel(R) PXA(R) Multimedia card Interface.
22 If you have a PXA(R) platform with a Multimedia Card slot,
28 tristate "Secure Digital Host Controller Interface support"
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.
35 If you have a controller with this interface, say Y or M here. You
36 also need to enable an appropriate bus interface.
40 config MMC_SDHCI_IO_ACCESSORS
44 This is silent Kconfig symbol that is selected by the drivers that
45 need to overwrite SDHCI IO memory accessors.
47 config MMC_SDHCI_BIG_ENDIAN_32BIT_BYTE_SWAPPER
49 select MMC_SDHCI_IO_ACCESSORS
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.
58 This is the case for the Freescale eSDHC and Nintendo Wii SDHCI.
61 tristate "SDHCI support on PCI bus"
62 depends on MMC_SDHCI && PCI
64 This selects the PCI Secure Digital Host Controller Interface.
65 Most controllers found today are PCI devices.
67 If you have a controller with this interface, say Y or M here.
72 bool "Ricoh MMC Controller Disabler (EXPERIMENTAL)"
73 depends on MMC_SDHCI_PCI
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.
84 config MMC_SDHCI_PLTFM
85 tristate "SDHCI platform and OF driver helper"
88 This selects the common helper functions support for Secure Digital
89 Host Controller Interface based platform and OF drivers.
91 If you have a controller with this interface, say Y or M here.
95 config MMC_SDHCI_OF_ESDHC
96 tristate "SDHCI OF support for the Freescale eSDHC controller"
97 depends on MMC_SDHCI_PLTFM
99 select MMC_SDHCI_BIG_ENDIAN_32BIT_BYTE_SWAPPER
101 This selects the Freescale eSDHC controller support.
103 If you have a controller with this interface, say Y or M here.
107 config MMC_SDHCI_OF_HLWD
108 tristate "SDHCI OF support for the Nintendo Wii SDHCI controllers"
109 depends on MMC_SDHCI_PLTFM
111 select MMC_SDHCI_BIG_ENDIAN_32BIT_BYTE_SWAPPER
113 This selects the Secure Digital Host Controller Interface (SDHCI)
114 found in the "Hollywood" chipset of the Nintendo Wii video game
117 If you have a controller with this interface, say Y or M here.
121 config MMC_SDHCI_CNS3XXX
122 tristate "SDHCI support on the Cavium Networks CNS3xxx SoC"
123 depends on ARCH_CNS3XXX
124 depends on MMC_SDHCI_PLTFM
126 This selects the SDHCI support for CNS3xxx System-on-Chip devices.
128 If you have a controller with this interface, say Y or M here.
132 config MMC_SDHCI_ESDHC_IMX
133 tristate "SDHCI platform support for the Freescale eSDHC i.MX controller"
134 depends on ARCH_MX25 || ARCH_MX35 || ARCH_MX5
135 depends on MMC_SDHCI_PLTFM
136 select MMC_SDHCI_IO_ACCESSORS
138 This selects the Freescale eSDHC controller support on the platform
139 bus, found on platforms like mx35/51.
141 If you have a controller with this interface, say Y or M here.
145 config MMC_SDHCI_DOVE
146 tristate "SDHCI support on Marvell's Dove SoC"
148 depends on MMC_SDHCI_PLTFM
149 select MMC_SDHCI_IO_ACCESSORS
151 This selects the Secure Digital Host Controller Interface in
154 If you have a controller with this interface, say Y or M here.
158 config 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
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.
170 tristate "SDHCI support on Samsung S3C SoC"
171 depends on MMC_SDHCI && PLAT_SAMSUNG
173 This selects the Secure Digital Host Controller Interface (SDHCI)
174 often referrered to as the HSMMC block in some of the Samsung S3C
177 Note, due to the problems with DMA, the DMA support is only
178 available with CONFIG_EXPERIMENTAL is selected.
180 If you have a controller with this interface, say Y or M here.
184 config MMC_SDHCI_PXAV3
185 tristate "Marvell MMP2 SD Host Controller support (PXAV3)"
186 depends on CLKDEV_LOOKUP
188 select MMC_SDHCI_PLTFM
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.
197 config MMC_SDHCI_PXAV2
198 tristate "Marvell PXA9XX SD Host Controller support (PXAV2)"
199 depends on CLKDEV_LOOKUP
201 select MMC_SDHCI_PLTFM
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.
210 config MMC_SDHCI_SPEAR
211 tristate "SDHCI support on ST SPEAr platform"
212 depends on MMC_SDHCI && PLAT_SPEAR
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
218 If you have a controller with this interface, say Y or M here.
222 config MMC_SDHCI_S3C_DMA
223 bool "DMA support on S3C SDHCI"
224 depends on MMC_SDHCI_S3C && EXPERIMENTAL
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.
233 tristate "TI OMAP Multimedia Card Interface support"
235 select TPS65010 if MACH_OMAP_H2
237 This selects the TI OMAP Multimedia card Interface.
238 If you have an OMAP board with a Multimedia Card slot,
244 tristate "TI OMAP High Speed Multimedia Card Interface support"
245 depends on SOC_OMAP2430 || ARCH_OMAP3 || ARCH_OMAP4
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.
254 tristate "Winbond W83L51xD SD/MMC Card Interface support"
255 depends on ISA_DMA_API
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.
265 tristate "Alchemy AU1XX0 MMC Card Interface support"
266 depends on SOC_AU1200
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.
274 prompt "Atmel SD/MMC Driver"
275 depends on AVR32 || ARCH_AT91
276 default MMC_ATMELMCI if AVR32
278 Choose which driver to use for the Atmel MCI Silicon
281 tristate "AT91 SD/MMC Card Interface support"
284 This selects the AT91 MCI controller.
289 tristate "Atmel Multimedia Card Interface support"
290 depends on AVR32 || ARCH_AT91
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.
300 config MMC_ATMELMCI_DMA
301 bool "Atmel MCI DMA support"
302 depends on MMC_ATMELMCI && (AVR32 || ARCH_AT91SAM9G45) && DMA_ENGINE
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.
311 tristate "Motorola i.MX Multimedia Card Interface support"
314 This selects the Motorola i.MX Multimedia card Interface.
315 If you have a i.MX platform with a Multimedia Card slot,
321 tristate "Qualcomm SDCC Controller Support"
322 depends on MMC && ARCH_MSM
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.
329 tristate "Freescale i.MX2/3 Multimedia Card Interface support"
330 depends on MACH_MX21 || MACH_MX27 || ARCH_MX31
332 This selects the Freescale i.MX2/3 Multimedia card Interface.
333 If you have a i.MX platform with a Multimedia Card slot,
339 tristate "Freescale MXS Multimedia Card Interface support"
340 depends on ARCH_MXS && MXS_DMA
342 This selects the Freescale SSP MMC controller found on MXS based
343 platforms like mx23/28.
348 tristate "TI Flash Media MMC/SD Interface support (EXPERIMENTAL)"
349 depends on EXPERIMENTAL && PCI
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
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
360 To compile this driver as a module, choose M here: the
361 module will be called tifm_sd.
364 tristate "Marvell MMC/SD/SDIO host driver"
365 depends on PLAT_ORION
367 This selects the Marvell SDIO host driver.
368 SDIO may currently be found on the Kirkwood 88F6281 and 88F6192
371 To compile this driver as a module, choose M here: the
372 module will be called mvsdio.
375 tristate "TI DAVINCI Multimedia Card Interface support"
376 depends on ARCH_DAVINCI
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.
383 tristate "MMC/SD/SDIO over SPI"
384 depends on SPI_MASTER && !HIGHMEM && HAS_DMA
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
394 If unsure, or if your system has no SPI master driver, say N.
397 tristate "Samsung S3C SD/MMC Card Interface support"
398 depends on ARCH_S3C2410
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.
407 config MMC_S3C_HW_SDIO_IRQ
408 bool "Hardware support for SDIO IRQ"
411 Enable the hardware support for SDIO interrupts instead of using
412 the generic polling code.
415 prompt "Samsung S3C SD/MMC transfer code"
419 bool "Use PIO transfers only"
421 Use PIO to transfer data between memory and the hardware.
423 PIO is slower than DMA as it requires CPU instructions to
424 move the data. This has been the traditional default for
428 bool "Use DMA transfers only (EXPERIMENTAL)"
429 depends on EXPERIMENTAL
431 Use DMA to transfer data between memory and the hardare.
433 Currently, the DMA support in this driver seems to not be
434 working properly and needs to be debugged before this
437 config MMC_S3C_PIODMA
438 bool "Support for both PIO and DMA (EXPERIMENTAL)"
440 Compile both the PIO and DMA transfer routines into the
441 driver and let the platform select at run-time which one
444 See notes for the DMA option.
448 config MMC_SDRICOH_CS
449 tristate "MMC/SD driver for Ricoh Bay1Controllers (EXPERIMENTAL)"
450 depends on EXPERIMENTAL && PCI && PCMCIA
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.
455 To compile this driver as a module, choose M here: the
456 module will be called sdricoh_cs.
462 tristate "Toshiba Mobile IO Controller (TMIO) MMC/SD function support"
463 depends on MFD_TMIO || MFD_ASIC3
466 This provides support for the SD/MMC cell found in TC6393XB,
467 T7L66XB and also HTC ASIC3
470 tristate "SH-Mobile SDHI SD/SDIO controller support"
471 depends on SUPERH || ARCH_SHMOBILE
474 This provides support for the SDHI SD/SDIO controller found in
475 SuperH and ARM SH-Mobile SoCs
478 tristate "ENE CB710 MMC/SD Interface support"
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
487 This driver can also be built as a module. If so, the module
488 will be called cb710-mmc.
491 tristate "VIA SD/MMC Card Reader Driver"
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
498 If you have a controller with this interface, say Y or M here.
503 tristate "Blackfin Secure Digital Host support"
504 depends on (BF54x && !BF544) || (BF51x && !BF512)
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
510 To compile this driver as a module, choose M here: the
511 module will be called bfin_sdh.
515 config SDH_BFIN_MISSING_CMD_PULLUP_WORKAROUND
516 bool "Blackfin EZkit Missing SDH_CMD Pull Up Resistor Workaround"
519 If you say yes here SD-Cards may work on the EZkit.
522 tristate "Synopsys DesignWare Memory Card Interface"
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.
530 bool "Internal DMAC interface"
533 This selects support for the internal DMAC block within the Synopsys
534 Designware Mobile Storage IP block. This disables the external DMA
538 tristate "SuperH Internal MMCIF support"
539 depends on MMC_BLOCK && (SUPERH || ARCH_SHMOBILE)
541 This selects the MMC Host Interface controller (MMCIF).
543 This driver supports MMCIF in sh7724/sh7757/sh7372.
546 tristate "JZ4740 SD/Multimedia Card Interface support"
547 depends on MACH_JZ4740
549 This selects support for the SD/MMC controller on Ingenic JZ4740
551 If you have a board based on such a SoC and with a SD/MMC slot,
555 tristate "VUB300 USB to SDIO/SD/MMC Host Controller support"
558 This selects support for Elan Digital Systems' VUB300 chip.
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.
564 The VUB300 chip will be found in both physically separate
565 USB to SDIO/SD/MMC adapters and embedded on some motherboards.
567 The VUB300 chip supports SD and MMC memory cards in addition
568 to single and multifunction SDIO cards.
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.
578 To compile this mmc host controller driver as a module,
579 choose M here: the module will be called vub300.
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.
586 tristate "USB SD Host Controller (USHC) support"
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).
593 CSR boards with this device include: USB<>SDIO (M1985v2),
596 Note: These controllers only support SDIO cards and do not
597 support MMC or SD memory cards.