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>,  Tom Rini <trini@konsulko.com>,
	 Steam Lin <stlin2@winbond.com>,
	 Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
	<u-boot@lists.denx.de>
Subject: Re: [PATCH] mtd: spi-nor: winbond: Make sure w25q{01,02}jv behave correctly
Date: Tue, 09 Sep 2025 12:13:55 +0200	[thread overview]
Message-ID: <87a534exwc.fsf@bootlin.com> (raw)
In-Reply-To: <20250702092313.970234-1-miquel.raynal@bootlin.com> (Miquel Raynal's message of "Wed, 2 Jul 2025 11:23:13 +0200")

Hello,

On 02/07/2025 at 11:23:13 +02, Miquel Raynal <miquel.raynal@bootlin.com> wrote:

> These chips are internally made of two/four dies with linear addressing
> capabilities to make it transparent to the user that two/four dies were
> used. There is one drawback however, the read status operation is racy
> as the status bit only gives the active die status and not the status of
> the other die. For commands affecting the two dies, it means if another
> command is sent too fast after the first die has returned a valid
> status (deviation can be up to 200us), the chip will get corrupted/in an
> unstable state.
>
> The solution adopted here is to iterate manually over all internal
> dies (which takes about 30us per die) until all are ready. This approach
> will always be faster than a blind delay which represents the maximum
> deviation, while also being totally safe.
>
> A flash-specific hook for the status register read had to be
> implemented. Testing with the flash_speed benchmark in Linux shown no
> difference with the existing performances (using the regular status read
> core function).
>
> As the presence of multiple dies is not filled in these chips SFDP
> tables (the table containing the crucial information is optional), we
> need to manually wire the hook.
>
> This change is adapted from Linux.
>
> Link: https://lore.kernel.org/all/20250110-winbond-6-12-rc1-nor-volatile-bit-v3-1-735363f8cc7d@bootlin.com/
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>

Same question for this one, no feedback for the past 2 months, I'm not
sure who's supposed to take these, Jagan and Vignesh you are marked M:
in maintainers, any chances this can get it?

Thanks a lot,
Miquèl

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02  9:23 [PATCH] mtd: spi-nor: winbond: Make sure w25q{01, 02}jv behave correctly Miquel Raynal
2025-09-09 10:13 ` Miquel Raynal [this message]
2025-09-09 12:07   ` Jagan Teki
2025-09-09 12:30     ` [PATCH] mtd: spi-nor: winbond: Make sure w25q{01,02}jv " Miquel Raynal
2025-09-09 17:08     ` Raghavendra, Vignesh
2025-09-10  5:28       ` [PATCH] mtd: spi-nor: winbond: Make sure w25q{01, 02}jv " Michael Nazzareno Trimarchi
2025-11-13  9:44         ` [PATCH] mtd: spi-nor: winbond: Make sure w25q{01,02}jv " Miquel Raynal
2026-02-13 20:16 ` [PATCH] mtd: spi-nor: winbond: Make sure w25q{01, 02}jv " 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=87a534exwc.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=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.