> Thanks for testing. > > I'm able to reproduce the issue locally (using a kernel 6.1.112). > It fail after the first sleep 20... > > If I remove MMC_CAP_AGGRESSIVE_PM from the sdhci-omap driver the issue is gone. > > About sdhci-omap driver, It's one of the only few enabling > MMC_CAP_AGGRESSIVE_PM. I recently switched to a new project using a newer SoC > but the eMMC driver doesn't event set MMC_CAP_AGGRESSIVE_PM. > > I'm wondering if MMC_CAP_AGGRESSIVE_PM is really safe (or compatible) for > HS200/HS400 eMMC speed. Indeed, MMC_CAP_AGGRESSIVE_PM has been added to > sdhci-omap driver to support SDIO WLAN device PM [1]. > > I've found another similar report on the Beaglebone-black (AM335x SoC) [2]. > > It seems the MMC_CAP_AGGRESSIVE_PM feature should only be enabled to SDIO cards. We've been chasing this Bug in BeagleLand for a while. Had Kingston run it thru their hardware debuggers.. On the BBB, once the eMMC is suspended during idle, the proper 'wakeup' cmd is NOT sent over, instead it forces a full reset. Eventually this kills the eMMC. Been playing with this same revert for a day or so, with my personal setup, it takes 3-4 Weeks (at idle every day) for it to finally die.. So i won't be able to verify this 'really' fixes it till next month.. Regards, -- Robert Nelson https://rcn-ee.com/
