From: Wolfram Sang <w.sang@pengutronix.de>
To: Huang Shijie <b32955@freescale.com>
Cc: baruch@tkos.co.il, koen.beel.barco@gmail.com,
marek.vasut@gmail.com, linux-mtd@lists.infradead.org,
Artem.Bityutskiy@intel.com, 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: Sat, 31 Dec 2011 16:43:38 +0100 [thread overview]
Message-ID: <20111231154338.GA27544@pengutronix.de> (raw)
In-Reply-To: <4EFE7236.10609@freescale.com>
[-- Attachment #1: Type: text/plain, Size: 1767 bytes --]
Hi,
On Sat, Dec 31, 2011 at 10:23:50AM +0800, Huang Shijie wrote:
> > 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?
> In one customer's 3G router which uses the MX28:
> [0] NAND boot mode, mount the UBIFS in the NAND partition.
> [1] We used the gpmi_reset_block(r->bch_regs, true) to init the BCH module.
> [2] The board will automatically reboot again after it booted by NAND
> boot mode.
> [3] After reboot more then thousands times(cost nearly one day), the BCH
> mode became UNSTABLE,
> the data read out was not right, so the system could not mount the UBIFS.
>
> After we use gpmi_reset_block(r->bch_regs, false) to init the BCH
> module, the bug never happens.
Yes, I undestood that. I was curious _why_ this happens, for example, because
of a bug in the rom-code or such. This would then lead to the question if this
can be fixed by some other means. Because currently it looks like this to me:
If you would do the above scenario of booting 10000 times on a MX23, then BCH
could enter the same unstable state (can it?). Since we cannot reset BCH due to
bug 2847, we have a serious problem, because NAND won't work until the next
power-cycle? I am curious if my assumptions are true and we have a serious
problem on the MX23.
> Yes, this is the bug 2847 from the mx23's errata.
OK, thanks.
Kind regards,
Wolfram
--
Pengutronix e.K. | Wolfram Sang |
Industrial Linux Solutions | http://www.pengutronix.de/ |
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
WARNING: multiple messages have this Message-ID (diff)
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: Sat, 31 Dec 2011 16:43:38 +0100 [thread overview]
Message-ID: <20111231154338.GA27544@pengutronix.de> (raw)
In-Reply-To: <4EFE7236.10609@freescale.com>
Hi,
On Sat, Dec 31, 2011 at 10:23:50AM +0800, Huang Shijie wrote:
> > 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?
> In one customer's 3G router which uses the MX28:
> [0] NAND boot mode, mount the UBIFS in the NAND partition.
> [1] We used the gpmi_reset_block(r->bch_regs, true) to init the BCH module.
> [2] The board will automatically reboot again after it booted by NAND
> boot mode.
> [3] After reboot more then thousands times(cost nearly one day), the BCH
> mode became UNSTABLE,
> the data read out was not right, so the system could not mount the UBIFS.
>
> After we use gpmi_reset_block(r->bch_regs, false) to init the BCH
> module, the bug never happens.
Yes, I undestood that. I was curious _why_ this happens, for example, because
of a bug in the rom-code or such. This would then lead to the question if this
can be fixed by some other means. Because currently it looks like this to me:
If you would do the above scenario of booting 10000 times on a MX23, then BCH
could enter the same unstable state (can it?). Since we cannot reset BCH due to
bug 2847, we have a serious problem, because NAND won't work until the next
power-cycle? I am curious if my assumptions are true and we have a serious
problem on the MX23.
> Yes, this is the bug 2847 from the mx23's errata.
OK, thanks.
Kind 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/20111231/dda562e2/attachment-0001.sig>
next prev parent reply other threads:[~2011-12-31 15:44 UTC|newest]
Thread overview: 26+ 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 8:27 ` Huang Shijie
2011-12-30 14:01 ` Marek Vasut
2011-12-30 14:01 ` Marek Vasut
2011-12-30 14:36 ` Wolfram Sang
2011-12-30 14:36 ` Wolfram Sang
2011-12-31 2:23 ` Huang Shijie
2011-12-31 2:23 ` Huang Shijie
2011-12-31 3:15 ` Marek Vasut
2011-12-31 3:15 ` Marek Vasut
2011-12-31 3:31 ` Huang Shijie
2011-12-31 3:31 ` Huang Shijie
2011-12-31 4:45 ` Marek Vasut
2011-12-31 4:45 ` Marek Vasut
2011-12-31 15:43 ` Wolfram Sang [this message]
2011-12-31 15:43 ` Wolfram Sang
2012-01-01 15:23 ` Huang Shijie
2012-01-01 15:23 ` Huang Shijie
2012-01-01 22:33 ` Wolfram Sang
2012-01-01 22:33 ` Wolfram Sang
2012-01-03 2:30 ` Huang Shijie
2012-01-03 2:30 ` Huang Shijie
2012-01-03 11:11 ` Wolfram Sang
2012-01-03 11:11 ` Wolfram Sang
2012-01-04 2:43 ` Huang Shijie
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=20111231154338.GA27544@pengutronix.de \
--to=w.sang@pengutronix.de \
--cc=Artem.Bityutskiy@intel.com \
--cc=LW@KARO-electronics.de \
--cc=b32955@freescale.com \
--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 \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.