summaryrefslogtreecommitdiff
path: root/include/linux/atmel-mci.h
diff options
context:
space:
mode:
authorBen Hutchings <ben@decadent.org.uk>2009-12-15 02:01:29 (GMT)
committerLinus Torvalds <torvalds@linux-foundation.org>2009-12-15 16:53:35 (GMT)
commitbd68e0838fe85794b06892054772fa013a8d1986 (patch)
treeadb0a3a1aad94f756b7d3d2f8e077877a0b982d0 /include/linux/atmel-mci.h
parentc78402e95dd8238ee2b0e6e62b9a0c8b2bb9bba9 (diff)
downloadlinux-fsl-qoriq-bd68e0838fe85794b06892054772fa013a8d1986.tar.xz
mmc: add module parameter to set whether cards are assumed removable
Some people run general-purpose distribution kernels on netbooks with a card that is physically non-removable or logically non-removable (e.g. used for /home) and cannot be cleanly unmounted during suspend. Add a module parameter to set whether cards are assumed removable or non-removable, with the default set by CONFIG_MMC_UNSAFE_RESUME. In general, it is not possible to tell whether a card present in an MMC slot after resume is the same that was there before suspend. So there are two possible behaviours, each of which will cause data loss in some cases: CONFIG_MMC_UNSAFE_RESUME=n (default): Cards are assumed to be removed during suspend. Any filesystem on them must be unmounted before suspend; otherwise, buffered writes will be lost. CONFIG_MMC_UNSAFE_RESUME=y: Cards are assumed to remain present during suspend. They must not be swapped during suspend; otherwise, buffered writes will be flushed to the wrong card. Currently the choice is made at compile time and this allows that to be overridden at module load time. Signed-off-by: Ben Hutchings <ben@decadent.org.uk> Cc: Wouter van Heyst <larstiq@larstiq.dyndns.org> Cc: <linux-mmc@vger.kernel.org> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/linux/atmel-mci.h')
0 files changed, 0 insertions, 0 deletions