From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mtd: mxc_nand: Fix crash after MTD resync
Date: Tue, 2 Jul 2013 23:11:32 +0200 [thread overview]
Message-ID: <201307022311.32450.marex@denx.de> (raw)
In-Reply-To: <1372798952.8183.119@snotra>
Dear Scott Wood,
> On 07/02/2013 03:57:58 PM, Marek Vasut wrote:
> > Dear Scott Wood,
> >
> > > On 07/02/2013 10:11:55 AM, Marek Vasut wrote:
> > > > The driver triggered a BUG() in nand_base.c:3214/nand_scan_tail()
> > > > because the ecc.strength was incorrectly set in case of
> >
> > NAND_ECC_HW
> >
> > > > instead of NAND_ECC_HW_SYNDROME ECC mode.
> > > >
> > > > Signed-off-by: Marek Vasut <marex@denx.de>
> > > > Cc: Beno?t Th?baudeau <benoit.thebaudeau@advansee.com>
> > > > Cc: Fabio Estevam <fabio.estevam@freescale.com>
> > > > Cc: Scott Wood <scottwood@freescale.com>
> > > > ---
> > > >
> > > > drivers/mtd/nand/mxc_nand.c | 7 ++-----
> > > > 1 file changed, 2 insertions(+), 5 deletions(-)
> > > >
> > > > diff --git a/drivers/mtd/nand/mxc_nand.c
> >
> > b/drivers/mtd/nand/mxc_nand.c
> >
> > > > index ac435f2..08c7b8b 100644
> > > > --- a/drivers/mtd/nand/mxc_nand.c
> > > > +++ b/drivers/mtd/nand/mxc_nand.c
> > > > @@ -1238,15 +1238,12 @@ int board_nand_init(struct nand_chip
> >
> > *this)
> >
> > > > this->ecc.write_oob = mxc_nand_write_oob_syndrome;
> > > > this->ecc.bytes = 9;
> > > > this->ecc.prepad = 7;
> > > >
> > > > - } else {
> > > > - this->ecc.mode = NAND_ECC_HW;
> > > > - }
> > > > -
> > > > - if (this->ecc.mode == NAND_ECC_HW) {
> > > >
> > > > if (is_mxc_nfc_1())
> > > >
> > > > this->ecc.strength = 1;
> > > >
> > > > else
> > > >
> > > > this->ecc.strength = 4;
> > > >
> > > > + } else {
> > > > + this->ecc.mode = NAND_ECC_HW;
> > > >
> > > > }
> > >
> > > Where does ecc.strength now get set for the non-SYNDROME case?
> >
> > Gone ;-) The strength only needs to be set for the SYNDROME case
> > according to
> > the code in nand_base.c .
>
> Read it again. Note the lack of a "break;" before "case
> NAND_ECC_HW_SYNDROME:".
Blargh. V2-time.
Best regards,
Marek Vasut
prev parent reply other threads:[~2013-07-02 21:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 15:11 [U-Boot] [PATCH] mtd: mxc_nand: Fix crash after MTD resync Marek Vasut
2013-07-02 19:13 ` Scott Wood
2013-07-02 20:57 ` Marek Vasut
2013-07-02 21:02 ` Scott Wood
2013-07-02 21:11 ` Marek Vasut [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=201307022311.32450.marex@denx.de \
--to=marex@denx.de \
--cc=u-boot@lists.denx.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