From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: Kamal Dasu <kdasu.kdev@gmail.com>,
linux-mtd@lists.infradead.org, f.fainelli@gmail.com,
bcm-kernel-feedback-list@broadcom.com
Subject: Re: [V3, 2/2] mtd: brcmnand: Detect sticky ucorr ecc error on dma reads
Date: Mon, 11 Jul 2016 08:49:06 +0200 [thread overview]
Message-ID: <20160711084906.13cac84e@bbrezillon> (raw)
In-Reply-To: <20160711050452.GA12083@localhost>
On Sun, 10 Jul 2016 22:04:52 -0700
Brian Norris <computersforpeace@gmail.com> wrote:
> Hi,
>
> Looking through Boris's pull request, I noticed an issue:
>
> On Thu, Jun 09, 2016 at 05:17:55PM -0400, Kamal Dasu wrote:
> > This change provides a fix for controller bug where nand
> > controller could have a possible sticky error after a PIO
> > followed by a DMA read. The fix retries a read if we see
> > a uncorr_ecc after read to detect such sticky errors.
> > The fix applies to only controller version 7.0 and 7.1.
> >
> > Signed-off-by: Kamal Dasu <kdasu.kdev@gmail.com>
> > ---
> > V3 changes
> > none
> > V2 Changes
> > Restrict controller bug workaround to version 7.0 and 7.1
> > ---
> > drivers/mtd/nand/brcmnand/brcmnand.c | 18 ++++++++++++++++++
> > 1 file changed, 18 insertions(+)
> >
> > diff --git a/drivers/mtd/nand/brcmnand/brcmnand.c b/drivers/mtd/nand/brcmnand/brcmnand.c
> > index 7ee9617..1156495 100644
> > --- a/drivers/mtd/nand/brcmnand/brcmnand.c
> > +++ b/drivers/mtd/nand/brcmnand/brcmnand.c
> > @@ -1602,9 +1602,11 @@ static int brcmnand_read(struct mtd_info *mtd, struct nand_chip *chip,
> > struct brcmnand_controller *ctrl = host->ctrl;
> > u64 err_addr = 0;
> > int err;
> > + static bool retry = true;
>
> Is this intentionally static? That means your retry will only be
> performed exactly once *ever*. Probably not what you expected?
>
> Boris, if this is indeed unintended, would you rather fix this up in the
> original patch and send me a new pull request?
I'll fix the initial commit and send a new PR once Kamal has confirmed
this variable should not be static (which is also my opinion).
> Or have my apply the
> trivial fixup (i.e., s/static//) as a separate patch on top?
Thanks,
Boris
next prev parent reply other threads:[~2016-07-11 6:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 21:17 [V3, 1/2] mtd: brcmnand: Add check for erased page bitflips Kamal Dasu
2016-06-09 21:17 ` [V3, 2/2] mtd: brcmnand: Detect sticky ucorr ecc error on dma reads Kamal Dasu
2016-07-11 5:04 ` Brian Norris
2016-07-11 6:49 ` Boris Brezillon [this message]
2016-07-11 14:52 ` Kamal Dasu
2016-06-13 20:07 ` [V3, 1/2] mtd: brcmnand: Add check for erased page bitflips 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=20160711084906.13cac84e@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=computersforpeace@gmail.com \
--cc=f.fainelli@gmail.com \
--cc=kdasu.kdev@gmail.com \
--cc=linux-mtd@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).