From: Boris Brezillon <bbrezillon@kernel.org>
To: "Bean Huo (beanhuo)" <beanhuo@micron.com>
Cc: "richard@nod.at" <richard@nod.at>,
"boris.brezillon@bootlin.com" <boris.brezillon@bootlin.com>,
"Zoltan Szubbocsev \(zszubbocsev\)" <zszubbocsev@micron.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"miquel.raynal@bootlin.com" <miquel.raynal@bootlin.com>,
"tglx@linutronix.de" <tglx@linutronix.de>
Subject: Re: [EXT] Re: [RESEND PATCH V2 2/2] mtd: core: NAND filling block
Date: Mon, 21 Jan 2019 11:12:55 +0100 [thread overview]
Message-ID: <20190121111255.79be03de@bbrezillon> (raw)
In-Reply-To: <BYAPR08MB4533227B317D5AA334FEB240DB9F0@BYAPR08MB4533.namprd08.prod.outlook.com>
On Mon, 21 Jan 2019 10:04:15 +0000
"Bean Huo (beanhuo)" <beanhuo@micron.com> wrote:
> Hi, Boris
>
> >On Fri, 18 Jan 2019 22:12:04 +0000
> >"Bean Huo (beanhuo)" <beanhuo@micron.com> wrote:
> >
> >> + /* Corrupt page0 and page1, in order to simulate an
> >> + * uncompleted eraseing scenario. Just for case of
> >> + * power loss hits while below programming. in this
> >> + * way, the PEB will be re-erased again.
> >> + */
> >> + empty_page_mask |= 0x3;
> >> + memset(data_buf, 0xAA, mtd->writesize);
> >
> >Why do you use the 0xaa pattern BTW?
>
> Random pattern or any pattern is ok. Just to fill in page.
Let's use 0x0 then. This way all cells are actually in a "programmed"
state. BTW, I'd still be interested in knowing more about the root
cause of this issue. What causes this wrong "cell is erased" detection
in your chips? I thought the ERASE operation was an iterative process
and cells were being tested after each step to know whether they are
erased or not in order to decide to do another step or stop.
Am I wrong? What happens here to cause this erroneous detection?
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-01-21 10:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-18 22:12 [RESEND PATCH V2 2/2] mtd: core: NAND filling block Bean Huo (beanhuo)
2019-01-18 22:39 ` Boris Brezillon
2019-01-20 17:31 ` Boris Brezillon
2019-01-21 12:28 ` [EXT] " Bean Huo (beanhuo)
2019-01-21 12:44 ` Boris Brezillon
2019-01-25 13:39 ` Bean Huo (beanhuo)
2019-01-25 14:10 ` Boris Brezillon
2019-01-18 23:01 ` Boris Brezillon
2019-01-21 10:04 ` [EXT] " Bean Huo (beanhuo)
2019-01-21 10:12 ` Boris Brezillon [this message]
2019-01-25 13:31 ` Bean Huo (beanhuo)
2019-01-25 14:15 ` Boris Brezillon
2019-01-20 15:59 ` Miquel Raynal
2019-01-24 15:47 ` [EXT] " Bean Huo (beanhuo)
2019-01-24 20:02 ` Miquel Raynal
2019-01-20 17:36 ` 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=20190121111255.79be03de@bbrezillon \
--to=bbrezillon@kernel.org \
--cc=beanhuo@micron.com \
--cc=boris.brezillon@bootlin.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
--cc=zszubbocsev@micron.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