public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: "Gupta, Pekon" <pekon@ti.com>
Cc: Huang Shijie <b32955@freescale.com>,
	Lin Wei-B34918 <B34918@freescale.com>,
	"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
	David Woodhouse <dwmw2@infradead.org>,
	Matthieu CASTET <matthieu.castet@parrot.com>
Subject: Re: question about mtd_torturetest.c
Date: Mon, 04 Feb 2013 08:58:44 +0200	[thread overview]
Message-ID: <1359961124.13791.1.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <20980858CB6D3A4BAE95CA194937D5E73E995A7B@DBDE01.ent.ti.com>

[-- Attachment #1: Type: text/plain, Size: 985 bytes --]

On Mon, 2013-02-04 at 05:19 +0000, Gupta, Pekon wrote:
> > On Wed, 2013-01-23 at 15:25 +0800, Huang Shijie wrote:
> > > Hi all:
> > >
> > >     The mtd_torturetest.c uses the 55/AA patterns to torture the nand
> > block.
> > > Are the 55/AA patterns more tougher then the random data?
> > 
> > Probably not, please, improve the test.
> > 
> 
> (0x55/0xAA/0x55) pattern ensures that _all_ bits in the byte transition from 0-> 1, and 1->0,
> Whereas, a random pattern may miss a bit-cell or miss transition sequence, of an bad bit-cell.
> Exercising each bit both ways is important so as to differentiate a bad bit-cell (permanent error) from read-disturb errors (temporary error).
> 
> For read-disturb: http://download.micron.com/pdf/presentations/events/flash_mem_summit_jcooke_inconvenient_truths_nand.pdf

Sure, I did not mean remove those, I meant that random data test can
also be added and that would be an improvement.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-02-04  6:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-18  8:05 question: Why the nand_wait() wait for 20ms for nand program Huang Shijie
2013-01-18 12:26 ` Matthieu CASTET
2013-01-21  3:34   ` Huang Shijie
2013-01-21  8:57     ` Matthieu CASTET
     [not found]       ` <50FD0554.8030108@freescale.com>
2013-01-21  9:15         ` Matthieu CASTET
2013-01-21  9:25           ` Huang Shijie
2013-01-21  9:32             ` Matthieu CASTET
2013-01-21  9:35               ` Huang Shijie
     [not found]                 ` <50FF9068.1030709@freescale.com>
2013-02-01 16:58                   ` question about mtd_torturetest.c Artem Bityutskiy
2013-02-04  5:19                     ` Gupta, Pekon
2013-02-04  6:58                       ` Artem Bityutskiy [this message]
2013-02-04  7:32                         ` Huang Shijie
2013-01-22  2:46               ` question: Why the nand_wait() wait for 20ms for nand program Huang Shijie

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=1359961124.13791.1.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=B34918@freescale.com \
    --cc=b32955@freescale.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=matthieu.castet@parrot.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox