[PATCH] mtd: nand: mxs: reset BCH earlier to avoid NAND startup problems
s.hauer at pengutronix.de
Wed Dec 5 13:50:36 EST 2012
On Wed, Dec 05, 2012 at 07:42:10PM +0100, Wolfram Sang wrote:
> On Wed, Dec 05, 2012 at 07:37:32PM +0100, Sascha Hauer wrote:
> > On Wed, Dec 05, 2012 at 03:53:53PM +0100, Wolfram Sang wrote:
> > > It could happen (1 out of 100 times) that NAND did not start up
> > > correctly after warm rebooting, so barebox could not find its
> > > environment or DMA timed out due to a stalled BCH. When resetting BCH
> > > together with GPMI, the issue could not be observed anymore. We probably
> > > need the consistent state already before sending commands to NAND.
> > The subject suggests that the BCH engine is resetted earlier, but
> > instead of moving the reset this patch adds another reset. Is this
> > intended?
> Yes, I wanted to keep resetting BCH before applying a new layout. Maybe
> the subject should have been named "earlier, too,". I can drop the other
> check and rerun my tests if this seems overcautios to you.
change the patch or the subject, either way is fine with me.
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
More information about the barebox