From: Huang Shijie <b32955@freescale.com>
To: Wolfram Sang <w.sang@pengutronix.de>
Cc: baruch@tkos.co.il, koen.beel.barco@gmail.com,
marek.vasut@gmail.com, linux-mtd@lists.infradead.org,
Artem.Bityutskiy@intel.com, Huang Shijie <shijie8@gmail.com>,
linux-arm-kernel@lists.infradead.org, LW@karo-electronics.de
Subject: Re: [PATCH v2] MTD/GPMI bugfix : reset the BCH module when it is not MX23
Date: Wed, 4 Jan 2012 10:43:45 +0800 [thread overview]
Message-ID: <4F03BCE1.80006@freescale.com> (raw)
In-Reply-To: <20120103111114.GA9083@pengutronix.de>
hi,
> Due to Errata #2847 of the MX23, the BCH cannot be soft reset on this
> chip, otherwise it will lock up. So we skip resetting BCH on the MX23.
> On the other hand, the MX28 needs the reset, because one case has been
> seen where the BCH produced ECC errors constantly after 10000
> consecutive reboots. The latter case has not been seen on the MX23 yet,
> still we don't if it could happen there as well.
>
> ===
>
> What do you think?
>
ok, thanks. I will add this comment to the patch.
Huang Shijie
prev parent reply other threads:[~2012-01-04 2:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 8:27 [PATCH v2] MTD/GPMI bugfix : reset the BCH module when it is not MX23 Huang Shijie
2011-12-30 14:01 ` Marek Vasut
2011-12-30 14:36 ` Wolfram Sang
2011-12-31 2:23 ` Huang Shijie
2011-12-31 3:15 ` Marek Vasut
2011-12-31 3:31 ` Huang Shijie
2011-12-31 4:45 ` Marek Vasut
2011-12-31 15:43 ` Wolfram Sang
2012-01-01 15:23 ` Huang Shijie
2012-01-01 22:33 ` Wolfram Sang
2012-01-03 2:30 ` Huang Shijie
2012-01-03 11:11 ` Wolfram Sang
2012-01-04 2:43 ` Huang Shijie [this message]
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=4F03BCE1.80006@freescale.com \
--to=b32955@freescale.com \
--cc=Artem.Bityutskiy@intel.com \
--cc=LW@karo-electronics.de \
--cc=baruch@tkos.co.il \
--cc=koen.beel.barco@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=shijie8@gmail.com \
--cc=w.sang@pengutronix.de \
/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).