Kconfig 19 KB

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