Hi Jean, On Mon, 11 May 2009, Jean Pihet wrote: > On Saturday 09 May 2009 00:43:43 Paul Walmsley wrote: > > One possibility: perhaps the problem is with Beagle's pin mux settings. > > You might want to boot with mem=128M and make sure > > CONTROL_PADCONF_SAD2D_SBUSFLAG and CONTROL_PADCONF_SDRC_CKE1 are in mode 0 > > before suspend and after resume. > Yes that definitely is the root cause. I should have checked this first ;-( > The U-Boot change is committed, cf. > http://gitorious.org/u-boot-omap3/mainline/commit/c6f01ad390308800693c62dbdb096ab59e03630b > and > http://gitorious.org/u-boot-omap3/mainline/commit/4025cfbde3611b14c0d4831a5524e5e061128e30 Nice work! Sounds like we should also patch mach-omap2/sdrc.c:omap2_sdrc_init() to warn if the sdrc_cke1 pin mux is wrong if a second struct omap_sdrc_params * is passed. Probably board-omap3beagle.c should also remux the pad if it's wrong. Otherwise there will be a lot of unhappy Rev C BeagleBoard users. > I am looking at a fix for the SDRC setup with 2 CSes. I will propose the > changes asap. Excellent, thanks Jean. - 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
