From: Artem Bityutskiy <Artem.Bityutskiy@nokia.com>
To: Mika Korhonen <ext-mika.2.korhonen@nokia.com>,
Adrian Hunter <adrian.hunter@nokia.com>
Cc: amul.saha@samsung.com, Kyungmin Park <kyungmin.park@samsung.com>,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH v5 0/3] MTD: OneNAND: multiblock erase support
Date: Tue, 20 Oct 2009 11:57:19 +0300 [thread overview]
Message-ID: <1256029039.29856.145.camel@localhost> (raw)
In-Reply-To: <1255341165-1972-1-git-send-email-ext-mika.2.korhonen@nokia.com>
Similarly, waiting for Adrian to review this. He said he'll do soon.
On Mon, 2009-10-12 at 12:52 +0300, Mika Korhonen wrote:
> (v5) Adjust patches to apply on current tree. Use __func__ in printk's.
> Fix mistakes found by K. Park.
>
> (v4) This patch series is a reworked version of
>
> http://lists.infradead.org/pipermail/linux-mtd/2009-September/027138.html
> http://lists.infradead.org/pipermail/linux-mtd/2009-September/027139.html
> http://lists.infradead.org/pipermail/linux-mtd/2009-September/027140.html
>
> based on comments by Adrian Hunter and Kyungmin Park. This version should
> address the issues pointed out by them.
>
> The original patch is:
> http://lists.infradead.org/pipermail/linux-mtd/2009-June/026130.html
>
> I split the original patch in two for readability: the first part extracts
> the execution of erase command to a separate function for easier integration
> of different erase method. The second part implements the multiblock erase
> function in case multiple blocks are requested to be erased and the chip is
> not Flex.
>
> This is useful for flashing applications that need to do their work as
> fast as possible. For full 64 eraseblock case the erase speed is up to 30x
> faster. (Samsung: 64 MB/s vs 2.1 GB/s, I got 1.4 GB/s on Linux kernel)
>
>
> Mika Korhonen (3):
> MTD: OneNAND: move erase method to a separate function
> MTD: OneNAND: multiblock erase support
> MTD: OneNAND: fix double printing of function name
>
> drivers/mtd/onenand/omap2.c | 22 +++-
> drivers/mtd/onenand/onenand_base.c | 289 +++++++++++++++++++++++++++++------
> include/linux/mtd/flashchip.h | 4 +-
> include/linux/mtd/onenand_regs.h | 2 +
> 4 files changed, 262 insertions(+), 55 deletions(-)
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2009-10-20 8:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 9:52 [PATCH v5 0/3] MTD: OneNAND: multiblock erase support Mika Korhonen
2009-10-12 9:52 ` [PATCH v5 1/3] MTD: OneNAND: move erase method to a separate function Mika Korhonen
2009-10-12 9:52 ` [PATCH v5 2/3] MTD: OneNAND: multiblock erase support Mika Korhonen
2009-10-12 9:52 ` [PATCH v5 3/3] MTD: OneNAND: fix double printing of function name Mika Korhonen
2009-10-20 13:09 ` [PATCH v5 2/3] MTD: OneNAND: multiblock erase support Adrian Hunter
2009-10-23 4:34 ` Artem Bityutskiy
2009-10-23 5:19 ` Mika Korhonen
2009-10-23 5:22 ` Artem Bityutskiy
2009-10-23 5:41 ` Amit Kumar Sharma
2009-10-23 6:00 ` Artem Bityutskiy
2009-10-23 6:05 ` Mika Korhonen
2009-10-23 8:09 ` Adrian Hunter
2009-10-23 8:33 ` Amit Kumar Sharma
2009-10-20 8:57 ` Artem Bityutskiy [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=1256029039.29856.145.camel@localhost \
--to=artem.bityutskiy@nokia.com \
--cc=adrian.hunter@nokia.com \
--cc=amul.saha@samsung.com \
--cc=ext-mika.2.korhonen@nokia.com \
--cc=kyungmin.park@samsung.com \
--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