On Thu, 2 Feb 2012, Shilimkar, Santosh wrote: > Yes, we do have issue with below APIs for OMAP4 and onwards design > because of the PRCM change. > > pwrdm_clear_all_prev_pwrst > pwrdm_*_mem_* > > There use to be a single power state and memory state register till OMAP3 > at power domain level which can give you the logic and memory last test > which is needed for OSWR. > > On OMAP4, we have registers per modules and it becomes difficult to model > this difference in APIs. Initially we tried to fix that with [1] and > then later realized > that's not going to work on OMAP4 + devices because of mentioned issue. If the registers are per-module, it seems like the best place for those would be the hwmod layer. Do you think that makes sense? So, something like omap_hwmod_clear_all_prev_pwrst(), etc.? Seems like that should be pretty efficient. - Paul -- 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
