Hi Kevin,
On 2/4/09, Kevin Hilman <khil...@deeprootsystems.com> wrote: > Ramesh Gupta Guntha <grgupt...@gmail.com> writes: > > > Kevin, > > > > > > On 2/4/09, Kevin Hilman <khil...@deeprootsystems.com> wrote: > >> Ramesh Gupta Guntha <grgupt...@gmail.com> writes: > >> > >> > Hi, > >> > > >> > I am able to resolve all other issues with this pm branch except one > >> > issue, > >> > > >> > I am not able to enable the iva2 clock once system is suspended and > >> > resumed, I am getting below messages. > >> >> > >> >> <3>clock: dpll2_ck failed transition to 'locked' > >> >> clock: dpll2_ck failed transition to 'locked' > >> >> <3>clock: dpll2_ck failed transition to 'locked' > >> >> clock: dpll2_ck failed transition to 'locked' > >> > > >> > Once after booting ( without adding bridgedriver/ installing > >> > bridgedriver) > >> > CM_CLKEN_PLL_IVA2 value shows as 0x37 indicates IVA2 DPLL in locked mode. > >> > > >> > once after system suspend the value is not restored I am seeing that as > >> > 0x11 indicates IVA2 DPLL is low power stop mode. > >> > > >> > Can any one please provide your inputs on the above error? I tried > >> > reconfiguring the CM_CLKEN_PLL_IVA2 to lock mode but still I am seeing > >> > the same messages as above while enabling iva2 clock. > >> > >> Are you suspending into retention or off-mode? > > > > I am suspending into Off mode. > > > > Do you see this problem when only going into retention? > > If not, sounds like we're missing some registers being saved/restored > across off-mode. I am seeing this issue only with OFF mode , retention works fine for me, yeah, looks like some registers are not restored properly across off mode. please let me know your inputs on this. -- Thanks Ramesh Gupta G -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
