From: Mehmet Fide <mehmet.fide@gmail.com>
To: Miquel Raynal <miquel.raynal@bootlin.com>
Cc: Mehmet Fide <mehmet.fide@gmail.com>,
Stefan Agner <stefan@agner.ch>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Boris Brezillon <bbrezillon@kernel.org>,
Frieder Schrempf <frieder.schrempf@kontron.de>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] mtd: rawnand: vf610_nfc: fix false bitflips on reads of erased pages
Date: Mon, 31 Aug 2026 13:40:00 +0200 [thread overview]
Message-ID: <20260831114000.1844796-3-mehmet.fide@gmail.com> (raw)
In-Reply-To: <871pbed8mc.fsf@bootlin.com>
Hi Miquel,
> chip.ecc.size is not covering the whole data buffer. You should be
> reading mtd->writesize + mtd->oobsize, no? Otherwise you only overwrite
> the first ECC step (out of 2/4/8 depending on the configuration of
> the ECC engine).
On this controller there is only ever one step: attach_chip() rejects
any hwecc setup where ecc.size differs from the page size ("Step size
needs to be page size") and the engine protects the whole page in one
go, so ecc.size always equals the full data area here. But you are
right that mtd->writesize says that much more clearly, so I will use it
in v3.
> Unrelated, but this comment is wrong, we accept up to <strength>
> bitflips. Not a big deal though, the impact is very limited.
I will reword that comment in v3 to match what the code actually passes
(the driver's historic threshold of half the strength). If you would
rather see the threshold itself aligned to <strength>, I can send that
as a separate cleanup so it does not hide in a fix.
Thanks,
Mehmet
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2026-08-31 11:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-28 8:53 [PATCH v2 0/2] mtd: rawnand: vf610_nfc: fix reads on chips with more than 64 bytes of OOB Mehmet Fide
2026-08-28 8:53 ` [PATCH v2 1/2] " Mehmet Fide
2026-08-31 8:04 ` Miquel Raynal
2026-08-31 11:39 ` Mehmet Fide
2026-08-31 12:26 ` Miquel Raynal
2026-08-28 8:53 ` [PATCH v2 2/2] mtd: rawnand: vf610_nfc: fix false bitflips on reads of erased pages Mehmet Fide
2026-08-31 7:58 ` Miquel Raynal
2026-08-31 11:40 ` Mehmet Fide [this message]
2026-08-31 12:23 ` Miquel Raynal
2026-08-31 8:07 ` [PATCH v2 0/2] mtd: rawnand: vf610_nfc: fix reads on chips with more than 64 bytes of OOB Miquel Raynal
2026-08-31 11:39 ` Mehmet Fide
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=20260831114000.1844796-3-mehmet.fide@gmail.com \
--to=mehmet.fide@gmail.com \
--cc=bbrezillon@kernel.org \
--cc=frieder.schrempf@kontron.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=stefan@agner.ch \
--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