From: Xiaolei Li <xiaolei.li@mediatek.com>
To: <miquel.raynal@bootlin.com>, <richard@nod.at>
Cc: linux-mediatek@lists.infradead.org, xiaolei.li@mediatek.com,
linux-mtd@lists.infradead.org, srv_heupstream@mediatek.com
Subject: [PATCH 0/5] MTK NAND driver improvements and fixes
Date: Mon, 29 Apr 2019 14:38:29 +0800 [thread overview]
Message-ID: <20190429063834.45967-1-xiaolei.li@mediatek.com> (raw)
Hello Maintainers,
The following patch set is used to do MTK NAND driver improvements and
bug fixes, include:
* Fix low level time calculation of read/write cycle to meet tRC_min
and tWC_min requirements.
* Refine RE# pulse width calculation and data sampling to improve read
performance.
* Add CS validity check.
* Fix oob buffer pointer wrongly setting and empty page threshold setting.
Changes relative to:
--------------------
tree : git://git.infradead.org/linux-mtd.git
branch : master
commit :
'commit 3e35730dd754 ("mtd: powernv_flash: Fix device
registration error")
Tests:
------
* ubifs and jffs2 are validated on NAND device MT29F16G08ADBCA by
'dd' command.
* all drivers/mtd/tests/* pass.
* speed test:
eraseblock write speed is 11087 KiB/s
eraseblock read speed is 19986 KiB/s
page write speed is 10689 KiB/s
page read speed is 18724 KiB/s
2 page write speed is 10611 KiB/s
2 page read speed is 18713 KiB/s
erase speed is 103696 KiB/s
2x multi-block erase speed is 354248 KiB/s
4x multi-block erase speed is 350459 KiB/s
8x multi-block erase speed is 356173 KiB/s
16x multi-block erase speed is 356173 KiB/s
32x multi-block erase speed is 358120 KiB/s
64x multi-block erase speed is 356173 KiB/s
Xiaolei Li (5):
mtd: rawnand: mtk: Correct low level time calculation of r/w cycle
mtd: rawnand: mtk: Improve data sampling timing for read cycle
mtd: rawnand: mtk: Add validity check for CE# pin setting
mtd: rawnand: mtk: Fix wrongly assigned oob buffer pointer issue
mtd: rawnand: mtk: Setup empty page threshold correctly
drivers/mtd/nand/raw/mtk_nand.c | 73 ++++++++++++++++++++++++++-------
1 file changed, 59 insertions(+), 14 deletions(-)
--
2.18.0
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2019-04-29 6:38 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-29 6:38 Xiaolei Li [this message]
2019-04-29 6:38 ` [PATCH 1/5] mtd: rawnand: mtk: Correct low level time calculation of r/w cycle Xiaolei Li
2019-04-29 9:03 ` Miquel Raynal
2019-04-29 9:35 ` xiaolei li
2019-04-29 10:02 ` Miquel Raynal
2019-04-30 0:59 ` xiaolei li
2019-04-29 6:38 ` [PATCH 2/5] mtd: rawnand: mtk: Improve data sampling timing for read cycle Xiaolei Li
2019-04-29 9:10 ` Miquel Raynal
2019-04-29 9:49 ` xiaolei li
2019-04-29 6:38 ` [PATCH 3/5] mtd: rawnand: mtk: Add validity check for CE# pin setting Xiaolei Li
2019-04-29 9:11 ` Miquel Raynal
2019-04-29 6:38 ` [PATCH 4/5] mtd: rawnand: mtk: Fix wrongly assigned oob buffer pointer issue Xiaolei Li
2019-04-29 9:14 ` Miquel Raynal
2019-04-29 9:52 ` xiaolei li
2019-04-29 6:38 ` [PATCH 5/5] mtd: rawnand: mtk: Setup empty page threshold correctly Xiaolei Li
2019-04-29 9:22 ` Miquel Raynal
2019-04-29 9:57 ` xiaolei li
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=20190429063834.45967-1-xiaolei.li@mediatek.com \
--to=xiaolei.li@mediatek.com \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=srv_heupstream@mediatek.com \
/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).