aboutsummaryrefslogtreecommitdiff
path: root/drivers/mmc/core/Kconfig
diff options
context:
space:
mode:
Diffstat (limited to 'drivers/mmc/core/Kconfig')
-rw-r--r--drivers/mmc/core/Kconfig17
1 files changed, 7 insertions, 10 deletions
diff --git a/drivers/mmc/core/Kconfig b/drivers/mmc/core/Kconfig
index ab37a6d9d32..9ebee72d9c3 100644
--- a/drivers/mmc/core/Kconfig
+++ b/drivers/mmc/core/Kconfig
@@ -2,15 +2,12 @@
# MMC core configuration
#
-config MMC_UNSAFE_RESUME
- bool "Allow unsafe resume (DANGEROUS)"
+config MMC_CLKGATE
+ bool "MMC host clock gating"
help
- If you say Y here, the MMC layer will assume that all cards
- stayed in their respective slots during the suspend. The
- normal behaviour is to remove them at suspend and
- redetecting them at resume. Breaking this assumption will
- in most cases result in data corruption.
-
- This option is usually just for embedded systems which use
- a MMC/SD card for rootfs. Most people should say N here.
+ This will attempt to aggressively gate the clock to the MMC card.
+ This is done to save power due to gating off the logic and bus
+ noise when the MMC card is not in use. Your host driver has to
+ support handling this in order for it to be of any use.
+ If unsure, say N.