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 support for the Freescale eSDHC/uSDHC i.MX controller"
135 depends on MMC_SDHCI_PLTFM
136 select MMC_SDHCI_IO_ACCESSORS
138 This selects the Freescale eSDHC/uSDHC controller support
139 found on i.MX25, i.MX35 i.MX5x and i.MX6x.
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 MIPS_ALCHEMY
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 (DEPRECATED)"
284 This selects the AT91 MCI controller. This driver will
285 be removed soon (for more information have a look to
286 Documentation/feature-removal-schedule.txt). Please use
292 tristate "Atmel Multimedia Card Interface support"
293 depends on AVR32 || ARCH_AT91
295 This selects the Atmel Multimedia Card Interface driver. If
296 you have an AT32 (AVR32) or AT91 platform with a Multimedia
297 Card slot, say Y or M here.
303 config MMC_ATMELMCI_DMA
304 bool "Atmel MCI DMA support"
305 depends on MMC_ATMELMCI && (AVR32 || ARCH_AT91SAM9G45) && DMA_ENGINE
307 Say Y here to have the Atmel MCI driver use a DMA engine to
308 do data transfers and thus increase the throughput and
309 reduce the CPU utilization.
314 tristate "Qualcomm SDCC Controller Support"
315 depends on MMC && ARCH_MSM
317 This provides support for the SD/MMC cell found in the
318 MSM and QSD SOCs from Qualcomm. The controller also has
319 support for SDIO devices.
322 tristate "Freescale i.MX21/27/31 Multimedia Card Interface support"
325 This selects the Freescale i.MX21, i.MX27 and i.MX31 Multimedia card
326 Interface. If you have a i.MX platform with a Multimedia Card slot,
332 tristate "Freescale MXS Multimedia Card Interface support"
333 depends on ARCH_MXS && MXS_DMA
335 This selects the Freescale SSP MMC controller found on MXS based
336 platforms like mx23/28.
341 tristate "TI Flash Media MMC/SD Interface support (EXPERIMENTAL)"
342 depends on EXPERIMENTAL && PCI
345 Say Y here if you want to be able to access MMC/SD cards with
346 the Texas Instruments(R) Flash Media card reader, found in many
348 This option 'selects' (turns on, enables) 'TIFM_CORE', but you
349 probably also need appropriate card reader host adapter, such as
350 'Misc devices: TI Flash Media PCI74xx/PCI76xx host adapter support
353 To compile this driver as a module, choose M here: the
354 module will be called tifm_sd.
357 tristate "Marvell MMC/SD/SDIO host driver"
358 depends on PLAT_ORION
360 This selects the Marvell SDIO host driver.
361 SDIO may currently be found on the Kirkwood 88F6281 and 88F6192
364 To compile this driver as a module, choose M here: the
365 module will be called mvsdio.
368 tristate "TI DAVINCI Multimedia Card Interface support"
369 depends on ARCH_DAVINCI
371 This selects the TI DAVINCI Multimedia card Interface.
372 If you have an DAVINCI board with a Multimedia Card slot,
373 say Y or M here. If unsure, say N.
376 tristate "MMC/SD/SDIO over SPI"
377 depends on SPI_MASTER && !HIGHMEM && HAS_DMA
381 Some systems access MMC/SD/SDIO cards using a SPI controller
382 instead of using a "native" MMC/SD/SDIO controller. This has a
383 disadvantage of being relatively high overhead, but a compensating
384 advantage of working on many systems without dedicated MMC/SD/SDIO
387 If unsure, or if your system has no SPI master driver, say N.
390 tristate "Samsung S3C SD/MMC Card Interface support"
391 depends on ARCH_S3C24XX
393 This selects a driver for the MCI interface found in
394 Samsung's S3C2410, S3C2412, S3C2440, S3C2442 CPUs.
395 If you have a board based on one of those and a MMC/SD
396 slot, say Y or M here.
400 config MMC_S3C_HW_SDIO_IRQ
401 bool "Hardware support for SDIO IRQ"
404 Enable the hardware support for SDIO interrupts instead of using
405 the generic polling code.
408 prompt "Samsung S3C SD/MMC transfer code"
412 bool "Use PIO transfers only"
414 Use PIO to transfer data between memory and the hardware.
416 PIO is slower than DMA as it requires CPU instructions to
417 move the data. This has been the traditional default for
421 bool "Use DMA transfers only (EXPERIMENTAL)"
422 depends on EXPERIMENTAL
424 Use DMA to transfer data between memory and the hardare.
426 Currently, the DMA support in this driver seems to not be
427 working properly and needs to be debugged before this
430 config MMC_S3C_PIODMA
431 bool "Support for both PIO and DMA (EXPERIMENTAL)"
433 Compile both the PIO and DMA transfer routines into the
434 driver and let the platform select at run-time which one
437 See notes for the DMA option.
441 config MMC_SDRICOH_CS
442 tristate "MMC/SD driver for Ricoh Bay1Controllers (EXPERIMENTAL)"
443 depends on EXPERIMENTAL && PCI && PCMCIA
445 Say Y here if your Notebook reports a Ricoh Bay1Controller PCMCIA
446 card whenever you insert a MMC or SD card into the card slot.
448 To compile this driver as a module, choose M here: the
449 module will be called sdricoh_cs.
455 tristate "Toshiba Mobile IO Controller (TMIO) MMC/SD function support"
456 depends on MFD_TMIO || MFD_ASIC3
459 This provides support for the SD/MMC cell found in TC6393XB,
460 T7L66XB and also HTC ASIC3
463 tristate "SH-Mobile SDHI SD/SDIO controller support"
464 depends on SUPERH || ARCH_SHMOBILE
467 This provides support for the SDHI SD/SDIO controller found in
468 SuperH and ARM SH-Mobile SoCs
471 tristate "ENE CB710 MMC/SD Interface support"
475 This option enables support for MMC/SD part of ENE CB710/720 Flash
476 memory card reader found in some laptops (ie. some versions of
479 This driver can also be built as a module. If so, the module
480 will be called cb710-mmc.
483 tristate "VIA SD/MMC Card Reader Driver"
486 This selects the VIA SD/MMC Card Reader driver, say Y or M here.
487 VIA provides one multi-functional card reader which integrated into
488 some motherboards manufactured by VIA. This card reader supports
490 If you have a controller with this interface, say Y or M here.
495 tristate "Blackfin Secure Digital Host support"
496 depends on (BF54x && !BF544) || (BF51x && !BF512)
498 If you say yes here you will get support for the Blackfin on-chip
499 Secure Digital Host interface. This includes support for MMC and
502 To compile this driver as a module, choose M here: the
503 module will be called bfin_sdh.
507 config SDH_BFIN_MISSING_CMD_PULLUP_WORKAROUND
508 bool "Blackfin EZkit Missing SDH_CMD Pull Up Resistor Workaround"
511 If you say yes here SD-Cards may work on the EZkit.
514 tristate "Synopsys DesignWare Memory Card Interface"
517 This selects support for the Synopsys DesignWare Mobile Storage IP
518 block, this provides host support for SD and MMC interfaces, in both
519 PIO and external DMA modes.
522 bool "Internal DMAC interface"
525 This selects support for the internal DMAC block within the Synopsys
526 Designware Mobile Storage IP block. This disables the external DMA
530 tristate "Synopsys Designware MCI Support as platform device"
534 This selects the common helper functions support for Host Controller
535 Interface based platform driver. Please select this option if the IP
536 is present as a platform device. This is the common interface for the
537 Synopsys Designware IP.
539 If you have a controller with this interface, say Y or M here.
544 tristate "Exynos specific extentions for Synopsys DW Memory Card Interface"
548 This selects support for Samsung Exynos SoC specific extensions to the
549 Synopsys DesignWare Memory Card Interface driver. Select this option
550 for platforms based on Exynos4 and Exynos5 SoC's.
553 tristate "Synopsys Designware MCI support on PCI bus"
554 depends on MMC_DW && PCI
556 This selects the PCI bus for the Synopsys Designware Mobile Storage IP.
557 Select this option if the IP is present on PCI platform.
559 If you have a controller with this interface, say Y or M here.
564 tristate "SuperH Internal MMCIF support"
565 depends on MMC_BLOCK && (SUPERH || ARCH_SHMOBILE)
567 This selects the MMC Host Interface controller (MMCIF).
569 This driver supports MMCIF in sh7724/sh7757/sh7372.
572 tristate "JZ4740 SD/Multimedia Card Interface support"
573 depends on MACH_JZ4740
575 This selects support for the SD/MMC controller on Ingenic JZ4740
577 If you have a board based on such a SoC and with a SD/MMC slot,
581 tristate "VUB300 USB to SDIO/SD/MMC Host Controller support"
584 This selects support for Elan Digital Systems' VUB300 chip.
586 The VUB300 is a USB-SDIO Host Controller Interface chip
587 that enables the host computer to use SDIO/SD/MMC cards
588 via a USB 2.0 or USB 1.1 host.
590 The VUB300 chip will be found in both physically separate
591 USB to SDIO/SD/MMC adapters and embedded on some motherboards.
593 The VUB300 chip supports SD and MMC memory cards in addition
594 to single and multifunction SDIO cards.
596 Some SDIO cards will need a firmware file to be loaded and
597 sent to VUB300 chip in order to achieve better data throughput.
598 Download these "Offload Pseudocode" from Elan Digital Systems'
599 web-site http://www.elandigitalsystems.com/support/downloads.php
600 and put them in /lib/firmware. Note that without these additional
601 firmware files the VUB300 chip will still function, but not at
602 the best obtainable data rate.
604 To compile this mmc host controller driver as a module,
605 choose M here: the module will be called vub300.
607 If you have a computer with an embedded VUB300 chip
608 or if you intend connecting a USB adapter based on a
609 VUB300 chip say Y or M here.
612 tristate "USB SD Host Controller (USHC) support"
615 This selects support for USB SD Host Controllers based on
616 the Cypress Astoria chip with firmware compliant with CSR's
617 USB SD Host Controller specification (CS-118793-SP).
619 CSR boards with this device include: USB<>SDIO (M1985v2),
622 Note: These controllers only support SDIO cards and do not
623 support MMC or SD memory cards.
625 config MMC_REALTEK_PCI
626 tristate "Realtek PCI-E SD/MMC Card Interface Driver"
627 depends on MFD_RTSX_PCI
629 Say Y here to include driver code to support SD/MMC card interface
630 of Realtek PCI-E card reader