On 06/05/14 06:15, Andrew LeCain wrote: > 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: That is probably some custom kernel, as mainline 2.6.32 didn't even have omapdss driver. > 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. Hmm. I think the "dss_clkdm->dss_pwrdm (0)" says that there are no users with references dss_pwrdm. So it sounds to me all the clocks etc are properly off, but the platform code does not turn the dss powerdomain off for some reason. Tomi
Attachment:
signature.asc
Description: OpenPGP digital signature
