summaryrefslogtreecommitdiff
path: root/tools/kernel-doc/Makefile
diff options
context:
space:
mode:
authorWolfram Sang <w.sang@pengutronix.de>2012-12-05 10:48:47 +0000
committerScott Wood <scottwood@freescale.com>2012-12-11 17:19:51 -0600
commit0b38fffbe413fc0725c750d046ca62c23fca196e (patch)
tree68d0306b85da9aceea263dc5c47aa0ed56076108 /tools/kernel-doc/Makefile
parentea40a05422bdc87a7af5dc349e8adce59f982e72 (diff)
downloadu-boot-imx-0b38fffbe413fc0725c750d046ca62c23fca196e.zip
u-boot-imx-0b38fffbe413fc0725c750d046ca62c23fca196e.tar.gz
u-boot-imx-0b38fffbe413fc0725c750d046ca62c23fca196e.tar.bz2
mtd: nand: mxs: reset BCH earlier, too, to avoid NAND startup problems
It could happen (1 out of 100 times) that NAND did not start up correctly after warm rebooting, so we end up with various failures or DMA timed out due to a stalled BCH. When resetting BCH together with GPMI, the issue could not be observed anymore (after 10000+ reboots). We probably need the consistent state already before sending commands to NAND. This behaviour was observed in barebox and kernel, so I assume it affects U-Boot as well. I chose to keep the extra reset for BCH when changing the flash layout to be on the safe side. Signed-off-by: Wolfram Sang <w.sang@pengutronix.de> Acked-by: Marek Vasut <marex@denx.de>
Diffstat (limited to 'tools/kernel-doc/Makefile')
0 files changed, 0 insertions, 0 deletions