summaryrefslogtreecommitdiff
path: root/arch
diff options
context:
space:
mode:
authorDeepesh Gujarathi <dgujarathi@nvidia.com>2010-03-30 16:52:48 +0530
committerGary King <gking@nvidia.com>2010-03-30 14:56:23 -0800
commit15e601183b513960c1803389d274b2bfb7bc60f0 (patch)
tree849b0d47e9cc8903f9223bbfdbd0ab251f939ba1 /arch
parent71333b22622f28fa4f6e7593179d7d154d7cae83 (diff)
tegra mmc: enable MMC_UNSAFE_RESUME config for tegra_whistler_android
Normally, when the system goes into suspend, all the storage cards are removed and later re-enumerated upon resume. During re-enumeration the device name and number are not guaranteed to be the same as they were during bootup. This can cause issues if rootfs falls on one such device. When the MMC_UNSAFE_RESUME config is enabled, it will prevent kernel from unmounting the mmc cards before suspend. Upon resume the cards will still be using the same device id as they were before suspend. Change-Id: I2821b20bbd3ecb753bdc8c90297e41c396c66364 Reviewed-on: http://git-master/r/988 Reviewed-by: Mayuresh Kulkarni <mkulkarni@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> Tested-by: Gary King <gking@nvidia.com>
Diffstat (limited to 'arch')
-rw-r--r--arch/arm/configs/tegra_whistler_android_defconfig2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm/configs/tegra_whistler_android_defconfig b/arch/arm/configs/tegra_whistler_android_defconfig
index 748bf5143e55..3749b83faf52 100644
--- a/arch/arm/configs/tegra_whistler_android_defconfig
+++ b/arch/arm/configs/tegra_whistler_android_defconfig
@@ -1207,7 +1207,7 @@ CONFIG_USB_TEGRA_OTG=y
CONFIG_MMC=y
CONFIG_EMBEDDED_MMC_START_OFFSET=y
# CONFIG_MMC_DEBUG is not set
-# CONFIG_MMC_UNSAFE_RESUME is not set
+CONFIG_MMC_UNSAFE_RESUME=y
# CONFIG_MMC_EMBEDDED_SDIO is not set
# CONFIG_MMC_PARANOID_SD_INIT is not set