Hi Vikram, I am now looking at the android-omap-2.6.29 branch, and after having looked at the zoom2_defconfig file, I notice that power management is not enabled in the zoom2_defconfg file. Do you know if anyone managed to get a working PM implementation for android-2.6.29 for TI OMAP 3503/3430? I adapted the zoom2 settings for my overo android-2.6.29 build, and find that the system doesn't go to suspend mode at all. :-) So, while DSS2 and OMAP-PM have been integrated into the android-omap-2.6.29 branch, am I correct in concluding that power management suspend has not yet been implemented for android on TI OMAP 3503/3430? For example, here is a snippet from the zoom2_defconfig that shows pm suspend not being enabled. Because of this android cannot suspend and blank the screen after a period of inactivity: # # OMAP Feature Selections # # CONFIG_OMAP_DEBUG_POWERDOMAIN is not set # CONFIG_OMAP_DEBUG_CLOCKDOMAIN is not set # CONFIG_OMAP_SMARTREFLEX is not set # CONFIG_OMAP_RESET_CLOCKS is not set # CONFIG_OMAP_PM_NONE is not set CONFIG_OMAP_PM_NOOP=y # CONFIG_OMAP_PM_SRF is not set Even CPU power management is disabled: # # CPU Power Management # # CONFIG_CPU_FREQ is not set # CONFIG_CPU_IDLE is not set As you can see suspend is disabled. # # Power management options # CONFIG_PM=y # CONFIG_PM_DEBUG is not set # CONFIG_SUSPEND is not set CONFIG_HAS_WAKELOCK=y CONFIG_HAS_EARLYSUSPEND=y CONFIG_WAKELOCK=y CONFIG_WAKELOCK_STAT=y CONFIG_USER_WAKELOCK=y CONFIG_EARLYSUSPEND=y # CONFIG_NO_USER_SPACE_SCREEN_ACCESS_CONTROL is not set # CONFIG_CONSOLE_EARLYSUSPEND is not set CONFIG_FB_EARLYSUSPEND=y # CONFIG_APM_EMULATION is not set CONFIG_ARCH_SUSPEND_POSSIBLE=y CONFIG_NET=y Best regards, Elvis -- 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