From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: "Qi Wang 王起 (qiwang)" <qiwang@micron.com>
Cc: "Iwo Mergler" <Iwo.Mergler@netcommwireless.com>,
"dedekind1@gmail.com" <dedekind1@gmail.com>,
"richard@nod.at" <richard@nod.at>,
"rnd4@dave-tech.it" <rnd4@dave-tech.it>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Frank Liu 刘群 (frankliu)" <frankliu@micron.com>,
"andrea.marson@dave.eu" <andrea.marson@dave.eu>,
"Bean Huo 霍斌斌 (beanhuo)" <beanhuo@micron.com>
Subject: Re: detect and manage power cut on MLC NAND
Date: Tue, 28 Apr 2015 06:56:20 +0200 [thread overview]
Message-ID: <20150428065620.6de8cd4f@bbrezillon> (raw)
In-Reply-To: <71CF8D7F32C5C24C9CD1D0E02D52498A9DF42BF4@NTXXIAMBX02.xacn.micron.com>
Hi Qi,
Sorry for the late reply (I was quite busy on other projects
lately :-/).
On Mon, 13 Apr 2015 00:44:35 +0000
Qi Wang 王起 (qiwang) <qiwang@micron.com> wrote:
>
> Glad to meet in you ELC.
I was glad to meet you too.
> Is there any planning or idea to fix MLC power loss problem?
For the ideas part, I haven't thought about it since my talk at ELC.
I guess the solution proposed on the MTD website is a good starting
point [1].
Some guys are also considering the "avoid any erase/program operation
when you're about to loose power", but as I already explained I think
the MTD/UBI/UBIFS layers should not rely on this assumption and take
appropriate action to prevent any issue caused by unstable bits.
Best Regards,
Boris
[1]http://www.linux-mtd.infradead.org/doc/ubifs.html#L_unstable_bits
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2015-04-28 4:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.37706.1426822709.22890.linux-mtd@lists.infradead.org>
[not found] ` <71CF8D7F32C5C24C9CD1D0E02D52498A7717444D@NTXXIAMBX02.xacn.micron.com>
2015-03-20 6:52 ` detect and manage power cut on MLC NAND Iwo Mergler
2015-03-20 7:44 ` Qi Wang 王起 (qiwang)
2015-03-20 8:58 ` Boris Brezillon
2015-03-20 9:07 ` Richard Weinberger
2015-03-20 15:05 ` Qi Wang 王起 (qiwang)
2015-03-20 15:19 ` Boris Brezillon
2015-03-20 15:49 ` Qi Wang 王起 (qiwang)
2015-03-20 16:48 ` Jeff Lauruhn (jlauruhn)
2015-03-21 1:48 ` Qi Wang 王起 (qiwang)
2015-03-21 16:06 ` Richard Weinberger
2015-03-20 15:45 ` Qi Wang 王起 (qiwang)
[not found] ` <71CF8D7F32C5C24C9CD1D0E02D52498A9DF42BF4@NTXXIAMBX02.xacn.micron.com>
2015-04-28 4:56 ` Boris Brezillon [this message]
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=20150428065620.6de8cd4f@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=Iwo.Mergler@netcommwireless.com \
--cc=andrea.marson@dave.eu \
--cc=beanhuo@micron.com \
--cc=dedekind1@gmail.com \
--cc=frankliu@micron.com \
--cc=linux-mtd@lists.infradead.org \
--cc=qiwang@micron.com \
--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