All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Jagan Teki <jagan@amarulasolutions.com>
Cc: Vignesh R <vigneshr@ti.com>,
	 Tudor Ambarus <tudor.ambarus@linaro.org>,
	Tom Rini <trini@konsulko.com>,  <u-boot@lists.denx.de>,
	 Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	 Steam Lin <stlin2@winbond.com>
Subject: Re: [PATCH] mtd: spinor: winbond: Describe several chips
Date: Tue, 09 Sep 2025 12:12:26 +0200	[thread overview]
Message-ID: <87frcwexyt.fsf@bootlin.com> (raw)
In-Reply-To: <20250703170253.1231818-1-miquel.raynal@bootlin.com> (Miquel Raynal's message of "Thu, 3 Jul 2025 19:02:53 +0200")

Hello,

On 03/07/2025 at 19:02:53 +02, Miquel Raynal <miquel.raynal@bootlin.com> wrote:

> All these chips are dual and quad capable. They are also DTR capable,
> but the core is not yet ready for that.
>
> Performances of all chips are comparable at 30MHz and are as follow:
> Eraseblock single read speed: 938kiB/s
> Eraseblock dual read speed:  1068kiB/s
> Eraseblock quad read speed:  3751kiB/s
>
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>

I believe this patch has been out for more than 2 months and is simple
enough, any plans for taking it soon?

Thanks,
Miquèl

  reply	other threads:[~2025-09-09 13:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-03 17:02 [PATCH] mtd: spinor: winbond: Describe several chips Miquel Raynal
2025-09-09 10:12 ` Miquel Raynal [this message]
2025-11-13  9:50   ` Miquel Raynal
2025-11-13 14:27     ` Tom Rini
2025-11-13 14:36       ` Michael Nazzareno Trimarchi
2025-11-18 14:34         ` Tom Rini
2025-11-18 14:43           ` Michael Nazzareno Trimarchi
2025-11-19  9:06             ` Michael Nazzareno Trimarchi
2025-11-19 10:01               ` Miquel Raynal
2025-11-19 10:08                 ` Michael Nazzareno Trimarchi
2025-11-19 20:55                   ` Tom Rini

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=87frcwexyt.fsf@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=jagan@amarulasolutions.com \
    --cc=stlin2@winbond.com \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=trini@konsulko.com \
    --cc=tudor.ambarus@linaro.org \
    --cc=u-boot@lists.denx.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.