>-----Original Message----- > >Richard, > >"Woodruff, Richard" <[email protected]> writes: > >>> I wait for a min and try to wakeup - It works. >>> >>> If i wait a little longer before waking it up say, 3 or 4 minutes. >>> It does not wakeup. >> >> That is consistent with your memory not being placed into self refresh >> properly. >> >> 5 general bugs I've seen over time: >> sw bug: >> - ctrl sequence issue before sleep >> - CKE balls not muxed correctly >> - crash on unexpected wake path >> chip bug: >> - (3430 >= es3 requires a errata sequence to work) >> board bug: >> - hooking ddr-chip-CKE wrongly or a way OMAP doesn't support >> like sharing between >dies. > >Another possibility is that the the memory timings for the custom >board are not set correctly. > >Richard, Do you have pointers to CDP/zoom code that has a workaround >for the 3430 > es3 errata as well as the 'ctrl sequence issue' you >mentioned?
Richard, All the fixes should be available on [1] Time to Market Branch: ti-2.6.24-omap3 You could point patches from there if required. [1] http://git.omapzoom.com/?p=omapkernel.git;a=shortlog;h=refs/heads/ti-2.6.24-omap3 > >Kevin > > > -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
