From: xiaolei li <xiaolei.li@mediatek.com>
To: <miquel.raynal@bootlin.com>
Cc: richard@nod.at, linux-mediatek@lists.infradead.org,
linux-mtd@lists.infradead.org, srv_heupstream@mediatek.com
Subject: Re: [PATCH v3 0/4] MTK NAND driver improvements and fixes
Date: Fri, 17 May 2019 09:32:47 +0800 [thread overview]
Message-ID: <1558056767.26455.98.camel@mhfsdcap03> (raw)
In-Reply-To: <20190507102541.34341-1-xiaolei.li@mediatek.com>
Hi Miquel,
Sorry to bother you, but may I ask if it is fine to accept this patch
set now, patches all with your review.
Thanks,
Xiaolei
On Tue, 2019-05-07 at 18:25 +0800, Xiaolei Li wrote:
> The following patch set mainly contains:
> * 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.
>
> Changes on v3 relative to:
> --------------------
>
> tree : https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git/
> branch : nand/next
> commit :
> 'commit 1c14fe2167ef ("mtd: nandsim: switch to exec_op interface")
>
> Patch v3:
> ---------
> - Fix some comment style.
> - Format patch base branch: nand/next
> - Pend to sent patch "mtd: rawnand: mtk: Setup empty page threshold
> correctly", because it seems that we should confirm this change has no
> side effect and need more test.
>
> Patch v2:
> ---------
> - Fix type
> - Reference correct faulty patch
> - Refine code to do calculation and condition in separate steps
> - Fix empty threshold calculation
>
> 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 (4):
> 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
>
> drivers/mtd/nand/raw/mtk_nand.c | 84 +++++++++++++++++++++++++++------
> 1 file changed, 70 insertions(+), 14 deletions(-)
>
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-05-17 1:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 10:25 [PATCH v3 0/4] MTK NAND driver improvements and fixes Xiaolei Li
2019-05-07 10:25 ` [PATCH v3 1/4] mtd: rawnand: mtk: Correct low level time calculation of r/w cycle Xiaolei Li
2019-06-03 8:04 ` Miquel Raynal
2019-05-07 10:25 ` [PATCH v3 2/4] mtd: rawnand: mtk: Improve data sampling timing for read cycle Xiaolei Li
2019-06-03 8:04 ` Miquel Raynal
2019-05-07 10:25 ` [PATCH v3 3/4] mtd: rawnand: mtk: Add validity check for CE# pin setting Xiaolei Li
2019-06-03 8:04 ` Miquel Raynal
2019-05-07 10:25 ` [PATCH v3 4/4] mtd: rawnand: mtk: Fix wrongly assigned OOB buffer pointer issue Xiaolei Li
2019-06-03 8:04 ` Miquel Raynal
2019-05-17 1:32 ` xiaolei li [this message]
2019-05-17 8:12 ` [PATCH v3 0/4] MTK NAND driver improvements and fixes Miquel Raynal
2019-05-17 9:21 ` 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=1558056767.26455.98.camel@mhfsdcap03 \
--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).