Kevin Hilman <khilman@xxxxxxxxxxxxxxxxxxx> writes: > Richard, > > "Woodruff, Richard" <r-woodruff2@xxxxxx> 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. > Also, as another reference point: I do not see this behavior on some other custom ES3-based hardware using the PM branch. So that suggests some board-specific issues are involved. Kevin -- 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
