Kconfig 18 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598
  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_PLTFM
  68. tristate "SDHCI platform and OF driver helper"
  69. depends on MMC_SDHCI
  70. help
  71. This selects the common helper functions support for Secure Digital
  72. Host Controller Interface based platform and OF drivers.
  73. If you have a controller with this interface, say Y or M here.
  74. If unsure, say N.
  75. config MMC_SDHCI_OF_ESDHC
  76. tristate "SDHCI OF support for the Freescale eSDHC controller"
  77. depends on MMC_SDHCI_PLTFM
  78. depends on PPC_OF
  79. select MMC_SDHCI_BIG_ENDIAN_32BIT_BYTE_SWAPPER
  80. help
  81. This selects the Freescale eSDHC controller support.
  82. If you have a controller with this interface, say Y or M here.
  83. If unsure, say N.
  84. config MMC_SDHCI_OF_HLWD
  85. tristate "SDHCI OF support for the Nintendo Wii SDHCI controllers"
  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 Secure Digital Host Controller Interface (SDHCI)
  91. found in the "Hollywood" chipset of the Nintendo Wii video game
  92. console.
  93. If you have a controller with this interface, say Y or M here.
  94. If unsure, say N.
  95. config MMC_SDHCI_CNS3XXX
  96. tristate "SDHCI support on the Cavium Networks CNS3xxx SoC"
  97. depends on ARCH_CNS3XXX
  98. depends on MMC_SDHCI_PLTFM
  99. help
  100. This selects the SDHCI support for CNS3xxx System-on-Chip devices.
  101. If you have a controller with this interface, say Y or M here.
  102. If unsure, say N.
  103. config MMC_SDHCI_ESDHC_IMX
  104. tristate "SDHCI platform support for the Freescale eSDHC i.MX controller"
  105. depends on ARCH_MX25 || ARCH_MX35 || ARCH_MX5
  106. depends on MMC_SDHCI_PLTFM
  107. select MMC_SDHCI_IO_ACCESSORS
  108. help
  109. This selects the Freescale eSDHC controller support on the platform
  110. bus, found on platforms like mx35/51.
  111. If you have a controller with this interface, say Y or M here.
  112. If unsure, say N.
  113. config MMC_SDHCI_DOVE
  114. tristate "SDHCI support on Marvell's Dove SoC"
  115. depends on ARCH_DOVE
  116. depends on MMC_SDHCI_PLTFM
  117. select MMC_SDHCI_IO_ACCESSORS
  118. help
  119. This selects the Secure Digital Host Controller Interface in
  120. Marvell's Dove SoC.
  121. If you have a controller with this interface, say Y or M here.
  122. If unsure, say N.
  123. config MMC_SDHCI_TEGRA
  124. tristate "SDHCI platform support for the Tegra SD/MMC Controller"
  125. depends on ARCH_TEGRA
  126. depends on MMC_SDHCI_PLTFM
  127. select MMC_SDHCI_IO_ACCESSORS
  128. help
  129. This selects the Tegra SD/MMC controller. If you have a Tegra
  130. platform with SD or MMC devices, say Y or M here.
  131. If unsure, say N.
  132. config MMC_SDHCI_S3C
  133. tristate "SDHCI support on Samsung S3C SoC"
  134. depends on MMC_SDHCI && PLAT_SAMSUNG
  135. help
  136. This selects the Secure Digital Host Controller Interface (SDHCI)
  137. often referrered to as the HSMMC block in some of the Samsung S3C
  138. range of SoC.
  139. Note, due to the problems with DMA, the DMA support is only
  140. available with CONFIG_EXPERIMENTAL is selected.
  141. If you have a controller with this interface, say Y or M here.
  142. If unsure, say N.
  143. config MMC_SDHCI_PXAV3
  144. tristate "Marvell MMP2 SD Host Controller support (PXAV3)"
  145. depends on CLKDEV_LOOKUP
  146. select MMC_SDHCI
  147. select MMC_SDHCI_PLTFM
  148. default CPU_MMP2
  149. help
  150. This selects the Marvell(R) PXAV3 SD Host Controller.
  151. If you have a MMP2 platform with SD Host Controller
  152. and a card slot, say Y or M here.
  153. If unsure, say N.
  154. config MMC_SDHCI_PXAV2
  155. tristate "Marvell PXA9XX SD Host Controller support (PXAV2)"
  156. depends on CLKDEV_LOOKUP
  157. select MMC_SDHCI
  158. select MMC_SDHCI_PLTFM
  159. default CPU_PXA910
  160. help
  161. This selects the Marvell(R) PXAV2 SD Host Controller.
  162. If you have a PXA9XX platform with SD Host Controller
  163. and a card slot, say Y or M here.
  164. If unsure, say N.
  165. config MMC_SDHCI_SPEAR
  166. tristate "SDHCI support on ST SPEAr platform"
  167. depends on MMC_SDHCI && PLAT_SPEAR
  168. help
  169. This selects the Secure Digital Host Controller Interface (SDHCI)
  170. often referrered to as the HSMMC block in some of the ST SPEAR range
  171. of SoC
  172. If you have a controller with this interface, say Y or M here.
  173. If unsure, say N.
  174. config MMC_SDHCI_S3C_DMA
  175. bool "DMA support on S3C SDHCI"
  176. depends on MMC_SDHCI_S3C && EXPERIMENTAL
  177. help
  178. Enable DMA support on the Samsung S3C SDHCI glue. The DMA
  179. has proved to be problematic if the controller encounters
  180. certain errors, and thus should be treated with care.
  181. YMMV.
  182. config MMC_OMAP
  183. tristate "TI OMAP Multimedia Card Interface support"
  184. depends on ARCH_OMAP
  185. select TPS65010 if MACH_OMAP_H2
  186. help
  187. This selects the TI OMAP Multimedia card Interface.
  188. If you have an OMAP board with a Multimedia Card slot,
  189. say Y or M here.
  190. If unsure, say N.
  191. config MMC_OMAP_HS
  192. tristate "TI OMAP High Speed Multimedia Card Interface support"
  193. depends on SOC_OMAP2430 || ARCH_OMAP3 || ARCH_OMAP4
  194. help
  195. This selects the TI OMAP High Speed Multimedia card Interface.
  196. If you have an OMAP2430 or OMAP3 board or OMAP4 board with a
  197. Multimedia Card slot, say Y or M here.
  198. If unsure, say N.
  199. config MMC_WBSD
  200. tristate "Winbond W83L51xD SD/MMC Card Interface support"
  201. depends on ISA_DMA_API
  202. help
  203. This selects the Winbond(R) W83L51xD Secure digital and
  204. Multimedia card Interface.
  205. If you have a machine with a integrated W83L518D or W83L519D
  206. SD/MMC card reader, say Y or M here.
  207. If unsure, say N.
  208. config MMC_AU1X
  209. tristate "Alchemy AU1XX0 MMC Card Interface support"
  210. depends on SOC_AU1200
  211. help
  212. This selects the AMD Alchemy(R) Multimedia card interface.
  213. If you have a Alchemy platform with a MMC slot, say Y or M here.
  214. If unsure, say N.
  215. choice
  216. prompt "Atmel SD/MMC Driver"
  217. depends on AVR32 || ARCH_AT91
  218. default MMC_ATMELMCI if AVR32
  219. help
  220. Choose which driver to use for the Atmel MCI Silicon
  221. config MMC_AT91
  222. tristate "AT91 SD/MMC Card Interface support"
  223. depends on ARCH_AT91
  224. help
  225. This selects the AT91 MCI controller.
  226. If unsure, say N.
  227. config MMC_ATMELMCI
  228. tristate "Atmel Multimedia Card Interface support"
  229. depends on AVR32 || ARCH_AT91
  230. help
  231. This selects the Atmel Multimedia Card Interface driver. If
  232. you have an AT32 (AVR32) or AT91 platform with a Multimedia
  233. Card slot, say Y or M here.
  234. If unsure, say N.
  235. endchoice
  236. config MMC_ATMELMCI_DMA
  237. bool "Atmel MCI DMA support (EXPERIMENTAL)"
  238. depends on MMC_ATMELMCI && (AVR32 || ARCH_AT91SAM9G45) && DMA_ENGINE && EXPERIMENTAL
  239. help
  240. Say Y here to have the Atmel MCI driver use a DMA engine to
  241. do data transfers and thus increase the throughput and
  242. reduce the CPU utilization. Note that this is highly
  243. experimental and may cause the driver to lock up.
  244. If unsure, say N.
  245. config MMC_IMX
  246. tristate "Motorola i.MX Multimedia Card Interface support"
  247. depends on ARCH_MX1
  248. help
  249. This selects the Motorola i.MX Multimedia card Interface.
  250. If you have a i.MX platform with a Multimedia Card slot,
  251. say Y or M here.
  252. If unsure, say N.
  253. config MMC_MSM
  254. tristate "Qualcomm SDCC Controller Support"
  255. depends on MMC && ARCH_MSM
  256. help
  257. This provides support for the SD/MMC cell found in the
  258. MSM and QSD SOCs from Qualcomm. The controller also has
  259. support for SDIO devices.
  260. config MMC_MXC
  261. tristate "Freescale i.MX2/3 Multimedia Card Interface support"
  262. depends on MACH_MX21 || MACH_MX27 || ARCH_MX31
  263. help
  264. This selects the Freescale i.MX2/3 Multimedia card Interface.
  265. If you have a i.MX platform with a Multimedia Card slot,
  266. say Y or M here.
  267. If unsure, say N.
  268. config MMC_MXS
  269. tristate "Freescale MXS Multimedia Card Interface support"
  270. depends on ARCH_MXS && MXS_DMA
  271. help
  272. This selects the Freescale SSP MMC controller found on MXS based
  273. platforms like mx23/28.
  274. If unsure, say N.
  275. config MMC_TIFM_SD
  276. tristate "TI Flash Media MMC/SD Interface support (EXPERIMENTAL)"
  277. depends on EXPERIMENTAL && PCI
  278. select TIFM_CORE
  279. help
  280. Say Y here if you want to be able to access MMC/SD cards with
  281. the Texas Instruments(R) Flash Media card reader, found in many
  282. laptops.
  283. This option 'selects' (turns on, enables) 'TIFM_CORE', but you
  284. probably also need appropriate card reader host adapter, such as
  285. 'Misc devices: TI Flash Media PCI74xx/PCI76xx host adapter support
  286. (TIFM_7XX1)'.
  287. To compile this driver as a module, choose M here: the
  288. module will be called tifm_sd.
  289. config MMC_MVSDIO
  290. tristate "Marvell MMC/SD/SDIO host driver"
  291. depends on PLAT_ORION
  292. ---help---
  293. This selects the Marvell SDIO host driver.
  294. SDIO may currently be found on the Kirkwood 88F6281 and 88F6192
  295. SoC controllers.
  296. To compile this driver as a module, choose M here: the
  297. module will be called mvsdio.
  298. config MMC_DAVINCI
  299. tristate "TI DAVINCI Multimedia Card Interface support"
  300. depends on ARCH_DAVINCI
  301. help
  302. This selects the TI DAVINCI Multimedia card Interface.
  303. If you have an DAVINCI board with a Multimedia Card slot,
  304. say Y or M here. If unsure, say N.
  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_S3C2410
  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 (EXPERIMENTAL)"
  344. depends on EXPERIMENTAL
  345. help
  346. Use DMA to transfer data between memory and the hardare.
  347. Currently, the DMA support in this driver seems to not be
  348. working properly and needs to be debugged before this
  349. option is useful.
  350. config MMC_S3C_PIODMA
  351. bool "Support for both PIO and DMA (EXPERIMENTAL)"
  352. help
  353. Compile both the PIO and DMA transfer routines into the
  354. driver and let the platform select at run-time which one
  355. is best.
  356. See notes for the DMA option.
  357. endchoice
  358. config MMC_SDRICOH_CS
  359. tristate "MMC/SD driver for Ricoh Bay1Controllers (EXPERIMENTAL)"
  360. depends on EXPERIMENTAL && PCI && PCMCIA
  361. help
  362. Say Y here if your Notebook reports a Ricoh Bay1Controller PCMCIA
  363. card whenever you insert a MMC or SD card into the card slot.
  364. To compile this driver as a module, choose M here: the
  365. module will be called sdricoh_cs.
  366. config MMC_TMIO_CORE
  367. tristate
  368. config MMC_TMIO
  369. tristate "Toshiba Mobile IO Controller (TMIO) MMC/SD function support"
  370. depends on MFD_TMIO || MFD_ASIC3
  371. select MMC_TMIO_CORE
  372. help
  373. This provides support for the SD/MMC cell found in TC6393XB,
  374. T7L66XB and also HTC ASIC3
  375. config MMC_SDHI
  376. tristate "SH-Mobile SDHI SD/SDIO controller support"
  377. depends on SUPERH || ARCH_SHMOBILE
  378. select MMC_TMIO_CORE
  379. help
  380. This provides support for the SDHI SD/SDIO controller found in
  381. SuperH and ARM SH-Mobile SoCs
  382. config MMC_CB710
  383. tristate "ENE CB710 MMC/SD Interface support"
  384. depends on PCI
  385. select MISC_DEVICES
  386. select CB710_CORE
  387. help
  388. This option enables support for MMC/SD part of ENE CB710/720 Flash
  389. memory card reader found in some laptops (ie. some versions of
  390. HP Compaq nx9500).
  391. This driver can also be built as a module. If so, the module
  392. will be called cb710-mmc.
  393. config MMC_VIA_SDMMC
  394. tristate "VIA SD/MMC Card Reader Driver"
  395. depends on PCI
  396. help
  397. This selects the VIA SD/MMC Card Reader driver, say Y or M here.
  398. VIA provides one multi-functional card reader which integrated into
  399. some motherboards manufactured by VIA. This card reader supports
  400. SD/MMC/SDHC.
  401. If you have a controller with this interface, say Y or M here.
  402. If unsure, say N.
  403. config SDH_BFIN
  404. tristate "Blackfin Secure Digital Host support"
  405. depends on (BF54x && !BF544) || (BF51x && !BF512)
  406. help
  407. If you say yes here you will get support for the Blackfin on-chip
  408. Secure Digital Host interface. This includes support for MMC and
  409. SD cards.
  410. To compile this driver as a module, choose M here: the
  411. module will be called bfin_sdh.
  412. If unsure, say N.
  413. config SDH_BFIN_MISSING_CMD_PULLUP_WORKAROUND
  414. bool "Blackfin EZkit Missing SDH_CMD Pull Up Resistor Workaround"
  415. depends on SDH_BFIN
  416. help
  417. If you say yes here SD-Cards may work on the EZkit.
  418. config MMC_DW
  419. tristate "Synopsys DesignWare Memory Card Interface"
  420. depends on ARM
  421. help
  422. This selects support for the Synopsys DesignWare Mobile Storage IP
  423. block, this provides host support for SD and MMC interfaces, in both
  424. PIO and external DMA modes.
  425. config MMC_DW_IDMAC
  426. bool "Internal DMAC interface"
  427. depends on MMC_DW
  428. help
  429. This selects support for the internal DMAC block within the Synopsys
  430. Designware Mobile Storage IP block. This disables the external DMA
  431. interface.
  432. config MMC_SH_MMCIF
  433. tristate "SuperH Internal MMCIF support"
  434. depends on MMC_BLOCK && (SUPERH || ARCH_SHMOBILE)
  435. help
  436. This selects the MMC Host Interface controller (MMCIF).
  437. This driver supports MMCIF in sh7724/sh7757/sh7372.
  438. config MMC_JZ4740
  439. tristate "JZ4740 SD/Multimedia Card Interface support"
  440. depends on MACH_JZ4740
  441. help
  442. This selects support for the SD/MMC controller on Ingenic JZ4740
  443. SoCs.
  444. If you have a board based on such a SoC and with a SD/MMC slot,
  445. say Y or M here.
  446. config MMC_VUB300
  447. tristate "VUB300 USB to SDIO/SD/MMC Host Controller support"
  448. depends on USB
  449. help
  450. This selects support for Elan Digital Systems' VUB300 chip.
  451. The VUB300 is a USB-SDIO Host Controller Interface chip
  452. that enables the host computer to use SDIO/SD/MMC cards
  453. via a USB 2.0 or USB 1.1 host.
  454. The VUB300 chip will be found in both physically separate
  455. USB to SDIO/SD/MMC adapters and embedded on some motherboards.
  456. The VUB300 chip supports SD and MMC memory cards in addition
  457. to single and multifunction SDIO cards.
  458. Some SDIO cards will need a firmware file to be loaded and
  459. sent to VUB300 chip in order to achieve better data throughput.
  460. Download these "Offload Pseudocode" from Elan Digital Systems'
  461. web-site http://www.elandigitalsystems.com/support/downloads.php
  462. and put them in /lib/firmware. Note that without these additional
  463. firmware files the VUB300 chip will still function, but not at
  464. the best obtainable data rate.
  465. To compile this mmc host controller driver as a module,
  466. choose M here: the module will be called vub300.
  467. If you have a computer with an embedded VUB300 chip
  468. or if you intend connecting a USB adapter based on a
  469. VUB300 chip say Y or M here.
  470. config MMC_USHC
  471. tristate "USB SD Host Controller (USHC) support"
  472. depends on USB
  473. help
  474. This selects support for USB SD Host Controllers based on
  475. the Cypress Astoria chip with firmware compliant with CSR's
  476. USB SD Host Controller specification (CS-118793-SP).
  477. CSR boards with this device include: USB<>SDIO (M1985v2),
  478. and Ultrasira.
  479. Note: These controllers only support SDIO cards and do not
  480. support MMC or SD memory cards.