From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Bean Huo (beanhuo)" <beanhuo@micron.com>
Cc: "boris.brezillon@bootlin.com" <boris.brezillon@bootlin.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"richard@nod.at" <richard@nod.at>
Subject: Re: [EXT] Re: [RESEND PATCH V2 2/2] mtd: core: NAND filling block
Date: Thu, 24 Jan 2019 21:02:34 +0100 [thread overview]
Message-ID: <20190124210234.29275239@xps13> (raw)
In-Reply-To: <BYASPR01MB003174C6FE221EE7CD5EA51BDB9A0@BYASPR01MB0031.namprd08.prod.outlook.com>
Hi Bean,
"Bean Huo (beanhuo)" <beanhuo@micron.com> wrote on Thu, 24 Jan 2019
15:47:25 +0000:
> Hi, Miquel
>
> >
> >> On some legacy planar 2D Micron NAND devices when a block erase
> >> command is issued, occasionally even though a block erase operation
> >> successfully completes and returns a pass status, the flash block may
> >> not be completely erased. Subsequent operations to this block on very
> >> rare cases can result in subtle failures or corruption. These
> >> extremely rare cases should nevertheless be considered.
> >>
> >> These rare occurrences have been observed on partially written blocks.
> >> Partially written blocks are not uncommon with UBI/UBIFS.
> >>
> >> To avoid this rare occurrence, we make sure that at least
> >> 15 pages have been programmed to a block before it is erased.
> >> In case we find that less than 15 pages have been programmed,
> >> additional pages are programmed in the block. The observation is that
> >> additional pages rarely need to be written
> >
> >I would stop the commit message here and remove the end of the sentence
> >which, I believe, is inaccurate.
> >
> I don't understand where is inaccurate.
>
> >> and most of
> >> the time UBI/UBIFS erases blocks that contain more programmed pages.
Because UBI/UBIFS is *one* user of MTD. This patch has nothing to do
with UBI/UBIFS. Plus, the sentence is not very clear to me anyway.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-01-24 20:07 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
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 [this message]
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=20190124210234.29275239@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=beanhuo@micron.com \
--cc=boris.brezillon@bootlin.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=tglx@linutronix.de \
/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).