Hi, I'm trying to backport a display driver for an RFBI panel to 2.6.32, but the dss_pwrdm is complaining about not entering target state:
root@02AA01AB381207S7# cat /sys/kernel/debug/pm_debug/count | grep dss dss_pwrdm (ON),OFF:0,RET:11,INA:0,ON:12 dss_clkdm->dss_pwrdm (0) root@02AA01AB381207S7# echo -n "mem" > /sys/power/state PM: Syncing filesystems ... done. PM: Preparing system for mem sleep Freezing user space processes ... (elapsed 0.02 seconds) done. Freezing remaining freezable tasks ... (elapsed 0.04 seconds) done. PM: Entering mem sleep spidev spi2.0: ... can't suspend WLAN: Suspend call WLAN_firmware Suspend Wake locks are active (count: 0) Shutting Down I&F Clock Interface Powerdomain (core_pwrdm) didn't enter target state 0 Powerdomain (dss_pwrdm) didn't enter target state 0 Could not enter target state in pm_suspend <snip> #no change after attempted suspend. root@02AA01AB381207S7# cat /sys/kernel/debug/pm_debug/count | grep dss dss_pwrdm (ON),OFF:0,RET:11,INA:0,ON:12 dss_clkdm->dss_pwrdm (0) I was worried it might be the dss clocks not being disabled, but I instrumented dss_clk_(en|dis)able to print clock counts and it goes to 0 before suspending. I don't really understand what will prevent the dss power domain from entering retain state or not, so any pointers would be useful. I'm less worried about the core_pwrdm error because that isn't a regression from the old panel, and power numbers are low enough without it, but any tips there would be great as well. Thanks -Andrew -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
