From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Andrea Scian <rnd4@dave-tech.it>
Cc: Richard Weinberger <richard@nod.at>,
"Jeff Lauruhn \(jlauruhn\)" <jlauruhn@micron.com>,
mtd_mailinglist <linux-mtd@lists.infradead.org>,
"dedekind1@gmail.com" <dedekind1@gmail.com>
Subject: Re: RFC: detect and manage power cut on MLC NAND
Date: Tue, 17 Mar 2015 11:02:30 +0100 [thread overview]
Message-ID: <20150317110230.28cfec36@bbrezillon> (raw)
In-Reply-To: <5507F436.7030903@dave-tech.it>
Hi Andrea,
I'll let Jeff answer this question, but I'd like to share my
understanding.
On Tue, 17 Mar 2015 10:30:30 +0100
Andrea Scian <rnd4@dave-tech.it> wrote:
>
>
> Dear Jeff,
>
> Il 16/03/2015 22:11, Jeff Lauruhn (jlauruhn) ha scritto:
> > Good morning Boris;
> > RR is a new feature and not available on all parts few. I'm not sure
> > about others, but since these are features, you simply enable of
> > disable via SET FEATURE/GET FEATURE. If you already provide that
> > SET/GET FEATURE functionality then an end-user determine if their
> > device supports a feature and then write the code to enable when they
> > need it on their particular design.
>
> I can confirm this. In fact I'm currently working with two Micron NAND:
>
> MT29F32G08CBACAWP
> MT29F32G08CBADAWP
>
> The latter should be "just" a newer die revision of the former (at
> least, this is what our distributor says)
>
> There's a technology change between the two and, in fact, the latter
> supports RR while there's no mention of such a feature inside rev C.
>
> Jeff, could you please help me in understanding which if the following
> sentences are true and which are false?
> - rev D is more "robust" than rev C because it has RR (so an additional
> feature that improve error correction)
> - rev D is "robust" like rev C, if rev D is used with RR
> - if RR is not used rev D is more error prone than rev C
RR shouldn't change NAND robustness (or sensitivity to read/write
disturbance generating bitflips).
AFAIU RR will help you improve your NAND lifetime, because you're
allowed to change voltage thresholds which means you can fix errors
that were previously considered as unfixable and lead to blocks being
marked bad earlier.
I'll let Jeff correct me if I'm wrong ;-).
>
> I think this is crucial to understand how RR works and how much is
> needed inside MTD/UBI code.
Hopefully this can all be handled in the MTD layer, with some help
from the UBI layer to feed the wear information (number of P/E cycles
on each block).
Best Regards,
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-17 10:02 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 11:57 RFC: detect and manage power cut on MLC NAND Andrea Scian
2015-03-10 12:51 ` Richard Weinberger
2015-03-11 7:20 ` Artem Bityutskiy
2015-03-11 8:57 ` Richard Weinberger
2015-03-11 9:05 ` Artem Bityutskiy
2015-03-11 9:09 ` Richard Weinberger
2015-03-11 17:01 ` Andrea Scian
2015-03-11 17:23 ` Jeff Lauruhn (jlauruhn)
2015-03-11 17:29 ` Richard Weinberger
2015-03-11 21:16 ` Jeff Lauruhn (jlauruhn)
2015-03-12 10:28 ` Richard Weinberger
2015-03-12 22:57 ` Jeff Lauruhn (jlauruhn)
2015-03-13 20:31 ` Boris Brezillon
2015-03-13 23:51 ` Jeff Lauruhn (jlauruhn)
2015-03-14 9:46 ` Andrea Marson - DAVE Embedded Systems
2015-03-16 16:02 ` Jeff Lauruhn (jlauruhn)
2015-03-17 8:00 ` Andrea Scian
2015-03-14 10:32 ` Boris Brezillon
2015-03-16 21:11 ` Jeff Lauruhn (jlauruhn)
2015-03-17 9:30 ` Andrea Scian
2015-03-17 10:02 ` Boris Brezillon [this message]
2015-03-17 16:42 ` Jeff Lauruhn (jlauruhn)
2015-03-18 8:45 ` RFC: detect and manage power cut on MLC NAND (linux-mtd Digest, Vol 144, Issue 70) Andrea Marson
2015-03-18 9:07 ` Boris Brezillon
2015-03-18 9:56 ` Andrea Marson
2015-03-18 10:03 ` Boris Brezillon
2015-03-18 12:07 ` Richard Weinberger
2015-03-18 17:11 ` Jeff Lauruhn (jlauruhn)
2015-03-18 16:12 ` Jeff Lauruhn (jlauruhn)
2015-03-19 8:47 ` RFC: detect and manage power cut on MLC NAND Andrea Marson
2015-03-19 9:12 ` Boris Brezillon
2015-03-19 17:45 ` Jeff Lauruhn (jlauruhn)
2015-03-20 0:25 ` Iwo Mergler
2015-03-20 3:38 ` nick
2015-03-20 5:40 ` Iwo Mergler
2015-03-20 8:26 ` Boris Brezillon
2015-03-20 17:15 ` Nick Krause
2015-03-22 23:45 ` Iwo Mergler
2015-03-23 2:18 ` Iwo Mergler
2015-03-23 7:06 ` Artem Bityutskiy
2015-03-23 19:05 ` Boris Brezillon
2015-03-24 7:05 ` Artem Bityutskiy
2015-03-19 18:00 ` Jeff Lauruhn (jlauruhn)
2015-03-20 8:07 ` Andrea Marson
2015-03-17 17:04 ` Jeff Lauruhn (jlauruhn)
2015-03-16 9:01 ` Ricard Wanderlof
2015-03-16 17:27 ` Jeff Lauruhn (jlauruhn)
2015-03-14 10:03 ` Richard Weinberger
2015-03-12 9:32 ` Ricard Wanderlof
2015-03-23 4:08 ` Iwo Mergler
2015-03-23 21:15 ` Jeff Lauruhn (jlauruhn)
2015-03-24 1:17 ` Iwo Mergler
2015-03-24 16:50 ` Jeff Lauruhn (jlauruhn)
2015-03-25 3:38 ` Iwo Mergler
2015-03-25 8:33 ` Ricard Wanderlof
2015-03-26 1:57 ` Jeff Lauruhn (jlauruhn)
2015-03-26 8:55 ` Ricard Wanderlof
2015-03-11 7:21 ` Artem Bityutskiy
-- strict thread matches above, loose matches on Subject: below --
2015-03-12 10:31 Andrea Marson - DAVE Embedded Systems
[not found] <mailman.37176.1426610573.22890.linux-mtd@lists.infradead.org>
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=20150317110230.28cfec36@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=dedekind1@gmail.com \
--cc=jlauruhn@micron.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=rnd4@dave-tech.it \
/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).