1#
 2# MMC core configuration
 3#
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 4
 5config MMC_UNSAFE_RESUME
 6	bool "Assume MMC/SD cards are non-removable (DANGEROUS)"
 
 
 
 7	help
 8	  If you say Y here, the MMC layer will assume that all cards
 9	  stayed in their respective slots during the suspend. The
10	  normal behaviour is to remove them at suspend and
11	  redetecting them at resume. Breaking this assumption will
12	  in most cases result in data corruption.
13
14	  This option is usually just for embedded systems which use
15	  a MMC/SD card for rootfs. Most people should say N here.
16
17	  This option sets a default which can be overridden by the
18	  module parameter "removable=0" or "removable=1".
19
20config MMC_CLKGATE
21	bool "MMC host clock gating (EXPERIMENTAL)"
22	depends on EXPERIMENTAL
23	help
24	  This will attempt to aggressively gate the clock to the MMC card.
25	  This is done to save power due to gating off the logic and bus
26	  noise when the MMC card is not in use. Your host driver has to
27	  support handling this in order for it to be of any use.
28
29	  If unsure, say N.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

 1# SPDX-License-Identifier: GPL-2.0-only
 2#
 3# MMC core configuration
 4#
 5config PWRSEQ_EMMC
 6	tristate "HW reset support for eMMC"
 7	default y
 8	depends on OF
 9	help
10	  This selects Hardware reset support aka pwrseq-emmc for eMMC
11	  devices. By default this option is set to y.
12
13	  This driver can also be built as a module. If so, the module
14	  will be called pwrseq_emmc.
15
16config PWRSEQ_SD8787
17	tristate "HW reset support for SD8787 BT + Wifi module"
18	depends on OF && (MWIFIEX != n || BT_MRVL_SDIO != n || LIBERTAS_SDIO != n || WILC1000_SDIO != n)
19	help
20	  This selects hardware reset support for the SD8787 BT + Wifi
21	  module. By default this option is set to n.
22
23	  This driver can also be built as a module. If so, the module
24	  will be called pwrseq_sd8787.
25
26config PWRSEQ_SIMPLE
27	tristate "Simple HW reset support for MMC"
28	default y
29	depends on OF
30	help
31	  This selects simple hardware reset support aka pwrseq-simple for MMC
32	  devices. By default this option is set to y.
33
34	  This driver can also be built as a module. If so, the module
35	  will be called pwrseq_simple.
36
37config MMC_BLOCK
38	tristate "MMC block device driver"
39	depends on BLOCK
40	depends on RPMB || !RPMB
41	imply IOSCHED_BFQ
42	default y
43	help
44	  Say Y here to enable the MMC block device driver support.
45	  This provides a block device driver, which you can use to
46	  mount the filesystem. Almost everyone wishing MMC support
47	  should say Y or M here.
48
49config MMC_BLOCK_MINORS
50	int "Number of minors per block device"
51	depends on MMC_BLOCK
52	range 4 256
53	default 8
54	help
55	  Number of minors per block device. One is needed for every
56	  partition on the disk (plus one for the whole disk).
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
57
58	  Number of total MMC minors available is 256, so your number
59	  of supported block devices will be limited to 256 divided
60	  by this number.
61
62	  Default is 8 to be backwards compatible with previous
63	  hardwired device numbering.
64
65	  If unsure, say 8 here.
66
67config SDIO_UART
68	tristate "SDIO UART/GPS class support"
69	depends on TTY
70	help
71	  SDIO function driver for SDIO cards that implements the UART
72	  class, as well as the GPS class which appears like a UART.
73
74config MMC_TEST
75	tristate "MMC host test driver"
76	help
77	  Development driver that performs a series of reads and writes
78	  to a memory card in order to expose certain well known bugs
79	  in host controllers. The tests are executed by writing to the
80	  "test" file in debugfs under each card. Note that whatever is
81	  on your card will be overwritten by these tests.
82
83	  This driver is only of interest to those developing or
84	  testing a host driver. Most people should say N here.
85
86config MMC_CRYPTO
87	bool "MMC Crypto Engine Support"
88	depends on BLK_INLINE_ENCRYPTION
89	help
90	  Enable Crypto Engine Support in MMC.
91	  Enabling this makes it possible for the kernel to use the crypto
92	  capabilities of the MMC device (if present) to perform crypto
93	  operations on data being transferred to/from the device.