2 # MMC/SD host controller drivers
5 comment "MMC/SD/SDIO Host Controller Drivers"
8 tristate "RK emmc controller suppport"
9 depends on ARCH_RK3188 || ARCH_RK3066B || ARCH_RK3026
11 This selects the RK EMMC controller
14 tristate "RK29 SDMMC controller suppport"
17 This selects the RK29 SDMMC controller.
18 SDMMC0 used for sd/mmc card, and SDMMC1 used for sdio.
20 comment "Now, there are two SDMMC controllers selected, SDMMC0 and SDMMC1."
22 bool "Old driver (DEPRECATED)"
24 You will select old,origin driver for your project if you say Yes.
25 It is not good to select the driver.
28 tristate "RK29 SDMMC0 controller support(sdmmc)"
31 This supports the use of the SDMMC0 controller on Rk29 processors.
33 config SDMMC0_RK29_WRITE_PROTECT
34 bool "Write-protect for SDMMC0"
36 depends on SDMMC0_RK29
38 You will add the feature of write-protect for sdmmc-card if you say Yes.
39 Please note that this feature requires hardware support.
41 config SDMMC0_RK29_SDCARD_DET_FROM_GPIO
42 bool "use the gpio-interrupt to detect card"
44 depends on SDMMC0_RK29
46 You can detect the presence of card by the gpio-interrupt if you say Yes.
47 Of course, you must define the pin-name for the detect-pin.
49 If you say No, then detect the card by register interrupt.
51 # config USE_SDMMC0_FOR_WIFI_DEVELOP_BOARD
52 # depends on SDMMC0_RK29
53 # bool "Switch the driver SDMMC0 for the debug of wifi_develop_board."
56 # In order to debug the Wifi development board using SD interface,
57 # we can switch the driver SDMMC0.
61 tristate "RK29 SDMMC1 controller support(sdio)"
64 This supports the use of the SDMMC1 controller on Rk29 processors.
65 config SDMMC1_RK29_WRITE_PROTECT
66 bool "Write-protect for SDMMC1"
68 depends on SDMMC1_RK29
70 You will add the feature of write-protect for sdio-card if you say Yes.
71 Please note that this feature requires hardware support.
73 config RK29_SDIO_IRQ_FROM_GPIO
74 bool "sdio-irq from gpio"
76 depends on SDMMC1_RK29 && (BCM_OOB_ENABLED || MT6620)
78 You will generate sdio interrupt from gpio if you say Yes.
79 Please note that this feature requires hardware support.
83 # config USE_SDMMC1_FOR_WIFI_DEVELOP_BOARD
84 # depends on SDMMC1_RK29
85 # bool "Switch the driver SDMMC1 for the debug of wifi_develop_board."
88 # In order to debug the Wifi development board using SD interface,
89 # we can switch the driver SDMMC1.
94 tristate "ARM AMBA Multimedia Card Interface support"
97 This selects the ARM(R) AMBA(R) PrimeCell Multimedia Card
98 Interface (PL180 and PL181) support. If you have an ARM(R)
99 platform with a Multimedia Card slot, say Y or M here.
104 tristate "Intel PXA25x/26x/27x Multimedia Card Interface support"
107 This selects the Intel(R) PXA(R) Multimedia card Interface.
108 If you have a PXA(R) platform with a Multimedia Card slot,
114 tristate "Secure Digital Host Controller Interface support"
117 This selects the generic Secure Digital Host Controller Interface.
118 It is used by manufacturers such as Texas Instruments(R), Ricoh(R)
119 and Toshiba(R). Most controllers found in laptops are of this type.
121 If you have a controller with this interface, say Y or M here. You
122 also need to enable an appropriate bus interface.
126 config MMC_SDHCI_IO_ACCESSORS
130 This is silent Kconfig symbol that is selected by the drivers that
131 need to overwrite SDHCI IO memory accessors.
133 config MMC_SDHCI_BIG_ENDIAN_32BIT_BYTE_SWAPPER
135 select MMC_SDHCI_IO_ACCESSORS
137 This option is selected by drivers running on big endian hosts
138 and performing I/O to a SDHCI controller through a bus that
139 implements a hardware byte swapper using a 32-bit datum.
140 This endian mapping mode is called "data invariance" and
141 has the effect of scrambling the addresses and formats of data
142 accessed in sizes other than the datum size.
144 This is the case for the Freescale eSDHC and Nintendo Wii SDHCI.
147 tristate "SDHCI support on PCI bus"
148 depends on MMC_SDHCI && PCI
150 This selects the PCI Secure Digital Host Controller Interface.
151 Most controllers found today are PCI devices.
153 If you have a controller with this interface, say Y or M here.
158 bool "Ricoh MMC Controller Disabler (EXPERIMENTAL)"
159 depends on MMC_SDHCI_PCI
161 This adds a pci quirk to disable Ricoh MMC Controller. This
162 proprietary controller is unnecessary because the SDHCI driver
163 supports MMC cards on the SD controller, but if it is not
164 disabled, it will steal the MMC cards away - rendering them
165 useless. It is safe to select this even if you don't
166 have a Ricoh based card reader.
171 tristate "SDHCI support on OpenFirmware platforms"
172 depends on MMC_SDHCI && OF
174 This selects the OF support for Secure Digital Host Controller
179 config MMC_SDHCI_OF_ESDHC
180 bool "SDHCI OF support for the Freescale eSDHC controller"
181 depends on MMC_SDHCI_OF
183 select MMC_SDHCI_BIG_ENDIAN_32BIT_BYTE_SWAPPER
185 This selects the Freescale eSDHC controller support.
189 config MMC_SDHCI_OF_HLWD
190 bool "SDHCI OF support for the Nintendo Wii SDHCI controllers"
191 depends on MMC_SDHCI_OF
193 select MMC_SDHCI_BIG_ENDIAN_32BIT_BYTE_SWAPPER
195 This selects the Secure Digital Host Controller Interface (SDHCI)
196 found in the "Hollywood" chipset of the Nintendo Wii video game
201 config MMC_SDHCI_PLTFM
202 tristate "SDHCI support on the platform specific bus"
205 This selects the platform specific bus support for Secure Digital Host
206 Controller Interface.
208 If you have a controller with this interface, say Y or M here.
212 config MMC_SDHCI_CNS3XXX
213 bool "SDHCI support on the Cavium Networks CNS3xxx SoC"
214 depends on ARCH_CNS3XXX
215 depends on MMC_SDHCI_PLTFM
217 This selects the SDHCI support for CNS3xxx System-on-Chip devices.
221 config MMC_SDHCI_ESDHC_IMX
222 bool "SDHCI platform support for the Freescale eSDHC i.MX controller"
223 depends on MMC_SDHCI_PLTFM && (ARCH_MX25 || ARCH_MX35 || ARCH_MX5)
224 select MMC_SDHCI_IO_ACCESSORS
226 This selects the Freescale eSDHC controller support on the platform
227 bus, found on platforms like mx35/51.
231 config MMC_SDHCI_DOVE
232 bool "SDHCI support on Marvell's Dove SoC"
234 depends on MMC_SDHCI_PLTFM
235 select MMC_SDHCI_IO_ACCESSORS
237 This selects the Secure Digital Host Controller Interface in
242 config MMC_SDHCI_TEGRA
243 bool "SDHCI platform support for the Tegra SD/MMC Controller"
244 depends on MMC_SDHCI_PLTFM && ARCH_TEGRA
245 select MMC_SDHCI_IO_ACCESSORS
247 This selects the Tegra SD/MMC controller. If you have a Tegra
248 platform with SD or MMC devices, say Y or M here.
253 tristate "SDHCI support on Samsung S3C SoC"
254 depends on MMC_SDHCI && PLAT_SAMSUNG
256 This selects the Secure Digital Host Controller Interface (SDHCI)
257 often referrered to as the HSMMC block in some of the Samsung S3C
260 Note, due to the problems with DMA, the DMA support is only
261 available with CONFIG_EXPERIMENTAL is selected.
263 If you have a controller with this interface, say Y or M here.
268 tristate "Marvell PXA168/PXA910/MMP2 SD Host Controller support"
269 depends on ARCH_PXA || ARCH_MMP
271 select MMC_SDHCI_IO_ACCESSORS
273 This selects the Marvell(R) PXA168/PXA910/MMP2 SD Host Controller.
274 If you have a PXA168/PXA910/MMP2 platform with SD Host Controller
275 and a card slot, say Y or M here.
279 config MMC_SDHCI_SPEAR
280 tristate "SDHCI support on ST SPEAr platform"
281 depends on MMC_SDHCI && PLAT_SPEAR
283 This selects the Secure Digital Host Controller Interface (SDHCI)
284 often referrered to as the HSMMC block in some of the ST SPEAR range
287 If you have a controller with this interface, say Y or M here.
291 config MMC_SDHCI_S3C_DMA
292 bool "DMA support on S3C SDHCI"
293 depends on MMC_SDHCI_S3C && EXPERIMENTAL
295 Enable DMA support on the Samsung S3C SDHCI glue. The DMA
296 has proved to be problematic if the controller encounters
297 certain errors, and thus should be treated with care.
302 tristate "TI OMAP Multimedia Card Interface support"
304 select TPS65010 if MACH_OMAP_H2
306 This selects the TI OMAP Multimedia card Interface.
307 If you have an OMAP board with a Multimedia Card slot,
313 tristate "TI OMAP High Speed Multimedia Card Interface support"
314 depends on SOC_OMAP2430 || ARCH_OMAP3 || ARCH_OMAP4
316 This selects the TI OMAP High Speed Multimedia card Interface.
317 If you have an OMAP2430 or OMAP3 board or OMAP4 board with a
318 Multimedia Card slot, say Y or M here.
323 tristate "Winbond W83L51xD SD/MMC Card Interface support"
324 depends on ISA_DMA_API
326 This selects the Winbond(R) W83L51xD Secure digital and
327 Multimedia card Interface.
328 If you have a machine with a integrated W83L518D or W83L519D
329 SD/MMC card reader, say Y or M here.
334 tristate "Alchemy AU1XX0 MMC Card Interface support"
335 depends on SOC_AU1200
337 This selects the AMD Alchemy(R) Multimedia card interface.
338 If you have a Alchemy platform with a MMC slot, say Y or M here.
343 prompt "Atmel SD/MMC Driver"
344 depends on AVR32 || ARCH_AT91
345 default MMC_ATMELMCI if AVR32
347 Choose which driver to use for the Atmel MCI Silicon
350 tristate "AT91 SD/MMC Card Interface support"
353 This selects the AT91 MCI controller.
358 tristate "Atmel Multimedia Card Interface support"
359 depends on AVR32 || ARCH_AT91
361 This selects the Atmel Multimedia Card Interface driver. If
362 you have an AT32 (AVR32) or AT91 platform with a Multimedia
363 Card slot, say Y or M here.
369 config MMC_ATMELMCI_DMA
370 bool "Atmel MCI DMA support (EXPERIMENTAL)"
371 depends on MMC_ATMELMCI && (AVR32 || ARCH_AT91SAM9G45) && DMA_ENGINE && EXPERIMENTAL
373 Say Y here to have the Atmel MCI driver use a DMA engine to
374 do data transfers and thus increase the throughput and
375 reduce the CPU utilization. Note that this is highly
376 experimental and may cause the driver to lock up.
381 tristate "Motorola i.MX Multimedia Card Interface support"
384 This selects the Motorola i.MX Multimedia card Interface.
385 If you have a i.MX platform with a Multimedia Card slot,
391 tristate "Qualcomm SDCC Controller Support"
392 depends on MMC && ARCH_MSM
394 This provides support for the SD/MMC cell found in the
395 MSM and QSD SOCs from Qualcomm. The controller also has
396 support for SDIO devices.
399 tristate "Freescale i.MX2/3 Multimedia Card Interface support"
400 depends on MACH_MX21 || MACH_MX27 || ARCH_MX31
402 This selects the Freescale i.MX2/3 Multimedia card Interface.
403 If you have a i.MX platform with a Multimedia Card slot,
409 tristate "Freescale MXS Multimedia Card Interface support"
410 depends on ARCH_MXS && MXS_DMA
412 This selects the Freescale SSP MMC controller found on MXS based
413 platforms like mx23/28.
418 tristate "TI Flash Media MMC/SD Interface support (EXPERIMENTAL)"
419 depends on EXPERIMENTAL && PCI
422 Say Y here if you want to be able to access MMC/SD cards with
423 the Texas Instruments(R) Flash Media card reader, found in many
425 This option 'selects' (turns on, enables) 'TIFM_CORE', but you
426 probably also need appropriate card reader host adapter, such as
427 'Misc devices: TI Flash Media PCI74xx/PCI76xx host adapter support
430 To compile this driver as a module, choose M here: the
431 module will be called tifm_sd.
434 tristate "Marvell MMC/SD/SDIO host driver"
435 depends on PLAT_ORION
437 This selects the Marvell SDIO host driver.
438 SDIO may currently be found on the Kirkwood 88F6281 and 88F6192
441 To compile this driver as a module, choose M here: the
442 module will be called mvsdio.
445 tristate "TI DAVINCI Multimedia Card Interface support"
446 depends on ARCH_DAVINCI
448 This selects the TI DAVINCI Multimedia card Interface.
449 If you have an DAVINCI board with a Multimedia Card slot,
450 say Y or M here. If unsure, say N.
453 tristate "MMC/SD/SDIO over SPI"
454 depends on SPI_MASTER && !HIGHMEM && HAS_DMA
458 Some systems access MMC/SD/SDIO cards using a SPI controller
459 instead of using a "native" MMC/SD/SDIO controller. This has a
460 disadvantage of being relatively high overhead, but a compensating
461 advantage of working on many systems without dedicated MMC/SD/SDIO
464 If unsure, or if your system has no SPI master driver, say N.
467 tristate "Samsung S3C SD/MMC Card Interface support"
468 depends on ARCH_S3C2410
470 This selects a driver for the MCI interface found in
471 Samsung's S3C2410, S3C2412, S3C2440, S3C2442 CPUs.
472 If you have a board based on one of those and a MMC/SD
473 slot, say Y or M here.
477 config MMC_S3C_HW_SDIO_IRQ
478 bool "Hardware support for SDIO IRQ"
481 Enable the hardware support for SDIO interrupts instead of using
482 the generic polling code.
485 prompt "Samsung S3C SD/MMC transfer code"
489 bool "Use PIO transfers only"
491 Use PIO to transfer data between memory and the hardware.
493 PIO is slower than DMA as it requires CPU instructions to
494 move the data. This has been the traditional default for
498 bool "Use DMA transfers only (EXPERIMENTAL)"
499 depends on EXPERIMENTAL
501 Use DMA to transfer data between memory and the hardare.
503 Currently, the DMA support in this driver seems to not be
504 working properly and needs to be debugged before this
507 config MMC_S3C_PIODMA
508 bool "Support for both PIO and DMA (EXPERIMENTAL)"
510 Compile both the PIO and DMA transfer routines into the
511 driver and let the platform select at run-time which one
514 See notes for the DMA option.
518 config MMC_SDRICOH_CS
519 tristate "MMC/SD driver for Ricoh Bay1Controllers (EXPERIMENTAL)"
520 depends on EXPERIMENTAL && PCI && PCMCIA
522 Say Y here if your Notebook reports a Ricoh Bay1Controller PCMCIA
523 card whenever you insert a MMC or SD card into the card slot.
525 To compile this driver as a module, choose M here: the
526 module will be called sdricoh_cs.
532 tristate "Toshiba Mobile IO Controller (TMIO) MMC/SD function support"
533 depends on MFD_TMIO || MFD_ASIC3
536 This provides support for the SD/MMC cell found in TC6393XB,
537 T7L66XB and also HTC ASIC3
540 tristate "SH-Mobile SDHI SD/SDIO controller support"
541 depends on SUPERH || ARCH_SHMOBILE
544 This provides support for the SDHI SD/SDIO controller found in
545 SuperH and ARM SH-Mobile SoCs
548 tristate "ENE CB710 MMC/SD Interface support"
553 This option enables support for MMC/SD part of ENE CB710/720 Flash
554 memory card reader found in some laptops (ie. some versions of
557 This driver can also be built as a module. If so, the module
558 will be called cb710-mmc.
561 tristate "VIA SD/MMC Card Reader Driver"
564 This selects the VIA SD/MMC Card Reader driver, say Y or M here.
565 VIA provides one multi-functional card reader which integrated into
566 some motherboards manufactured by VIA. This card reader supports
568 If you have a controller with this interface, say Y or M here.
573 tristate "Blackfin Secure Digital Host support"
574 depends on (BF54x && !BF544) || (BF51x && !BF512)
576 If you say yes here you will get support for the Blackfin on-chip
577 Secure Digital Host interface. This includes support for MMC and
580 To compile this driver as a module, choose M here: the
581 module will be called bfin_sdh.
585 config SDH_BFIN_MISSING_CMD_PULLUP_WORKAROUND
586 bool "Blackfin EZkit Missing SDH_CMD Pull Up Resistor Workaround"
589 If you say yes here SD-Cards may work on the EZkit.
592 tristate "Synopsys DesignWare Memory Card Interface"
595 This selects support for the Synopsys DesignWare Mobile Storage IP
596 block, this provides host support for SD and MMC interfaces, in both
597 PIO and external DMA modes.
600 bool "Internal DMAC interface"
603 This selects support for the internal DMAC block within the Synopsys
604 Designware Mobile Storage IP block. This disables the external DMA
608 tristate "SuperH Internal MMCIF support"
609 depends on MMC_BLOCK && (SUPERH || ARCH_SHMOBILE)
611 This selects the MMC Host Interface controller (MMCIF).
613 This driver supports MMCIF in sh7724/sh7757/sh7372.
616 tristate "JZ4740 SD/Multimedia Card Interface support"
617 depends on MACH_JZ4740
619 This selects support for the SD/MMC controller on Ingenic JZ4740
621 If you have a board based on such a SoC and with a SD/MMC slot,
625 tristate "VUB300 USB to SDIO/SD/MMC Host Controller support"
628 This selects support for Elan Digital Systems' VUB300 chip.
630 The VUB300 is a USB-SDIO Host Controller Interface chip
631 that enables the host computer to use SDIO/SD/MMC cards
632 via a USB 2.0 or USB 1.1 host.
634 The VUB300 chip will be found in both physically separate
635 USB to SDIO/SD/MMC adapters and embedded on some motherboards.
637 The VUB300 chip supports SD and MMC memory cards in addition
638 to single and multifunction SDIO cards.
640 Some SDIO cards will need a firmware file to be loaded and
641 sent to VUB300 chip in order to achieve better data throughput.
642 Download these "Offload Pseudocode" from Elan Digital Systems'
643 web-site http://www.elandigitalsystems.com/support/downloads.php
644 and put them in /lib/firmware. Note that without these additional
645 firmware files the VUB300 chip will still function, but not at
646 the best obtainable data rate.
648 To compile this mmc host controller driver as a module,
649 choose M here: the module will be called vub300.
651 If you have a computer with an embedded VUB300 chip
652 or if you intend connecting a USB adapter based on a
653 VUB300 chip say Y or M here.
656 tristate "USB SD Host Controller (USHC) support"
659 This selects support for USB SD Host Controllers based on
660 the Cypress Astoria chip with firmware compliant with CSR's
661 USB SD Host Controller specification (CS-118793-SP).
663 CSR boards with this device include: USB<>SDIO (M1985v2),
666 Note: These controllers only support SDIO cards and do not
667 support MMC or SD memory cards.