On Mon, 28 Jul 2014, Tony Lindgren wrote: > Hmm I think the difference with the working v3.10 one is that you have > root=/dev/mmcblk0p2 instead of root=/dev/nfs. As the Ethernet on beagle > is on the USB EHCI, this is still blocking the deeper idle states AFAIK. Hmm? There's no Ethernet on the 3530 Beagle. The hardware configuration on those two boards - the 37xxevm and the 3530es3beagle - hasn't changed between the two test runs, AFAIK. Just to take the Beagle out of the equation, here's a test with the 37xxevm on 3.11 where it passes the dynamic idle tests: http://www.pwsan.com/omap/testlogs/test_v3.11/20130902150604/pm/37xxevm/37xxevm_log.txt And here's one on the 37xxevm on 3.16-rc7 where it fails: http://www.pwsan.com/omap/testlogs/test_v3.11/20130902150604/pm/37xxevm/37xxevm_log.txt I should probably read back those writes to autosuspend_delay_ms, just to make sure they are reaching the right destinations. But you might want to confirm that you can see the CORE RET count increasing during dynamic idle on your 37xxevm. - Paul -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
