public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Mika Korhonen <mika.j.korhonen@gmail.com>
To: dedekind@infradead.org
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] MTD: OneNAND: multiblock erase support
Date: Tue, 23 Jun 2009 16:19:21 +0300	[thread overview]
Message-ID: <7948530906230619q6b0d91d8id28a1dbc8131d59f@mail.gmail.com> (raw)
In-Reply-To: <1245755193.9487.53.camel@localhost.localdomain>

2009/6/23 Artem Bityutskiy <dedekind@infradead.org>:
> On Tue, 2009-06-23 at 14:02 +0300, Mika Korhonen wrote:
>> Add support for multiblock erase command. OneNANDs (excluding Flex-OneNAND)
>> are capable of simultaneous erase of up to 64 eraseblocks.
>> This changes the erase requests for regions covering multiple eraseblocks
>> to be performed using multiblock erase.
>>
>> Signed-off-by: Mika Korhonen <ext-mika.2.korhonen@nokia.com>
>> ---
>>  drivers/mtd/onenand/omap2.c        |   22 +++-
>>  drivers/mtd/onenand/onenand_base.c |  268 ++++++++++++++++++++++++++++-------
>>  include/linux/mtd/onenand.h        |    2 +
>>  include/linux/mtd/onenand_regs.h   |    2 +
>>  4 files changed, 236 insertions(+), 58 deletions(-)
>
> Just out of curiosity, what is your use-case for this?
>

When erasing and programming large amounts, e.g. filesystem images on
OneNAND the erase part takes about 10-15% of the time. Using
multiblock erase it takes almost no time (up to 30x faster) :)
Obviously, it is especially useful if the data to be programmed covers
only part of the erased region.

Mika

  reply	other threads:[~2009-06-23 13:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-23 11:02 [PATCH] MTD: OneNAND: multiblock erase support Mika Korhonen
2009-06-23 11:06 ` Artem Bityutskiy
2009-06-23 13:19   ` Mika Korhonen [this message]
2009-06-23 11:27 ` Mika Korhonen

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=7948530906230619q6b0d91d8id28a1dbc8131d59f@mail.gmail.com \
    --to=mika.j.korhonen@gmail.com \
    --cc=dedekind@infradead.org \
    --cc=linux-mtd@lists.infradead.org \
    /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