Hi, Am Fri, 7 Mar 2025 08:42:02 -0600 schrieb Robert Nelson <robertcnelson@xxxxxxxxx>: > On Thu, Mar 6, 2025 at 10:28 PM Tony Lindgren <tony@xxxxxxxxxxx> wrote: > > > > Best to revert the patch first until the issue has been fixed. > > > > Based on the symptoms, it sounds like there might be a missing flush of > > a posted write in the PM runtime suspend/resume path. This could cause > > something in the sequence happen in the wrong order for some of the > > related surrounding resources like power, clocks or interrupts. > > > > Kington's hardware anaylizer said after CMD5/sleep in about 10us, > instead of CMD5/wkup being called, it just resets the eMMC.. So > someone deep within the sdhc/mmc layer might understand that. ;) > hmm, omap3/4/5 are using omap-hsmmc and are not switched towards sdhci yet. So I guess that might be the reason why things are not coming to light that easy. Also I am wondering whether we can start by destroying SD cards rather then eMMC. So maybe we can do some stress-testing to have the cycles shorter. Do we have an overview what is really working reliable with that driver? Regards, Andreas
