This is a known issue just like removable USB disk.
Actually SD/MMC driver has provided a solution. There is a "dangerous" kernel option CONFIG_MMC_UNSAFE_RESUME to fix this issue. It depends the customers to chose whether to enable this option.
I attached the option's description here:
config MMC_UNSAFE_RESUME
bool "Allow unsafe resume (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 is a known issue just like removable USB disk.
Actually SD/MMC driver has provided a solution. There is a "dangerous" kernel option CONFIG_ MMC_UNSAFE_ RESUME to fix this issue. It depends the customers to chose whether to enable this option.
I attached the option's description here:
config MMC_UNSAFE_RESUME
redetecting them at resume. Breaking this assumption will
bool "Allow unsafe resume (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
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.