Message ID | 20160205061021.GS19432@atomide.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
On 5.02.2016 08:10, Tony Lindgren wrote: > This seems to fix things here for legacy booting and booting the > maemo zImage after dts image. Care to give it a try? > > Basically onenand after reset is in wrong state, have not looked > up the bits yet. Will post a better patch when I get a chance > over next few days. > > Regards, > > Tony Yep, that looks to fix the things, I submitted a patch "[PATCH] ARM: OMAP2+: Fix onenand initialization to avoid filesystem corruption" (it was supposed to be a reply to this mail, but my git-send-mail-fu failed on me as always :) ) Thanks, Ivo -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
--- a/arch/arm/mach-omap2/gpmc-onenand.c +++ b/arch/arm/mach-omap2/gpmc-onenand.c @@ -104,6 +104,7 @@ static void set_onenand_cfg(void __iomem *onenand_base) u32 reg; reg = readw(onenand_base + ONENAND_REG_SYS_CFG1); + reg = 0x06c0; reg &= ~((0x7 << ONENAND_SYS_CFG1_BRL_SHIFT) | (0x7 << 9)); reg |= (latency << ONENAND_SYS_CFG1_BRL_SHIFT) | ONENAND_SYS_CFG1_BL_16; @@ -289,6 +290,7 @@ static int omap2_onenand_setup_async(void __iomem *onenand_base) } } + onenand_async.sync_write = true; omap2_onenand_calc_async_timings(&t); ret = gpmc_cs_program_settings(gpmc_onenand_data->cs, &onenand_async);