Hi Tomi, On 5/5/2011 5:59 PM, Valkeinen, Tomi wrote:
Hi Paul, Benoit, I've started testing pm runtime with DSS, and I encountered a problem. I'm using latest -rc5 as a base, and it looks like omap_hwmod:_wait_target_ready() does not succeed for dss_core hwmod. This causes _enable() to fail, but omap_device_enable_hwmods() does not check the return values so it looks like everything went well, until the driver crashes as the DSS HW module was off. Ideas about _wait_target_ready()? And omap_device_enable_hwmods() would need some fixing, I wasted quite a while debugging this =).
The wait_target_ready is waiting for the PRCM status. It the status does not change, it is probably because some inputs clocks... like the optional ones are not enabled.
In your case, you have to enable the DSS fck before calling into PM runtime because hwmod does mark this clock as optional:-(
Regards, Benoit -- 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
