public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrea Scian <rnd4@dave-tech.it>
To: linux-mtd@lists.infradead.org, Han Xu <b45815@freescale.com>
Cc: shijie8@gmail.com, dwmw2@infradead.org,
	computersforpeace@gmail.com, boris.brezillon@free-electrons.com,
	fabio.estevam@freescale.com, hofrat@osadl.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] mtd: nand: gpmi: correct bitflip for erased NAND page
Date: Wed, 29 Jul 2015 10:05:38 +0200	[thread overview]
Message-ID: <55B88952.1060709@dave-tech.it> (raw)
In-Reply-To: <1438105841-22314-1-git-send-email-b45815@freescale.com>

Dear Han Xu,


Il 28/07/2015 19:50, Han Xu ha scritto:
> i.MX6QP and i.MX7D BCH module integrated a new feature to detect the
> bitflip number for erased NAND page. So for these two platform, set the
> erase threshold to gf/2 and if bitflip detected, GPMI driver will
> correct the data to all 0xFF.


That's an iteresting feature of iMX6QP
We were discussing about erased NAND page bitflip in MTD ML a few days ago.

Is gf/2 a right value to choose? Why?
IIUC, in a previuos MTD-level patch [1] Brian used ECC strength as 
threshold.

Could you please also share with which NAND device you tested this patch?

Kind regards and TIA,

-- 

Andrea SCIAN

DAVE Embedded Systems

[1] http://article.gmane.org/gmane.linux.drivers.mtd/52216

  reply	other threads:[~2015-07-29  8:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.4028.1438106338.1758.linux-mtd@lists.infradead.org>
     [not found] ` <mailman.4028.1438106338.1758.linux-mtd.{c3fbf4b6-bd46-4f1f-ba46-40c78864ddc3}.0@lists.infradead.org>
2015-07-28 17:50   ` [PATCH 5/6] mtd: nand: gpmi: correct bitflip for erased NAND page Han Xu
2015-07-29  8:05     ` Andrea Scian [this message]
2015-07-29 14:34       ` Han Xu
2015-07-29 16:01         ` Andrea Scian

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=55B88952.1060709@dave-tech.it \
    --to=rnd4@dave-tech.it \
    --cc=b45815@freescale.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=fabio.estevam@freescale.com \
    --cc=hofrat@osadl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox