From: shijie8@gmail.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] mtd: nand: gpmi: add proper raw access support
Date: Sun, 19 Oct 2014 10:20:38 +0800 [thread overview]
Message-ID: <20141019022035.GA1412@localhost.localdomain> (raw)
In-Reply-To: <EACD232272DA4849B060F0828564D13B44955ABE1F@ntcex01.corp.netcomm.com.au>
On Tue, Oct 14, 2014 at 04:50:27PM +1100, Iwo Mergler wrote:
>
> >
> > No, it doesn't seem to be correct.
> > But it's an MLC flash, so you'll most probably need to apply this patch
> > to nandbiterrs testsuite:
> >
> > http://code.bulix.org/f69wuu-87021
> >
> > This patch is flashing the block between each bitflip insertion to
> > avoid multiple write without erasure (which, AFAIK, is not supported
> > by MLC flashes).
>
> Hi Huang,
>
>
> just out of interest, have you tried this on the MLC NAND without the patch?
>
> I'm aware that MLC says you shouldn't write multiple times, but that is
> with a view towards specified data endurance. I would only expect a few
> additional bit errors during the test.
>
> Did you try the overwrite test?
>
The following is the test result for overwrite with this MLC patch:
root at imx6qdlsolo:~# insmod mtd_nandbiterrs.ko dev=1 mode=1
[ 762.534714]
[ 762.536259] ==================================================
[ 762.542115] mtd_nandbiterrs: MTD device: 1
[ 762.546326] mtd_nandbiterrs: MTD device size 16777216,
eraseblock=2097152, page=8192, oob=744
[ 762.554937] mtd_nandbiterrs: Device uses 1 subpages of 8192
bytes
[ 762.561059] mtd_nandbiterrs: Using page=0, offset=0,
eraseblock=0
[ 762.571333] mtd_nandbiterrs: overwrite biterrors test
[ 762.576715] mtd_nandbiterrs: write_page
[ 762.590448] mtd_nandbiterrs: error: read failed at 0x0
[ 762.595650] mtd_nandbiterrs: Read reported error -74
[ 762.600625] mtd_nandbiterrs: Bit error histogram (0
operations total):
[ 762.608586] mtd_nandbiterrs: finished successfully.
[ 762.613501]
==================================================
insmod: ERROR: could not insert module mtd_nandbiterrs.ko:
Input/output error
thanks
Huang Shijie
next prev parent reply other threads:[~2014-10-19 2:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 14:07 [PATCH v3 0/3] mtd: nand: gpmi: add proper raw access support Boris BREZILLON
2014-09-23 14:07 ` [PATCH v3 1/3] mtd: nand: gpmi: add gpmi_move_bits function Boris BREZILLON
2014-09-23 14:54 ` Huang Shijie
2014-09-23 14:58 ` Boris BREZILLON
2014-09-23 15:04 ` Huang Shijie
2014-09-23 15:20 ` Huang Shijie
2014-09-23 15:25 ` Boris BREZILLON
2014-09-23 14:07 ` [PATCH v3 2/3] mtd: nand: gpmi: add proper raw access support Boris BREZILLON
2014-09-23 15:17 ` Huang Shijie
2014-09-23 15:34 ` Boris BREZILLON
2014-09-23 16:10 ` Huang Shijie
2014-09-23 17:16 ` Boris BREZILLON
2014-09-23 17:21 ` Boris BREZILLON
2014-09-23 14:07 ` [PATCH v3 3/3] mtd: nand: gpmi: add raw oob access functions Boris BREZILLON
2014-09-30 8:07 ` [PATCH v3 0/3] mtd: nand: gpmi: add proper raw access support Boris Brezillon
2014-10-05 2:13 ` Huang Shijie
2014-10-08 14:24 ` Huang Shijie
2014-10-08 15:10 ` Boris Brezillon
2014-10-10 14:42 ` Huang Shijie
2014-10-10 14:53 ` Boris Brezillon
2014-10-14 5:50 ` Iwo Mergler
2014-10-16 15:52 ` Huang Shijie
2014-10-19 2:20 ` Huang Shijie [this message]
2014-10-20 5:02 ` Iwo Mergler
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=20141019022035.GA1412@localhost.localdomain \
--to=shijie8@gmail.com \
--cc=linux-arm-kernel@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).