Kconfig 19 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644
  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 (EXPERIMENTAL)"
  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. Note, due to the problems with DMA, the DMA support is only
  149. available with CONFIG_EXPERIMENTAL is selected.
  150. If you have a controller with this interface, say Y or M here.
  151. If unsure, say N.
  152. config MMC_SDHCI_PXAV3
  153. tristate "Marvell MMP2 SD Host Controller support (PXAV3)"
  154. depends on CLKDEV_LOOKUP
  155. select MMC_SDHCI
  156. select MMC_SDHCI_PLTFM
  157. default CPU_MMP2
  158. help
  159. This selects the Marvell(R) PXAV3 SD Host Controller.
  160. If you have a MMP2 platform with SD Host Controller
  161. and a card slot, say Y or M here.
  162. If unsure, say N.
  163. config MMC_SDHCI_PXAV2
  164. tristate "Marvell PXA9XX SD Host Controller support (PXAV2)"
  165. depends on CLKDEV_LOOKUP
  166. select MMC_SDHCI
  167. select MMC_SDHCI_PLTFM
  168. default CPU_PXA910
  169. help
  170. This selects the Marvell(R) PXAV2 SD Host Controller.
  171. If you have a PXA9XX platform with SD Host Controller
  172. and a card slot, say Y or M here.
  173. If unsure, say N.
  174. config MMC_SDHCI_SPEAR
  175. tristate "SDHCI support on ST SPEAr platform"
  176. depends on MMC_SDHCI && PLAT_SPEAR
  177. help
  178. This selects the Secure Digital Host Controller Interface (SDHCI)
  179. often referrered to as the HSMMC block in some of the ST SPEAR range
  180. of SoC
  181. If you have a controller with this interface, say Y or M here.
  182. If unsure, say N.
  183. config MMC_SDHCI_S3C_DMA
  184. bool "DMA support on S3C SDHCI"
  185. depends on MMC_SDHCI_S3C && EXPERIMENTAL
  186. help
  187. Enable DMA support on the Samsung S3C SDHCI glue. The DMA
  188. has proved to be problematic if the controller encounters
  189. certain errors, and thus should be treated with care.
  190. YMMV.
  191. config MMC_SDHCI_BCM2835
  192. tristate "SDHCI platform support for the BCM2835 SD/MMC Controller"
  193. depends on ARCH_BCM2835
  194. depends on MMC_SDHCI_PLTFM
  195. select MMC_SDHCI_IO_ACCESSORS
  196. help
  197. This selects the BCM2835 SD/MMC controller. If you have a BCM2835
  198. platform with SD or MMC devices, say Y or M here.
  199. If unsure, say N.
  200. config MMC_OMAP
  201. tristate "TI OMAP Multimedia Card Interface support"
  202. depends on ARCH_OMAP
  203. select TPS65010 if MACH_OMAP_H2
  204. help
  205. This selects the TI OMAP Multimedia card Interface.
  206. If you have an OMAP board with a Multimedia Card slot,
  207. say Y or M here.
  208. If unsure, say N.
  209. config MMC_OMAP_HS
  210. tristate "TI OMAP High Speed Multimedia Card Interface support"
  211. depends on SOC_OMAP2430 || ARCH_OMAP3 || ARCH_OMAP4
  212. help
  213. This selects the TI OMAP High Speed Multimedia card Interface.
  214. If you have an OMAP2430 or OMAP3 board or OMAP4 board with a
  215. Multimedia Card slot, say Y or M here.
  216. If unsure, say N.
  217. config MMC_WBSD
  218. tristate "Winbond W83L51xD SD/MMC Card Interface support"
  219. depends on ISA_DMA_API
  220. help
  221. This selects the Winbond(R) W83L51xD Secure digital and
  222. Multimedia card Interface.
  223. If you have a machine with a integrated W83L518D or W83L519D
  224. SD/MMC card reader, say Y or M here.
  225. If unsure, say N.
  226. config MMC_AU1X
  227. tristate "Alchemy AU1XX0 MMC Card Interface support"
  228. depends on MIPS_ALCHEMY
  229. help
  230. This selects the AMD Alchemy(R) Multimedia card interface.
  231. If you have a Alchemy platform with a MMC slot, say Y or M here.
  232. If unsure, say N.
  233. config MMC_ATMELMCI
  234. tristate "Atmel SD/MMC Driver (Multimedia Card Interface)"
  235. depends on AVR32 || ARCH_AT91
  236. help
  237. This selects the Atmel Multimedia Card Interface driver. If
  238. you have an AT32 (AVR32) or AT91 platform with a Multimedia
  239. Card slot, say Y or M here.
  240. If unsure, say N.
  241. config MMC_ATMELMCI_DMA
  242. bool "Atmel MCI DMA support"
  243. depends on MMC_ATMELMCI && (AVR32 || ARCH_AT91SAM9G45) && DMA_ENGINE
  244. help
  245. Say Y here to have the Atmel MCI driver use a DMA engine to
  246. do data transfers and thus increase the throughput and
  247. reduce the CPU utilization.
  248. If unsure, say N.
  249. config MMC_MSM
  250. tristate "Qualcomm SDCC Controller Support"
  251. depends on MMC && ARCH_MSM
  252. help
  253. This provides support for the SD/MMC cell found in the
  254. MSM and QSD SOCs from Qualcomm. The controller also has
  255. support for SDIO devices.
  256. config MMC_MXC
  257. tristate "Freescale i.MX21/27/31 Multimedia Card Interface support"
  258. depends on ARCH_MXC
  259. help
  260. This selects the Freescale i.MX21, i.MX27 and i.MX31 Multimedia card
  261. Interface. If you have a i.MX platform with a Multimedia Card slot,
  262. say Y or M here.
  263. If unsure, say N.
  264. config MMC_MXS
  265. tristate "Freescale MXS Multimedia Card Interface support"
  266. depends on ARCH_MXS && MXS_DMA
  267. help
  268. This selects the Freescale SSP MMC controller found on MXS based
  269. platforms like mx23/28.
  270. If unsure, say N.
  271. config MMC_TIFM_SD
  272. tristate "TI Flash Media MMC/SD Interface support (EXPERIMENTAL)"
  273. depends on EXPERIMENTAL && PCI
  274. select TIFM_CORE
  275. help
  276. Say Y here if you want to be able to access MMC/SD cards with
  277. the Texas Instruments(R) Flash Media card reader, found in many
  278. laptops.
  279. This option 'selects' (turns on, enables) 'TIFM_CORE', but you
  280. probably also need appropriate card reader host adapter, such as
  281. 'Misc devices: TI Flash Media PCI74xx/PCI76xx host adapter support
  282. (TIFM_7XX1)'.
  283. To compile this driver as a module, choose M here: the
  284. module will be called tifm_sd.
  285. config MMC_MVSDIO
  286. tristate "Marvell MMC/SD/SDIO host driver"
  287. depends on PLAT_ORION
  288. ---help---
  289. This selects the Marvell SDIO host driver.
  290. SDIO may currently be found on the Kirkwood 88F6281 and 88F6192
  291. SoC controllers.
  292. To compile this driver as a module, choose M here: the
  293. module will be called mvsdio.
  294. config MMC_DAVINCI
  295. tristate "TI DAVINCI Multimedia Card Interface support"
  296. depends on ARCH_DAVINCI
  297. help
  298. This selects the TI DAVINCI Multimedia card Interface.
  299. If you have an DAVINCI board with a Multimedia Card slot,
  300. say Y or M here. If unsure, say N.
  301. config MMC_SPI
  302. tristate "MMC/SD/SDIO over SPI"
  303. depends on SPI_MASTER && !HIGHMEM && HAS_DMA
  304. select CRC7
  305. select CRC_ITU_T
  306. help
  307. Some systems access MMC/SD/SDIO cards using a SPI controller
  308. instead of using a "native" MMC/SD/SDIO controller. This has a
  309. disadvantage of being relatively high overhead, but a compensating
  310. advantage of working on many systems without dedicated MMC/SD/SDIO
  311. controllers.
  312. If unsure, or if your system has no SPI master driver, say N.
  313. config MMC_S3C
  314. tristate "Samsung S3C SD/MMC Card Interface support"
  315. depends on ARCH_S3C24XX
  316. help
  317. This selects a driver for the MCI interface found in
  318. Samsung's S3C2410, S3C2412, S3C2440, S3C2442 CPUs.
  319. If you have a board based on one of those and a MMC/SD
  320. slot, say Y or M here.
  321. If unsure, say N.
  322. config MMC_S3C_HW_SDIO_IRQ
  323. bool "Hardware support for SDIO IRQ"
  324. depends on MMC_S3C
  325. help
  326. Enable the hardware support for SDIO interrupts instead of using
  327. the generic polling code.
  328. choice
  329. prompt "Samsung S3C SD/MMC transfer code"
  330. depends on MMC_S3C
  331. config MMC_S3C_PIO
  332. bool "Use PIO transfers only"
  333. help
  334. Use PIO to transfer data between memory and the hardware.
  335. PIO is slower than DMA as it requires CPU instructions to
  336. move the data. This has been the traditional default for
  337. the S3C MCI driver.
  338. config MMC_S3C_DMA
  339. bool "Use DMA transfers only (EXPERIMENTAL)"
  340. depends on EXPERIMENTAL
  341. help
  342. Use DMA to transfer data between memory and the hardare.
  343. Currently, the DMA support in this driver seems to not be
  344. working properly and needs to be debugged before this
  345. option is useful.
  346. config MMC_S3C_PIODMA
  347. bool "Support for both PIO and DMA (EXPERIMENTAL)"
  348. help
  349. Compile both the PIO and DMA transfer routines into the
  350. driver and let the platform select at run-time which one
  351. is best.
  352. See notes for the DMA option.
  353. endchoice
  354. config MMC_SDRICOH_CS
  355. tristate "MMC/SD driver for Ricoh Bay1Controllers (EXPERIMENTAL)"
  356. depends on EXPERIMENTAL && PCI && PCMCIA
  357. help
  358. Say Y here if your Notebook reports a Ricoh Bay1Controller PCMCIA
  359. card whenever you insert a MMC or SD card into the card slot.
  360. To compile this driver as a module, choose M here: the
  361. module will be called sdricoh_cs.
  362. config MMC_TMIO_CORE
  363. tristate
  364. config MMC_TMIO
  365. tristate "Toshiba Mobile IO Controller (TMIO) MMC/SD function support"
  366. depends on MFD_TMIO || MFD_ASIC3
  367. select MMC_TMIO_CORE
  368. help
  369. This provides support for the SD/MMC cell found in TC6393XB,
  370. T7L66XB and also HTC ASIC3
  371. config MMC_SDHI
  372. tristate "SH-Mobile SDHI SD/SDIO controller support"
  373. depends on SUPERH || ARCH_SHMOBILE
  374. select MMC_TMIO_CORE
  375. help
  376. This provides support for the SDHI SD/SDIO controller found in
  377. SuperH and ARM SH-Mobile SoCs
  378. config MMC_CB710
  379. tristate "ENE CB710 MMC/SD Interface support"
  380. depends on PCI
  381. select CB710_CORE
  382. help
  383. This option enables support for MMC/SD part of ENE CB710/720 Flash
  384. memory card reader found in some laptops (ie. some versions of
  385. HP Compaq nx9500).
  386. This driver can also be built as a module. If so, the module
  387. will be called cb710-mmc.
  388. config MMC_VIA_SDMMC
  389. tristate "VIA SD/MMC Card Reader Driver"
  390. depends on PCI
  391. help
  392. This selects the VIA SD/MMC Card Reader driver, say Y or M here.
  393. VIA provides one multi-functional card reader which integrated into
  394. some motherboards manufactured by VIA. This card reader supports
  395. SD/MMC/SDHC.
  396. If you have a controller with this interface, say Y or M here.
  397. If unsure, say N.
  398. config SDH_BFIN
  399. tristate "Blackfin Secure Digital Host support"
  400. depends on (BF54x && !BF544) || (BF51x && !BF512)
  401. help
  402. If you say yes here you will get support for the Blackfin on-chip
  403. Secure Digital Host interface. This includes support for MMC and
  404. SD cards.
  405. To compile this driver as a module, choose M here: the
  406. module will be called bfin_sdh.
  407. If unsure, say N.
  408. config SDH_BFIN_MISSING_CMD_PULLUP_WORKAROUND
  409. bool "Blackfin EZkit Missing SDH_CMD Pull Up Resistor Workaround"
  410. depends on SDH_BFIN
  411. help
  412. If you say yes here SD-Cards may work on the EZkit.
  413. config MMC_DW
  414. tristate "Synopsys DesignWare Memory Card Interface"
  415. depends on ARM
  416. help
  417. This selects support for the Synopsys DesignWare Mobile Storage IP
  418. block, this provides host support for SD and MMC interfaces, in both
  419. PIO and external DMA modes.
  420. config MMC_DW_IDMAC
  421. bool "Internal DMAC interface"
  422. depends on MMC_DW
  423. help
  424. This selects support for the internal DMAC block within the Synopsys
  425. Designware Mobile Storage IP block. This disables the external DMA
  426. interface.
  427. config MMC_DW_PLTFM
  428. tristate "Synopsys Designware MCI Support as platform device"
  429. depends on MMC_DW
  430. default y
  431. help
  432. This selects the common helper functions support for Host Controller
  433. Interface based platform driver. Please select this option if the IP
  434. is present as a platform device. This is the common interface for the
  435. Synopsys Designware IP.
  436. If you have a controller with this interface, say Y or M here.
  437. If unsure, say Y.
  438. config MMC_DW_EXYNOS
  439. tristate "Exynos specific extensions for Synopsys DW Memory Card Interface"
  440. depends on MMC_DW
  441. select MMC_DW_PLTFM
  442. help
  443. This selects support for Samsung Exynos SoC specific extensions to the
  444. Synopsys DesignWare Memory Card Interface driver. Select this option
  445. for platforms based on Exynos4 and Exynos5 SoC's.
  446. config MMC_DW_PCI
  447. tristate "Synopsys Designware MCI support on PCI bus"
  448. depends on MMC_DW && PCI
  449. help
  450. This selects the PCI bus for the Synopsys Designware Mobile Storage IP.
  451. Select this option if the IP is present on PCI platform.
  452. If you have a controller with this interface, say Y or M here.
  453. If unsure, say N.
  454. config MMC_SH_MMCIF
  455. tristate "SuperH Internal MMCIF support"
  456. depends on MMC_BLOCK && (SUPERH || ARCH_SHMOBILE)
  457. help
  458. This selects the MMC Host Interface controller (MMCIF).
  459. This driver supports MMCIF in sh7724/sh7757/sh7372.
  460. config MMC_JZ4740
  461. tristate "JZ4740 SD/Multimedia Card Interface support"
  462. depends on MACH_JZ4740
  463. help
  464. This selects support for the SD/MMC controller on Ingenic JZ4740
  465. SoCs.
  466. If you have a board based on such a SoC and with a SD/MMC slot,
  467. say Y or M here.
  468. config MMC_VUB300
  469. tristate "VUB300 USB to SDIO/SD/MMC Host Controller support"
  470. depends on USB
  471. help
  472. This selects support for Elan Digital Systems' VUB300 chip.
  473. The VUB300 is a USB-SDIO Host Controller Interface chip
  474. that enables the host computer to use SDIO/SD/MMC cards
  475. via a USB 2.0 or USB 1.1 host.
  476. The VUB300 chip will be found in both physically separate
  477. USB to SDIO/SD/MMC adapters and embedded on some motherboards.
  478. The VUB300 chip supports SD and MMC memory cards in addition
  479. to single and multifunction SDIO cards.
  480. Some SDIO cards will need a firmware file to be loaded and
  481. sent to VUB300 chip in order to achieve better data throughput.
  482. Download these "Offload Pseudocode" from Elan Digital Systems'
  483. web-site http://www.elandigitalsystems.com/support/downloads.php
  484. and put them in /lib/firmware. Note that without these additional
  485. firmware files the VUB300 chip will still function, but not at
  486. the best obtainable data rate.
  487. To compile this mmc host controller driver as a module,
  488. choose M here: the module will be called vub300.
  489. If you have a computer with an embedded VUB300 chip
  490. or if you intend connecting a USB adapter based on a
  491. VUB300 chip say Y or M here.
  492. config MMC_USHC
  493. tristate "USB SD Host Controller (USHC) support"
  494. depends on USB
  495. help
  496. This selects support for USB SD Host Controllers based on
  497. the Cypress Astoria chip with firmware compliant with CSR's
  498. USB SD Host Controller specification (CS-118793-SP).
  499. CSR boards with this device include: USB<>SDIO (M1985v2),
  500. and Ultrasira.
  501. Note: These controllers only support SDIO cards and do not
  502. support MMC or SD memory cards.
  503. config MMC_WMT
  504. tristate "Wondermedia SD/MMC Host Controller support"
  505. depends on ARCH_VT8500
  506. default y
  507. help
  508. This selects support for the SD/MMC Host Controller on
  509. Wondermedia WM8505/WM8650 based SoCs.
  510. To compile this driver as a module, choose M here: the
  511. module will be called wmt-sdmmc.
  512. config MMC_REALTEK_PCI
  513. tristate "Realtek PCI-E SD/MMC Card Interface Driver"
  514. depends on MFD_RTSX_PCI
  515. help
  516. Say Y here to include driver code to support SD/MMC card interface
  517. of Realtek PCI-E card reader