From: Md Sadre Alam <md.alam@oss.qualcomm.com>
To: Mark Brown <broonie@kernel.org>
Cc: linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org,
Md Sadre Alam <md.alam@oss.qualcomm.com>
Subject: [PATCH] spi: spi-qpic-snand: Increase ECC strength for large OOB SPI-NAND devices
Date: Thu, 16 Jul 2026 11:13:05 +0530 [thread overview]
Message-ID: <20260716-8bitecc-v1-1-6eef4bcc3a14@oss.qualcomm.com> (raw)
Some SPI-NAND devices with large OOB areas require a stronger ECC
configuration than the default one provided through firmware
description. For example, Macronix devices with a 256-byte OOB area
report that 4-bit ECC is insufficient and trigger:
nand: WARNING: the ECC used on your system is too weak compared
to the one required by the NAND chip
The QPIC SPI-NAND controller supports both 4-bit and 8-bit BCH ECC
modes. When a device exposes an OOB area of at least 128 bytes, there
is sufficient space to accommodate 8-bit ECC without exceeding the OOB
layout constraints.
Automatically increase the ECC strength to 8 bits when the detected OOB
size is 128 bytes or larger and the current configuration requests a
weaker ECC level. This avoids ECC capability mismatches on devices that
require stronger error correction and improves reliability.
Signed-off-by: Md Sadre Alam <md.alam@oss.qualcomm.com>
---
drivers/spi/spi-qpic-snand.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/drivers/spi/spi-qpic-snand.c b/drivers/spi/spi-qpic-snand.c
index 6cc53586b8a8..19812400124f 100644
--- a/drivers/spi/spi-qpic-snand.c
+++ b/drivers/spi/spi-qpic-snand.c
@@ -274,6 +274,19 @@ static int qcom_spi_ecc_init_ctx_pipelined(struct nand_device *nand)
ecc_cfg->strength = 4;
}
+ /*
+ * Override ECC strength based on OOB size to avoid weak ECC warning.
+ * If OOB size is more than 128 bytes, use 8-bit ECC for better
+ * error correction capability, which is required by chips with
+ * larger OOB areas like Macronix SPI NAND with 256 bytes OOB.
+ */
+ if (mtd->oobsize >= 128 && ecc_cfg->strength < 8) {
+ dev_info(snandc->dev,
+ "Upgrading ECC strength from %d to 8 bits (OOB size: %d bytes)\n",
+ ecc_cfg->strength, mtd->oobsize);
+ ecc_cfg->strength = 8;
+ }
+
if (ecc_cfg->step_size != NANDC_STEP_SIZE) {
dev_err(snandc->dev,
"only %u bytes ECC step size is supported\n",
---
base-commit: 19827e7930a5511c68e12aac6e4522f3661a1709
change-id: 20260716-8bitecc-b9be3d2e7690
Best regards,
--
Md Sadre Alam <md.alam@oss.qualcomm.com>
reply other threads:[~2026-07-16 5:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260716-8bitecc-v1-1-6eef4bcc3a14@oss.qualcomm.com \
--to=md.alam@oss.qualcomm.com \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
/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