From: Iwo Mergler <iwo.mergler@netcommwireless.com>
To: <linux-mtd@lists.infradead.org>
Cc: Richard Weinberger <richard@nod.at>,
Brian Norris <computersforpeace@gmail.com>,
Huang Shijie <b32955@freescale.com>
Subject: [PATCH] mtd: nandbiterrs: Support for NAND biterrors test on platforms without raw write
Date: Fri, 6 May 2016 10:00:12 +1000 [thread overview]
Message-ID: <572BDE8C.3020703@netcommwireless.com> (raw)
Hi all,
I'm vaguely aware that there is an ongoing effort to move this
stuff to mtd-utils, but I was unable to find a source tree
with the work so far.
Below is a single-line patch for the kernel tests, feel free
to apply to the userspace source as well.
Best regards,
Iwo
Support for NAND biterrors test on platforms without raw write
While the default test mode relies on raw write (mtd_write_oob) to introduce
bit errors into a page, the rewrite test mode doesn't need it.
Some drivers use eldritch data/ECC arrangements in a NAND page and reshuffle
things on-the-fly, to present a normal page view to the kernel. Typically,
raw write / read is unsupported on such platforms. Examples are Freescale
MXS and Qualcomm MDM9 and probably many others.
Changed the overwrite test to use normal writes.
Signed-off-by: Iwo Mergler <Iwo.Mergler@netcommwireless.com>
---
drivers/mtd/tests/nandbiterrs.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mtd/tests/nandbiterrs.c
b/drivers/mtd/tests/nandbiterrs.c
index 09a4cca..f26dec8 100644
--- a/drivers/mtd/tests/nandbiterrs.c
+++ b/drivers/mtd/tests/nandbiterrs.c
@@ -290,7 +290,7 @@ static int overwrite_test(void)
while (opno < max_overwrite) {
- err = rewrite_page(0);
+ err = write_page(0);
if (err)
break;
--
2.7.3
next reply other threads:[~2016-05-06 0:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-06 0:00 Iwo Mergler [this message]
2016-05-08 16:44 ` [PATCH] mtd: nandbiterrs: Support for NAND biterrors test on platforms without raw write Boris Brezillon
2016-05-08 16:47 ` Boris Brezillon
2016-05-09 4:09 ` Iwo Mergler
2016-05-10 8:48 ` Boris Brezillon
2016-05-11 6:54 ` Iwo Mergler
2016-05-11 6:54 ` Iwo Mergler
2016-06-20 11:48 ` 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=572BDE8C.3020703@netcommwireless.com \
--to=iwo.mergler@netcommwireless.com \
--cc=b32955@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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