2 # MMC core configuration
5 tristate "HW reset support for eMMC"
9 This selects Hardware reset support aka pwrseq-emmc for eMMC
10 devices. By default this option is set to y.
12 This driver can also be built as a module. If so, the module
13 will be called pwrseq_emmc.
16 tristate "Simple HW reset support for MMC"
20 This selects simple hardware reset support aka pwrseq-simple for MMC
21 devices. By default this option is set to y.
23 This driver can also be built as a module. If so, the module
24 will be called pwrseq_simple.
27 tristate "MMC block device driver"
31 Say Y here to enable the MMC block device driver support.
32 This provides a block device driver, which you can use to
33 mount the filesystem. Almost everyone wishing MMC support
34 should say Y or M here.
36 config MMC_BLOCK_MINORS
37 int "Number of minors per block device"
42 Number of minors per block device. One is needed for every
43 partition on the disk (plus one for the whole disk).
45 Number of total MMC minors available is 256, so your number
46 of supported block devices will be limited to 256 divided
49 Default is 8 to be backwards compatible with previous
50 hardwired device numbering.
52 If unsure, say 8 here.
54 config MMC_BLOCK_BOUNCE
55 bool "Use bounce buffer for simple hosts"
59 SD/MMC is a high latency protocol where it is crucial to
60 send large requests in order to get high performance. Many
61 controllers, however, are restricted to continuous memory
62 (i.e. they can't do scatter-gather), something the kernel
65 Say Y here to help these restricted hosts by bouncing
66 requests back and forth from a large buffer. You will get
67 a big performance gain at the cost of up to 64 KiB of
70 If unsure, say Y here.
73 tristate "SDIO UART/GPS class support"
76 SDIO function driver for SDIO cards that implements the UART
77 class, as well as the GPS class which appears like a UART.
80 tristate "MMC host test driver"
82 Development driver that performs a series of reads and writes
83 to a memory card in order to expose certain well known bugs
84 in host controllers. The tests are executed by writing to the
85 "test" file in debugfs under each card. Note that whatever is
86 on your card will be overwritten by these tests.
88 This driver is only of interest to those developing or
89 testing a host driver. Most people should say N here.