linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Teng Wu <gigadevice2025@gmail.com>
Cc: richard@nod.at,  vigneshr@ti.com,  linux-mtd@lists.infradead.org,
	linux-kernel@vger.kernel.org,  teng.wu@gigadevice.com
Subject: Re: [PATCH] mtd: spinand: gigadevice: Add continuous read support
Date: Sun, 24 Aug 2025 18:30:51 +0200	[thread overview]
Message-ID: <87349gisw4.fsf@bootlin.com> (raw)
In-Reply-To: <20250818135227.2114-1-gigadevice2025@gmail.com> (Teng Wu's message of "Mon, 18 Aug 2025 21:52:27 +0800")

Hello Teng,

On 18/08/2025 at 21:52:27 +08, Teng Wu <gigadevice2025@gmail.com> wrote:

> GD5F1GM9 supports a high-speed Continuous Read (CR) mode which allows
> the entire memory array to be read out by a single read command
> without re-issuing the 13h “Page Read to Cache” command for every page.
>
> Datasheet summary
> Feature register B0[3] (NR bit)
> 1 = Normal Read (default)
> 0 = Continuous Read (CR)
>
> ECC status register 7Ch
> Normal read: bits [3:0] → ECC status of last page
> Continuous read: bits [7:4] → accumulated max bit-flips over the
> whole sequential read operation.
>
> Datasheet:
> https://github.com/WT-886/DATASHEET/blob/main/GD5F1GM9-v1.0.pdf
>
> Signed-off-by: Teng Wu <gigadevice2025@gmail.com>
> ---

I am happy to see more defines benefiting from this feature! Would you
mind sharing the result of a speed test?
`flash_speed -c10 -d /dev/mtdx`

Thanks!
Miquèl

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2025-08-24 16:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-18 13:52 [PATCH] mtd: spinand: gigadevice: Add continuous read support Teng Wu
2025-08-24 16:30 ` Miquel Raynal [this message]
2025-09-01 12:28 ` Miquel Raynal
  -- strict thread matches above, loose matches on Subject: below --
2025-08-18 13:51 Teng Wu

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=87349gisw4.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=gigadevice2025@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --cc=teng.wu@gigadevice.com \
    --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;
as well as URLs for NNTP newsgroup(s).