From: w.sang@pengutronix.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] MTD/GPMI bugfix : reset the BCH module when it is not MX23
Date: Fri, 30 Dec 2011 15:36:58 +0100 [thread overview]
Message-ID: <20111230143658.GA9141@pengutronix.de> (raw)
In-Reply-To: <1325233646-3343-1-git-send-email-b32955@freescale.com>
On Fri, Dec 30, 2011 at 04:27:26PM +0800, Huang Shijie wrote:
> In MX28, if we do not reset the BCH module. The BCH module may
> becomes unstable when the board reboots for several thousands times.
Do you have more details when and why this happens? What happens on MX23 then?
> Signed-off-by: Huang Shijie <b32955@freescale.com>
Is this Bug 2847 from the errata? Should be mentioned in the commit message and
comments of the patch if so.
Regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20111230/424847b3/attachment.sig>
next prev parent reply other threads:[~2011-12-30 14:36 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 [this message]
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
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=20111230143658.GA9141@pengutronix.de \
--to=w.sang@pengutronix.de \
--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).