From: Boris Brezillon <boris.brezillon@bootlin.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Richard Weinberger <richard@nod.at>,
stable@vger.kernel.org, Peter Pan <peterpandong@micron.com>,
Marek Vasut <marek.vasut@gmail.com>,
linux-mtd@lists.infradead.org,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Bean Huo <beanhuo@micron.com>
Subject: Re: [PATCH] mtd: rawnand: micron: Fix support for on-die ECC
Date: Tue, 8 May 2018 23:12:59 +0200 [thread overview]
Message-ID: <20180508231259.10e951d4@bbrezillon> (raw)
In-Reply-To: <20180504115835.5702710e@xps13>
On Fri, 4 May 2018 11:58:35 +0200
Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> Hi Boris,
>
> On Thu, 3 May 2018 09:49:08 +0200, Boris Brezillon
> <boris.brezillon@bootlin.com> wrote:
>
> > It looks like the NAND_STATUS_FAIL bit is sticky after an ECC failure,
> > which leads all READ operations following the failing one to report
> > an ECC failure. Reset the chip to clear the NAND_STATUS_FAIL bit.
> >
> > Note that this behavior is not document in the datasheet, but resetting
> > the chip is the only solution we found to fix the problem.
> >
> > Fixes: 9748e1d87573 ("mtd: nand: add support for Micron on-die ECC")
> > Cc: <stable@vger.kernel.org>
> > Signed-off-by: Boris Brezillon <boris.brezillon@bootlin.com>
> > Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
> > Cc: Bean Huo <beanhuo@micron.com>
> > Cc: Peter Pan <peterpandong@micron.com>
> > ---
>
> Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
Queued to mtd/master.
next prev parent reply other threads:[~2018-05-08 21:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 7:49 [PATCH] mtd: rawnand: micron: Fix support for on-die ECC Boris Brezillon
2018-05-04 9:58 ` Miquel Raynal
2018-05-08 21:12 ` Boris Brezillon [this message]
2018-05-10 6:46 ` Boris Brezillon
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=20180508231259.10e951d4@bbrezillon \
--to=boris.brezillon@bootlin.com \
--cc=beanhuo@micron.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=miquel.raynal@bootlin.com \
--cc=peterpandong@micron.com \
--cc=richard@nod.at \
--cc=stable@vger.kernel.org \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox