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>,
Michael Trimarchi <michael@amarulasolutions.com>
Subject: Re: [PATCH] mtd: spinor: winbond: Describe several chips
Date: Thu, 13 Nov 2025 10:50:34 +0100 [thread overview]
Message-ID: <875xbegt1x.fsf@bootlin.com> (raw)
In-Reply-To: <87frcwexyt.fsf@bootlin.com> (Miquel Raynal's message of "Tue, 09 Sep 2025 12:12:26 +0200")
Hi,
I am manually adding Michael, as apparently he was not listed
automatically.
On 09/09/2025 at 12:12:26 +02, Miquel Raynal <miquel.raynal@bootlin.com> wrote:
> 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?
It's now been few more months and I haven't been notified this patch got
merged. It is also not visible in upstream U-Boot. Could we please speed
up the merging process, especially for such simple change?
Thanks,
Miquèl
next prev parent reply other threads:[~2025-11-13 13:17 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
2025-11-13 9:50 ` Miquel Raynal [this message]
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=875xbegt1x.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=jagan@amarulasolutions.com \
--cc=michael@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox