From: Roger Quadros <rogerq@ti.com>
To: <computersforpeace@gmail.com>, <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org, akinobu.mita@gmail.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] mtd: oobtest: Add parameter to ignore bitflip errors within specified limit
Date: Tue, 11 Nov 2014 12:14:34 +0200 [thread overview]
Message-ID: <5461E18A.6000303@ti.com> (raw)
In-Reply-To: <1413899608-3911-1-git-send-email-rogerq@ti.com>
Hi,
On 10/21/2014 04:53 PM, Roger Quadros wrote:
> Hi,
>
> The oobtest case uses raw NAND read/writes to OOB area bypassing the error correction
> mechanism and hence is bound to be affected by bitflip errors which are normal
> in NAND memories. (e.g. we can never get DRA7-evm's NAND to fully pass
> mtd_oobtest).
>
> In these patches we add a module parameter "bitflip_limit" to specify how many
> bitflips per page are tolerable. Not specifiing the parameter defaults to old
> behaviour (i.e. zero bitflips tolerated).
> Specifying bitflip_limit=1 makes us pass on DRA7-evm with 0 errors.
>
> Introduce a new memcmpshow() function that shows the data byte where comparison failed.
> This is useful for debugging. The same function is also used to calculate number of
> bitflip errors over the data block.
Any comments on this series?
cheers,
-roger
>
> Roger Quadros (2):
> mtd: mtd_oobtest: Show the verification error location and data
> mtd: mtd_oobtest: add bitflip_limit parameter
>
> drivers/mtd/tests/oobtest.c | 77 +++++++++++++++++++++++++++++++++++++--------
> 1 file changed, 64 insertions(+), 13 deletions(-)
>
WARNING: multiple messages have this Message-ID (diff)
From: Roger Quadros <rogerq@ti.com>
To: <computersforpeace@gmail.com>, <dwmw2@infradead.org>
Cc: <akinobu.mita@gmail.com>, <linux-mtd@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/2] mtd: oobtest: Add parameter to ignore bitflip errors within specified limit
Date: Tue, 11 Nov 2014 12:14:34 +0200 [thread overview]
Message-ID: <5461E18A.6000303@ti.com> (raw)
In-Reply-To: <1413899608-3911-1-git-send-email-rogerq@ti.com>
Hi,
On 10/21/2014 04:53 PM, Roger Quadros wrote:
> Hi,
>
> The oobtest case uses raw NAND read/writes to OOB area bypassing the error correction
> mechanism and hence is bound to be affected by bitflip errors which are normal
> in NAND memories. (e.g. we can never get DRA7-evm's NAND to fully pass
> mtd_oobtest).
>
> In these patches we add a module parameter "bitflip_limit" to specify how many
> bitflips per page are tolerable. Not specifiing the parameter defaults to old
> behaviour (i.e. zero bitflips tolerated).
> Specifying bitflip_limit=1 makes us pass on DRA7-evm with 0 errors.
>
> Introduce a new memcmpshow() function that shows the data byte where comparison failed.
> This is useful for debugging. The same function is also used to calculate number of
> bitflip errors over the data block.
Any comments on this series?
cheers,
-roger
>
> Roger Quadros (2):
> mtd: mtd_oobtest: Show the verification error location and data
> mtd: mtd_oobtest: add bitflip_limit parameter
>
> drivers/mtd/tests/oobtest.c | 77 +++++++++++++++++++++++++++++++++++++--------
> 1 file changed, 64 insertions(+), 13 deletions(-)
>
next prev parent reply other threads:[~2014-11-11 10:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-21 13:53 [PATCH 0/2] mtd: oobtest: Add parameter to ignore bitflip errors within specified limit Roger Quadros
2014-10-21 13:53 ` Roger Quadros
2014-10-21 13:53 ` [PATCH 1/2] mtd: mtd_oobtest: Show the verification error location and data Roger Quadros
2014-10-21 13:53 ` Roger Quadros
2014-10-21 13:53 ` [PATCH 2/2] mtd: mtd_oobtest: add bitflip_limit parameter Roger Quadros
2014-10-21 13:53 ` Roger Quadros
2014-11-11 10:14 ` Roger Quadros [this message]
2014-11-11 10:14 ` [PATCH 0/2] mtd: oobtest: Add parameter to ignore bitflip errors within specified limit Roger Quadros
2014-11-20 7:57 ` Brian Norris
2014-11-20 7:57 ` Brian Norris
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=5461E18A.6000303@ti.com \
--to=rogerq@ti.com \
--cc=akinobu.mita@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.