summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDeepesh Gujarathi <dgujarathi@nvidia.com>2010-03-31 13:25:48 +0530
committerGary King <gking@nvidia.com>2010-04-01 18:05:40 -0800
commit75bcb77344c4f242f595107d7b89e6a316ac0690 (patch)
tree0b792b7d1ce67f4e16e2c0881bfad5ea9633e9c8
parentccbaa3ec2afb825c315d11e34b30faffa10c199e (diff)
tegra mmc: enable MMC_UNSAFE_RESUME config for tegra_whistler_gnu_linux
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: Ibc1511c5feb0391dc644df2d710e386ec0d353ce Reviewed-on: http://git-master/r/994 Reviewed-by: Bharat Nihalani <bnihalani@nvidia.com> Reviewed-by: Gary King <gking@nvidia.com> Tested-by: Gary King <gking@nvidia.com>
-rw-r--r--arch/arm/configs/tegra_whistler_gnu_linux_defconfig2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm/configs/tegra_whistler_gnu_linux_defconfig b/arch/arm/configs/tegra_whistler_gnu_linux_defconfig
index 04d850c05414..3d4cb97c8540 100644
--- a/arch/arm/configs/tegra_whistler_gnu_linux_defconfig
+++ b/arch/arm/configs/tegra_whistler_gnu_linux_defconfig
@@ -1230,7 +1230,7 @@ CONFIG_UDC_FSL_NR_ENDPOINTS=32
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