All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: "Boris Brezillon" <boris.brezillon@free-electrons.com>,
	"\"Qi Wang 王起 (qiwang)\"" <qiwang@micron.com>
Cc: "Iwo Mergler" <Iwo.Mergler@netcommwireless.com>,
	"Jeff Lauruhn (jlauruhn)" <jlauruhn@micron.com>,
	"dedekind1@gmail.com" <dedekind1@gmail.com>,
	"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: Fri, 20 Mar 2015 10:07:33 +0100	[thread overview]
Message-ID: <550BE355.8020009@nod.at> (raw)
In-Reply-To: <20150320095822.7e1979ff@bbrezillon>

Am 20.03.2015 um 09:58 schrieb Boris Brezillon:
> Hi Qi,
> 
> On Fri, 20 Mar 2015 07:44:58 +0000
> Qi Wang 王起 (qiwang) <qiwang@micron.com> wrote:
> 
>>>
>>> I seem to remember a requirement to write pages to a block in a
>>> monotonic fashion (low to high). Is that still the case? It
>>> seems that the low page backup could violate that rule otherwise.
>>
>> Yes, pages need to be programmed from low to high. But it is possible
>> to skip some pages. Take a example,
>>
>> below page program ordering is ok.
>> Page 0, page 1, page 2, page 4, page 6, page 10, page 15, etc..
>> Just make sure don't turn back to program the low page is ok.
> 
> I asked a question regarding the programming sequence in answer to Iwo,
> but I'm not sure you were in Cc, so I'm asking it again.
> 
> Say page 1 is paired with page 4, can we program pages in this order:
> 1, 4, 2, 5, 3, 6, ..., so that both paired pages are programmed
> together (the Jumbo page approach Iwo described in his mail).

That's a good question. I was always told that you're not allowed
to program pages in a non-linear manner.

Thanks,
//richard

  reply	other threads:[~2015-03-20  9:08 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 [this message]
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

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=550BE355.8020009@nod.at \
    --to=richard@nod.at \
    --cc=Iwo.Mergler@netcommwireless.com \
    --cc=andrea.marson@dave.eu \
    --cc=beanhuo@micron.com \
    --cc=boris.brezillon@free-electrons.com \
    --cc=dedekind1@gmail.com \
    --cc=frankliu@micron.com \
    --cc=jlauruhn@micron.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=qiwang@micron.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.