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 || BT_MRVL_SDIO || LIBERTAS_SDIO)
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	default y
41	help
42	  Say Y here to enable the MMC block device driver support.
43	  This provides a block device driver, which you can use to
44	  mount the filesystem. Almost everyone wishing MMC support
45	  should say Y or M here.
46
47config MMC_BLOCK_MINORS
48	int "Number of minors per block device"
49	depends on MMC_BLOCK
50	range 4 256
51	default 8
52	help
53	  Number of minors per block device. One is needed for every
54	  partition on the disk (plus one for the whole disk).
55
56	  Number of total MMC minors available is 256, so your number
57	  of supported block devices will be limited to 256 divided
58	  by this number.
59
60	  Default is 8 to be backwards compatible with previous
61	  hardwired device numbering.
62
63	  If unsure, say 8 here.
64
65config SDIO_UART
66	tristate "SDIO UART/GPS class support"
67	depends on TTY
68	help
69	  SDIO function driver for SDIO cards that implements the UART
70	  class, as well as the GPS class which appears like a UART.
71
72config MMC_TEST
73	tristate "MMC host test driver"
74	help
75	  Development driver that performs a series of reads and writes
76	  to a memory card in order to expose certain well known bugs
77	  in host controllers. The tests are executed by writing to the
78	  "test" file in debugfs under each card. Note that whatever is
79	  on your card will be overwritten by these tests.
80
81	  This driver is only of interest to those developing or
82	  testing a host driver. Most people should say N here.
83