From: Pratyush Yadav <pratyush@kernel.org>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Tudor Ambarus <tudor.ambarus@linaro.org>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <mwalle@kernel.org>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Steam Lin <STLin2@winbond.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 0/2] mtd: spi-nor: winbond: Add support for flashes with several dies
Date: Mon, 03 Feb 2025 14:28:24 +0000 [thread overview]
Message-ID: <mafs0a5b3je5z.fsf@kernel.org> (raw)
In-Reply-To: <20250110-winbond-6-12-rc1-nor-volatile-bit-v3-0-735363f8cc7d@bootlin.com> (Miquel Raynal's message of "Fri, 10 Jan 2025 15:49:29 +0100")
On Fri, Jan 10 2025, Miquel Raynal wrote:
> Some Winbond devices are made of up smaller stacked dies, like for
> instance W25Q01JV which is a 1G-bit serial flash memory made of two
> 512M-bit dies, and W25Q02JV which is made of four of them. Internally,
> the dies can either be in the active state (only one at a time), the
> others being in the idle state. Problem: there are commands impacting
> all 4 dies, for which we monitor the state of the chip reading the
> status register, but the status register only gives the status of the
> active die. It was observed a possible internal deviation of up to 200us
> between each die when doing similar operations, which can lead to
> races. This series aims at supporting these chips properly.
Applied to spi-nor/next. Thanks!
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2025-02-03 14:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-10 14:49 [PATCH v3 0/2] mtd: spi-nor: winbond: Add support for flashes with several dies Miquel Raynal
2025-01-10 14:49 ` [PATCH v3 1/2] mtd: spi-nor: winbond: Add support for w25q01jv Miquel Raynal
2025-01-29 15:39 ` Pratyush Yadav
2025-01-10 14:49 ` [PATCH v3 2/2] mtd: spi-nor: winbond: Add support for w25q02jv Miquel Raynal
2025-01-29 15:39 ` Pratyush Yadav
2025-02-03 14:28 ` Pratyush Yadav [this message]
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=mafs0a5b3je5z.fsf@kernel.org \
--to=pratyush@kernel.org \
--cc=STLin2@winbond.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mwalle@kernel.org \
--cc=richard@nod.at \
--cc=thomas.petazzoni@bootlin.com \
--cc=tudor.ambarus@linaro.org \
--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