PM regression in next
From: tony@atomide.com (Tony Lindgren)
Date: 2018-01-12 14:15:01
Also in:
linux-omap, linux-pm, lkml
From: tony@atomide.com (Tony Lindgren)
Date: 2018-01-12 14:15:01
Also in:
linux-omap, linux-pm, lkml
* Andrew Lunn [off-list ref] [180112 13:55]:
quoted
Thanks that fixes the suspend error. And I was able to confirm that the suspend power consumption is OK. That still leaves the mystery of the runtime idle power consumption being much higher with commit e130bc1d00a4.Did you re-measure the runtime power? Do you have an unused PHY? It could be it is not getting shut down. 1G PHYs can be quite power hungry.
Yes this is a different issue, the increase in runtime PM consumption measurement I'm measuring is for a SoM board. It contains the SoC + memory + PMIC and few devices. The Ethernet controller is on a separate optional base board and not related to the runtime PM issue. Regards, Tony