ir-core: fix gcc-7 warning on bool arithmetic
[GitHub/mt8127/android_kernel_alcatel_ttab.git] / drivers / mmc / card / Kconfig
1 #
2 # MMC/SD card drivers
3 #
4
5 comment "MMC/SD/SDIO Card Drivers"
6
7 config MMC_BLOCK
8 tristate "MMC block device driver"
9 depends on BLOCK
10 default y
11 help
12 Say Y here to enable the MMC block device driver support.
13 This provides a block device driver, which you can use to
14 mount the filesystem. Almost everyone wishing MMC support
15 should say Y or M here.
16
17 config MMC_BLOCK_MINORS
18 int "Number of minors per block device"
19 depends on MMC_BLOCK
20 range 4 256
21 default 8
22 help
23 Number of minors per block device. One is needed for every
24 partition on the disk (plus one for the whole disk).
25
26 Number of total MMC minors available is 256, so your number
27 of supported block devices will be limited to 256 divided
28 by this number.
29
30 Default is 8 to be backwards compatible with previous
31 hardwired device numbering.
32
33 If unsure, say 8 here.
34
35 config MMC_BLOCK_BOUNCE
36 bool "Use bounce buffer for simple hosts"
37 depends on MMC_BLOCK
38 default y
39 help
40 SD/MMC is a high latency protocol where it is crucial to
41 send large requests in order to get high performance. Many
42 controllers, however, are restricted to continuous memory
43 (i.e. they can't do scatter-gather), something the kernel
44 rarely can provide.
45
46 Say Y here to help these restricted hosts by bouncing
47 requests back and forth from a large buffer. You will get
48 a big performance gain at the cost of up to 64 KiB of
49 physical memory.
50
51 If unsure, say Y here.
52
53 config SDIO_UART
54 tristate "SDIO UART/GPS class support"
55 depends on TTY
56 help
57 SDIO function driver for SDIO cards that implements the UART
58 class, as well as the GPS class which appears like a UART.
59
60 config MMC_TEST
61 tristate "MMC host test driver"
62 help
63 Development driver that performs a series of reads and writes
64 to a memory card in order to expose certain well known bugs
65 in host controllers. The tests are executed by writing to the
66 "test" file in debugfs under each card. Note that whatever is
67 on your card will be overwritten by these tests.
68
69 This driver is only of interest to those developing or
70 testing a host driver. Most people should say N here.