From: Mikhail Kshevetskiy <mikhail.kshevetskiy@iopsys.eu>
To: David LaPorte <dalaport@amazon.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Martin Kurbanov <mmkurbanov@salutedevices.com>,
Cheng Ming Lin <chengminglin@mxic.com.tw>,
Pratyush Yadav <pratyush@kernel.org>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Gunnar Kudrjavets <gunnarku@amazon.com>
Subject: Re: [PATCH] mtd: spinand: Disable continuous read during probe
Date: Fri, 30 Jan 2026 03:05:54 +0300 [thread overview]
Message-ID: <5fc6b07f-4998-432f-9f9e-197ed08c2d16@iopsys.eu> (raw)
In-Reply-To: <20260129221606.35158-1-dalaport@amazon.com>
On 1/30/26 01:15, David LaPorte wrote:
> [You don't often get email from dalaport@amazon.com. Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
>
> Macronix serial NAND devices with continuous read support do not
> clear the configuration register on soft reset and lack a hardware
> reset pin. When continuous read is interrupted (e.g., during reboot),
> the feature remains enabled at the device level.
>
> With continuous read enabled, the OOB area becomes inaccessible and
> all reads are instead directed to the main area. As a result, during
> partition allocation as part of MTD device registration, the first two
> bytes of the main area for the master block are read and indicate that
> the block is bad. This process repeats for every subsequent block for
> the partition.
>
> All reads and writes that reference the BBT find no good blocks and
> fail.
>
> The only paths for recovery from this state are triggering the
> continuous read feature by way of raw MTD reads or through a NAND
> device power drain.
>
> Disable continuous read explicitly during spinand probe to ensure
> quiescent feature state.
>
> Fixes: 631cfdd0520d ("mtd: spi-nand: Add continuous read support")
> Signed-off-by: David LaPorte <dalaport@amazon.com>
> Reviewed-by: Gunnar Kudrjavets <gunnarku@amazon.com>
> ---
> Testing details:
> - Instrumented feature enablement and verified fix with affected Macronix
> serial NAND device: warm reboot without patch marks all blocks bad
> during partition allocation; with patch applied, device registers
> cleanly with no bad blocks marked
> - Patch cherry-picks cleanly to mainline v6.19-rc6 and builds without
> warnings
> - Boot tested mainline + patch on aarch64 host without SPI interface
> ---
> drivers/mtd/nand/spi/core.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/mtd/nand/spi/core.c b/drivers/mtd/nand/spi/core.c
> index d207286572d8..1fb05ac8678b 100644
> --- a/drivers/mtd/nand/spi/core.c
> +++ b/drivers/mtd/nand/spi/core.c
> @@ -859,6 +859,7 @@ static void spinand_cont_read_init(struct spinand_device *spinand)
> (engine_type == NAND_ECC_ENGINE_TYPE_ON_DIE ||
> engine_type == NAND_ECC_ENGINE_TYPE_NONE)) {
> spinand->cont_read_possible = true;
> + spinand_cont_read_enable(spinand, false);
I think a comment should be added here explaining why you disable
cont_read here
> }
> }
>
> --
> 2.43.0
>
prev parent reply other threads:[~2026-01-30 0:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-29 22:15 David LaPorte
2026-01-30 0:05 ` Mikhail Kshevetskiy [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=5fc6b07f-4998-432f-9f9e-197ed08c2d16@iopsys.eu \
--to=mikhail.kshevetskiy@iopsys.eu \
--cc=chengminglin@mxic.com.tw \
--cc=dalaport@amazon.com \
--cc=gunnarku@amazon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mmkurbanov@salutedevices.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--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
all inboxes | Powered by JetHome®