From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Cyrille Pitchen <cyrille.pitchen@wedev4u.fr>
Subject: Re: [PATCH] mtd: nand: Support 'EXIT GET STATUS' command in nand_command_lp()
Date: Wed, 17 May 2017 18:02:56 +0200 [thread overview]
Message-ID: <20170517180256.0b2abafd@free-electrons.com> (raw)
In-Reply-To: <1494952545-5089-1-git-send-email-boris.brezillon@free-electrons.com>
Hello,
On Tue, 16 May 2017 18:35:45 +0200, Boris Brezillon wrote:
> READ0 is sometimes used to exit GET STATUS mode. When this is the case
> no address cycles are requested, and we can use this information to
> detect that READSTART should not be issued after READ0 or that we
> shouldn't wait for the chip to be ready.
>
> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
Tested-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
On Spear600, which has the FSMC NAND controller, on a platform with a
Micron SLC NAND with on-die ECC.
Tested both mtd_speedtest.ko and mtd_nandbiterrs.ko. The speedtest
shows a nice read speed improvements.
Before:
mtd_speedtest: eraseblock read speed is 8545 KiB/s
mtd_speedtest: page read speed is 8428 KiB/s
mtd_speedtest: 2 page read speed is 8486 KiB/s
After:
mtd_speedtest: eraseblock read speed is 9834 KiB/s
mtd_speedtest: page read speed is 9682 KiB/s
mtd_speedtest: 2 page read speed is 9756 KiB/s
The write and erase speeds are unchanged.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-17 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-16 16:35 [PATCH] mtd: nand: Support 'EXIT GET STATUS' command in nand_command_lp() Boris Brezillon
2017-05-17 16:02 ` Thomas Petazzoni [this message]
2017-05-29 18:50 ` 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=20170517180256.0b2abafd@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=richard@nod.at \
/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).