From: b32955@freescale.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] mtd: nand: gpmi: reset BCH earlier, too, to avoid NAND startup problems
Date: Thu, 6 Dec 2012 10:16:08 +0800 [thread overview]
Message-ID: <50BFFFE8.8040002@freescale.com> (raw)
In-Reply-To: <1354740362-20412-1-git-send-email-w.sang@pengutronix.de>
? 2012?12?06? 04:46, Wolfram Sang ??:
> correctly after warm rebooting, so the kernel could not find the UBI or
which Soc do you meet this issue? the mx23 or mx28?
It's bad news to me. I ever thought the BCH-reset-issue is gone.
I ever tested many times in mx28(> 10000 times) with freescale's uboot.
I guest you are not use the freescale's uboot. The uboot also will reset
the BCH/GPMI.
thanks
Huang Shijie
next prev parent reply other threads:[~2012-12-06 2:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-05 20:46 [PATCH] mtd: nand: gpmi: reset BCH earlier, too, to avoid NAND startup problems Wolfram Sang
2012-12-06 2:16 ` Huang Shijie [this message]
2012-12-06 9:52 ` Wolfram Sang
2012-12-06 14:58 ` Huang Shijie
2012-12-06 16:58 ` Wolfram Sang
2012-12-11 2:01 ` Huang Shijie
2012-12-12 15:11 ` Artem Bityutskiy
2012-12-12 16:01 ` Wolfram Sang
2012-12-13 11:41 ` Artem Bityutskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=50BFFFE8.8040002@freescale.com \
--to=b32955@freescale.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).