From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <michael@walle.cc>, <linux-mtd@lists.infradead.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Michal Simek <michal.simek@amd.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 2/3] mtd: rawnand: arasan: Ensure program page operations are successful
Date: Mon, 11 Sep 2023 17:52:47 +0200 [thread overview]
Message-ID: <20230911175247.44c1d894@xps-13> (raw)
In-Reply-To: <20230717194221.229778-2-miquel.raynal@bootlin.com>
Hi Michal,
miquel.raynal@bootlin.com wrote on Mon, 17 Jul 2023 21:42:20 +0200:
> The NAND core complies with the ONFI specification, which itself
> mentions that after any program or erase operation, a status check
> should be performed to see whether the operation was finished *and*
> successful.
>
> The NAND core offers helpers to finish a page write (sending the
> "PAGE PROG" command, waiting for the NAND chip to be ready again, and
> checking the operation status). But in some cases, advanced controller
> drivers might want to optimize this and craft their own page write
> helper to leverage additional hardware capabilities, thus not always
> using the core facilities.
>
> Some drivers, like this one, do not use the core helper to finish a page
> write because the final cycles are automatically managed by the
> hardware. In this case, the additional care must be taken to manually
> perform the final status check.
>
> Let's read the NAND chip status at the end of the page write helper and
> return -EIO upon error.
>
> Cc: Michal Simek <michal.simek@amd.com>
> Cc: stable@vger.kernel.org
> Fixes: 88ffef1b65cf ("mtd: rawnand: arasan: Support the hardware BCH ECC engine")
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
>
> ---
>
> Hello Michal,
>
> I have not tested this, but based on a report on another driver, I
> believe the status check is also missing here and could sometimes
> lead to unnoticed partial writes.
>
> Please test on your side that everything still works and let me
> know how it goes.
Any news from the testing team about patches 2/3 and 3/3?
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Pratyush Yadav <pratyush@kernel.org>,
Michael Walle <michael@walle.cc>, <linux-mtd@lists.infradead.org>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
Michal Simek <michal.simek@amd.com>,
stable@vger.kernel.org
Subject: Re: [PATCH 2/3] mtd: rawnand: arasan: Ensure program page operations are successful
Date: Mon, 11 Sep 2023 17:52:47 +0200 [thread overview]
Message-ID: <20230911175247.44c1d894@xps-13> (raw)
In-Reply-To: <20230717194221.229778-2-miquel.raynal@bootlin.com>
Hi Michal,
miquel.raynal@bootlin.com wrote on Mon, 17 Jul 2023 21:42:20 +0200:
> The NAND core complies with the ONFI specification, which itself
> mentions that after any program or erase operation, a status check
> should be performed to see whether the operation was finished *and*
> successful.
>
> The NAND core offers helpers to finish a page write (sending the
> "PAGE PROG" command, waiting for the NAND chip to be ready again, and
> checking the operation status). But in some cases, advanced controller
> drivers might want to optimize this and craft their own page write
> helper to leverage additional hardware capabilities, thus not always
> using the core facilities.
>
> Some drivers, like this one, do not use the core helper to finish a page
> write because the final cycles are automatically managed by the
> hardware. In this case, the additional care must be taken to manually
> perform the final status check.
>
> Let's read the NAND chip status at the end of the page write helper and
> return -EIO upon error.
>
> Cc: Michal Simek <michal.simek@amd.com>
> Cc: stable@vger.kernel.org
> Fixes: 88ffef1b65cf ("mtd: rawnand: arasan: Support the hardware BCH ECC engine")
> Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
>
> ---
>
> Hello Michal,
>
> I have not tested this, but based on a report on another driver, I
> believe the status check is also missing here and could sometimes
> lead to unnoticed partial writes.
>
> Please test on your side that everything still works and let me
> know how it goes.
Any news from the testing team about patches 2/3 and 3/3?
Thanks,
Miquèl
next prev parent reply other threads:[~2023-09-11 15:54 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 19:42 [PATCH 1/3] mtd: rawnand: marvell: Ensure program page operations are successful Miquel Raynal
2023-07-17 19:42 ` Miquel Raynal
2023-07-17 19:42 ` [PATCH 2/3] mtd: rawnand: arasan: " Miquel Raynal
2023-07-17 19:42 ` Miquel Raynal
2023-09-11 15:52 ` Miquel Raynal [this message]
2023-09-11 15:52 ` Miquel Raynal
2023-09-12 13:55 ` Michal Simek
2023-09-12 13:55 ` Michal Simek
2023-09-12 14:17 ` Miquel Raynal
2023-09-12 14:17 ` Miquel Raynal
2023-09-20 7:55 ` Michal Simek
2023-09-20 7:55 ` Michal Simek
2023-09-21 10:25 ` Michal Simek
2023-09-21 10:25 ` Michal Simek
2023-09-22 9:14 ` Miquel Raynal
2023-09-22 9:14 ` Miquel Raynal
2023-09-22 9:16 ` Michal Simek
2023-09-22 9:16 ` Michal Simek
2023-09-22 9:17 ` Miquel Raynal
2023-09-22 9:17 ` Miquel Raynal
2023-09-22 14:51 ` Miquel Raynal
2023-09-22 14:51 ` Miquel Raynal
2023-07-17 19:42 ` [PATCH 3/3] mtd: rawnand: pl353: " Miquel Raynal
2023-07-17 19:42 ` Miquel Raynal
2023-09-22 14:51 ` Miquel Raynal
2023-09-22 14:51 ` Miquel Raynal
2023-08-26 13:33 ` [PATCH 1/3] mtd: rawnand: marvell: " Ravi Minnikanti
2023-08-26 13:33 ` Ravi Minnikanti
2023-09-11 15:53 ` Miquel Raynal
2023-09-11 15:53 ` Miquel Raynal
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=20230911175247.44c1d894@xps-13 \
--to=miquel.raynal@bootlin.com \
--cc=linux-mtd@lists.infradead.org \
--cc=michael@walle.cc \
--cc=michal.simek@amd.com \
--cc=pratyush@kernel.org \
--cc=richard@nod.at \
--cc=stable@vger.kernel.org \
--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 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.