Hi again. Thank you for your response Ulf. I am going to start over though since I did not get everything right the first time. As stated I am running the 4.1.5 Linux kernel and what I am actually using is a SD card. The host driver is sdhci-esdhc-imx.c. And my initial issue was that on resume I get the following: [ 31.848397] mmc0: card never left busy state [ 31.848412] mmc0: error -110 during resume (card was removed?) [ 31.848550] PM: resume of devices complete after 2062.936 msecs [ 31.931086] PM: Finishing wakeup. [ 31.931102] Restarting tasks ... done. [ 31.954336] mmc0: card dade removed [ 32.358711] mmc0: host does not support reading read-only switch, assuming write-enable [ 32.391857] mmc0: new SD card at address aaaa [ 32.418228] mmcblk0: mmc0:aaaa SU02G 1.84 GiB [ 32.446402] mmcblk0: p1 [ 32.835907] EXT4-fs (mmcblk0p1): recovery complete [ 32.840873] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data mode. Opts: (null) And that was the reason of my initial questions on what is supposed to happen when suspending. The card IS actually "removed" when in suspended state since we cut the power-rail completely to the SD card. I assume that this is a sdhci-esdhc-imx issue, but then I wonder what would be a proper fix for this. As stated before I get around this problem by adding a HACK to force removal of the SD card before suspending in mmc_pm_notify. Sorry if I am spamming but I am trying to learn :). Best Regards Mirza Krak -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
