From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Dario Binacchi <dario.binacchi@amarulasolutions.com>
Cc: linux-kernel@vger.kernel.org,
Michael Trimarchi <michael@amarulasolutions.com>,
Han Xu <han.xu@nxp.com>, Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org
Subject: Re: [RFC PATCH 2/4] mtd: rawnand: gpmi: support fast edo timings for mx28
Date: Wed, 22 Dec 2021 17:08:54 +0100 [thread overview]
Message-ID: <20211222170854.7f6f91da@xps13> (raw)
In-Reply-To: <20211217155512.1877408-3-dario.binacchi@amarulasolutions.com>
Hi Dario,
dario.binacchi@amarulasolutions.com wrote on Fri, 17 Dec 2021 16:55:10
+0100:
> In the mx28 reference manual there are examples of how to set up the
> GPMI controller to support fast NAND EDO timing.
... which are? I am not sure to understand what you mean here.
And what you change below is just "not refusing EDO timings with on
MX28". There is a mismatch between the the two.
Plus, it seems that this patch should come last given the fact that
you're fixing the EDO calculations.
> This patch has been tested on a 2048/64 byte NAND (Micron MT29F2G08ABAEAH4).
> Kernel mtd tests:
> - mtd_nandbiterrs
> - mtd_nandecctest
> - mtd_oobtest
> - mtd_pagetest
> - mtd_readtest
> - mtd_speedtest
> - mtd_stresstest
> - mtd_subpagetest
> - mtd_torturetest [cycles_count = 10000000]
> run without errors.
>
> Before this patch (mode 0):
> ---------------------------
> eraseblock write speed is 2098 KiB/s
> eraseblock read speed is 2680 KiB/s
> page write speed is 1689 KiB/s
> page read speed is 2522 KiB/s
> 2 page write speed is 1899 KiB/s
> 2 page read speed is 2579 KiB/s
> erase speed is 128000 KiB/s
> 2x multi-block erase speed is 73142 KiB/s
> 4x multi-block erase speed is 204800 KiB/s
> 8x multi-block erase speed is 256000 KiB/s
> 16x multi-block erase speed is 256000 KiB/s
> 32x multi-block erase speed is 256000 KiB/s
> 64x multi-block erase speed is 256000 KiB/s
>
> After this patch (mode 5):
> -------------------------
> eraseblock write speed is 3390 KiB/s
> eraseblock read speed is 5688 KiB/s
> page write speed is 2680 KiB/s
> page read speed is 4876 KiB/s
> 2 page write speed is 2909 KiB/s
> 2 page read speed is 5224 KiB/s
> erase speed is 170666 KiB/s
> 2x multi-block erase speed is 204800 KiB/s
> 4x multi-block erase speed is 256000 KiB/s
> 8x multi-block erase speed is 256000 KiB/s
> 16x multi-block erase speed is 256000 KiB/s
> 32x multi-block erase speed is 256000 KiB/s
> 64x multi-block erase speed is 256000 KiB/s
>
> Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com>
> Co-developed-by: Michael Trimarchi <michael@amarulasolutions.com>
> ---
>
> drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c b/drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c
> index 65bcd1c548d2..fd935e893daf 100644
> --- a/drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c
> +++ b/drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c
> @@ -772,8 +772,8 @@ static int gpmi_setup_interface(struct nand_chip *chip, int chipnr,
> if (IS_ERR(sdr))
> return PTR_ERR(sdr);
>
> - /* Only MX6 GPMI controller can reach EDO timings */
> - if (sdr->tRC_min <= 25000 && !GPMI_IS_MX6(this))
> + /* Only MX28/MX6 GPMI controller can reach EDO timings */
> + if (sdr->tRC_min <= 25000 && !GPMI_IS_MX28(this) && !GPMI_IS_MX6(this))
> return -ENOTSUPP;
>
> /* Stop here if this call was just a check */
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2021-12-22 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-17 15:55 [RFC PATCH 0/4] Fix and improve gpmi nand on mx28 Dario Binacchi
2021-12-17 15:55 ` [RFC PATCH 2/4] mtd: rawnand: gpmi: support fast edo timings for mx28 Dario Binacchi
2021-12-22 16:08 ` Miquel Raynal [this message]
2021-12-17 15:55 ` [RFC PATCH 3/4] mtd: rawnand: gpmi: fix controller timings setting Dario Binacchi
2021-12-22 16:10 ` Miquel Raynal
2021-12-17 15:55 ` [RFC PATCH 4/4] mtd: rawnand: gpmi: validate controller clock rate Dario Binacchi
2021-12-22 16:23 ` Miquel Raynal
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=20211222170854.7f6f91da@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=dario.binacchi@amarulasolutions.com \
--cc=han.xu@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@amarulasolutions.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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