From mboxrd@z Thu Jan 1 00:00:00 1970 From: tony@atomide.com (Tony Lindgren) Date: Wed, 6 Jan 2016 10:26:50 -0800 Subject: [PATCH 2/2] memory: omap-gpmc: Add Kconfig option for debug In-Reply-To: <568D5669.4040801@gmail.com> References: <20160104170206.GC12777@atomide.com> <201601041834.56056@pali> <20160104174001.GD12777@atomide.com> <568AC0F9.2010304@gmail.com> <20160105041356.GE12777@atomide.com> <20160105084947.GG22661@pali> <20160105224929.GF12777@atomide.com> <20160106174039.GA14271@earth> <20160106174713.GL12777@atomide.com> <568D5669.4040801@gmail.com> Message-ID: <20160106182650.GM12777@atomide.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org * Ivaylo Dimitrov [160106 10:01]: > > Unfortunately, it seems there is more to be fixed. It booted several times > to the userspace, but after a couple of shutdowns, rootfs became corrupted > again. I flashed, installed linux 4.4, but the same happened after the first > shutdown with 4.4: 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. Also, do things now work reliably for you with CONFIG_OMAP_GPMC_DEBUG enabled? Or does that also produce corruption after few reboots? Regards, Tony 8< -------------- --- 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; }