Thread (2 messages) flat view 2 messages, 2 authors, 2011-02-11
STALE5656d

Revision v2 of 7 in this series.

Revisions (7)
  1. v2 current
  2. v4 [diff vs current]
  3. v4 [diff vs current]
  4. v4 [diff vs current]
  5. v5 [diff vs current]
  6. v5 [diff vs current]
  7. v5 [diff vs current]

[PATCH v2 0/5] ARM: omap[34]: Thumb-2 compatibility fixes

From: Kevin Hilman <hidden>
Date: 2011-02-10 21:38:27
Also in: linux-omap

Santosh Shilimkar [off-list ref] writes:

[...]
quoted
The SD card gets suspended, but nothing else seems to happen, and I
can't resume the system.

Am I doing something wrong?
MMC suspend is broken. I use ramdisk-ext3 or NFS for my testing
Just to clarify, MMC suspend is not broken.  It's a "feature" the MMC
core.  See the help text of the following Kconfig option, and ensure
that it's enabled:


config MMC_UNSAFE_RESUME
	bool "Assume MMC/SD cards are non-removable (DANGEROUS)"
	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 option sets a default which can be overridden by the
	  module parameter "removable=0" or "removable=1".

Looking at Dave's .config, this option is disabled, so suspend will hang
when rootfs is on MMC.

Kevin
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help