All of lore.kernel.org
 help / color / mirror / Atom feed
From: Brian Norris <computersforpeace@gmail.com>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: Kent Li <kent.li@radisys.com>,
	Elie De Brauwer <eliedebrauwer@gmail.com>,
	Artem Bityutskiy <dedekind1@gmail.com>,
	HOUR Frederic <frederic.hour@safran-engineering.com>,
	Huang Shijie <b32955@freescale.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	"Gupta, Pekon" <pekon@ti.com>
Subject: Re: [PATCH 1/2] mtd: nand: add erased-page bitflip correction
Date: Mon, 17 Mar 2014 11:53:47 -0700	[thread overview]
Message-ID: <20140317185347.GC3834@ld-irv-0074> (raw)
In-Reply-To: <20140313125717.GB1758@arch.cereza>

On Thu, Mar 13, 2014 at 09:57:17AM -0300, Ezequiel Garcia wrote:
> On Mar 12, Brian Norris wrote:
> > Really? So if you read a blank (all 0xff) page that has no bitflips, you
> > see an ECC error? I'm sorry, but I didn't realize that's how your
> > hardware worked. That's the worst hardware ECC design I've seen so far
> > :(
> > 
> 
> I haven't had time to follow this discussion yet, but just wanted to point
> out the above is also true for pxa3xx-nand.c.

I'm learning every day!

> If a completely erased page is read, the calculated ECC would be 0 and the
> stored ECC would be all 0xff (although I never actually checked this).
> See the snippet below:
> 
> static int pxa3xx_nand_read_page_hwecc(struct mtd_info *mtd,
> 		struct nand_chip *chip, uint8_t *buf, int oob_required,
> 		int page)
> {
> 	[..]
> 	} else if (info->retcode == ERR_UNCORERR) {
> 		/*
> 		 * for blank page (all 0xff), HW will calculate its ECC as
> 		 * 0, which is different from the ECC information within
> 		 * OOB, ignore such uncorrectable errors
> 		 */
> 		if (is_buf_blank(buf, mtd->writesize))
> 			info->retcode = ERR_NONE;
> 	}
> 	[..]
> }

Looks like pxa3xx_nand will probably need the same flag, then we could
probably kill the is_buf_blank() check.

Brian

  reply	other threads:[~2014-03-17 18:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-11  9:11 [PATCH 1/2] mtd: nand: add erased-page bitflip correction Brian Norris
2014-03-11  9:11 ` [PATCH 2/2] mtd: gpmi-nand: use erased-page bitflip check Brian Norris
2014-03-11 10:12 ` [PATCH 1/2] mtd: nand: add erased-page bitflip correction Gupta, Pekon
2014-03-12  5:32   ` Brian Norris
2014-03-12  5:59     ` Elie De Brauwer
2014-03-12  6:59       ` Brian Norris
2014-03-12 12:45         ` Elie De Brauwer
2014-03-13  5:22           ` Brian Norris
2014-03-13  5:55             ` Gupta, Pekon
2014-03-13  6:28               ` Brian Norris
2014-03-13  7:01                 ` Gupta, Pekon
2014-03-17 18:47                   ` Brian Norris
2014-03-18  7:55                     ` Ricard Wanderlof
2014-03-13 12:57                 ` Ezequiel Garcia
2014-03-17 18:53                   ` Brian Norris [this message]
2014-03-13  7:37             ` Elie De Brauwer
2014-03-12  8:06 ` Huang Shijie
2014-03-13  4:55   ` Brian Norris
2014-03-13  8:04     ` Huang Shijie
2014-03-17 16:46       ` Brian Norris
2014-03-17 17:50         ` Gupta, Pekon
2014-03-18  6:48         ` Huang Shijie
2014-03-13 21:32 ` Bill Pringlemeir
2014-03-17 19:46   ` Brian Norris
2014-03-17 22:55     ` Bill Pringlemeir
2014-03-17 23:01       ` Bill Pringlemeir

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=20140317185347.GC3834@ld-irv-0074 \
    --to=computersforpeace@gmail.com \
    --cc=b32955@freescale.com \
    --cc=dedekind1@gmail.com \
    --cc=eliedebrauwer@gmail.com \
    --cc=ezequiel.garcia@free-electrons.com \
    --cc=frederic.hour@safran-engineering.com \
    --cc=kent.li@radisys.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=pekon@ti.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.