Hello Richard, On Fri, 19 Jun 2009, Woodruff, Richard wrote: > > From: Paul Walmsley [mailto:paul@xxxxxxxxx] > > Sent: Thursday, June 18, 2009 4:07 PM > > > On Wed, 17 Jun 2009, Woodruff, Richard wrote: > > > > > I've only seen the condition along side of very aggressive SDRC_POWER > > > settings. > > > > Could you send over the SDRC_POWER settings that cause this problem? > > This is one pulled for a custom board: > > # ./readmem 0x6d000070 > 0x000200AD Thanks. According to the 34xx TRM Table 11-178 this sets the following: (asterisks mark differences from the current linux-omap code base.) WAKEUPPROC = 0 * AUTOCOUNT = 0x200 * SRFRONRESET = 1 SRFRONIDLEREQ = 0 * CLKCTRL = 2 EXTCLKDIS = 1 PWDENA = 1 PAGEPOLICY = 1 Looks like the significant difference is the use of CLKCTRL = 0x2 (+ AUTOCOUNT). Maybe there is some SDRC bug related to CLKCTRL = 0x2 that causes this problem? Perhaps the problem is partially related to PWDENA = 1 and erratum 1.150? Anyway, will do a test run here with this SDRC_POWER register value and see if the problem reproduces. - 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
