Message ID | 20160106182650.GM12777@atomide.com (mailing list archive) |
---|---|
State | New, archived |
Headers | show |
Hi, On 6.01.2016 20:26, Tony Lindgren wrote: > > Hmm. Care to verify that your onenand really gets detected at 83 MHz like > your earlier logs show? Below is a patch that should show it. before the corruption appeared, I looked a couple of times in syslog and the freq there was 83MHz. Including after I disabled CONFIG_OMAP_GPMC_DEBUG. > > Also, do things now work reliably for you with CONFIG_OMAP_GPMC_DEBUG > enabled? Or does that also produce corruption after few reboots? CONFIG_OMAP_GPMC_DEBUG is disabled, shall I enable it? > --- a/arch/arm/mach-omap2/gpmc-onenand.c > +++ b/arch/arm/mach-omap2/gpmc-onenand.c > @@ -153,6 +153,8 @@ static int omap2_onenand_get_freq(struct omap_onenand_platform_data *cfg, > freq = 0; > } > > + pr_info("onenand rate detected: %i\n", freq); > + > return freq; > } > Where am I supposed to get the output from ^^^ if rootfs become corrupted? The problem appears after poweroff/restart when it is already too late to get the syslog. BTW, did you compare all the GPMC registers with and without HWMOD_INIT_NO_RESET? Regards, 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 @@ -153,6 +153,8 @@ static int omap2_onenand_get_freq(struct omap_onenand_platform_data *cfg, freq = 0; } + pr_info("onenand rate detected: %i\n", freq); + return freq; }