xref: /linux/drivers/mmc/core/Kconfig (revision 6abaa0c9fec563538f2a28a682af8c89bb9b125c)
1*6abaa0c9SPierre Ossman#
2*6abaa0c9SPierre Ossman# MMC core configuration
3*6abaa0c9SPierre Ossman#
4*6abaa0c9SPierre Ossman
5*6abaa0c9SPierre Ossmanconfig MMC_UNSAFE_RESUME
6*6abaa0c9SPierre Ossman	bool "Allow unsafe resume (DANGEROUS)"
7*6abaa0c9SPierre Ossman	depends on MMC != n
8*6abaa0c9SPierre Ossman	help
9*6abaa0c9SPierre Ossman	  If you say Y here, the MMC layer will assume that all cards
10*6abaa0c9SPierre Ossman	  stayed in their respective slots during the suspend. The
11*6abaa0c9SPierre Ossman	  normal behaviour is to remove them at suspend and
12*6abaa0c9SPierre Ossman	  redetecting them at resume. Breaking this assumption will
13*6abaa0c9SPierre Ossman	  in most cases result in data corruption.
14*6abaa0c9SPierre Ossman
15*6abaa0c9SPierre Ossman	  This option is usually just for embedded systems which use
16*6abaa0c9SPierre Ossman	  a MMC/SD card for rootfs. Most people should say N here.
17*6abaa0c9SPierre Ossman
18