From: Sascha Hauer <s.hauer@pengutronix.de>
To: linux-mtd@lists.infradead.org
Cc: miquel.raynal@bootlin.com
Subject: nand_ecc_is_strong_enough() doesn't trigger
Date: Thu, 11 Apr 2024 12:06:30 +0200 [thread overview]
Message-ID: <Zhe2JtvvN1M4Ompw@pengutronix.de> (raw)
Hi,
I am currently working with a NAND chip requiring 4 bit correction per
512 byte data while my NAND driver only supports 1 bit correction, so
I would assume this to trigger:
/* ECC sanity check: warn if it's too weak */
if (!nand_ecc_is_strong_enough(&chip->base))
pr_warn("WARNING: %s: the ECC used on your system (%db/%dB) is too weak compared to the one required by the NAND chip (%db/%dB)\n",
mtd->name, chip->ecc.strength, chip->ecc.size,
nanddev_get_ecc_requirements(&chip->base)->strength,
nanddev_get_ecc_requirements(&chip->base)->step_size);
nand_ecc_is_strong_enough() works on nand->ecc.ctx.conf.step_size, but
this only ever seems to be initialized by the various ecc-sw-*
algorithms.
This was changed in 8c126720fe10 ("mtd: rawnand: Use the ECC framework
nand_ecc_is_strong_enough() helper"). Before this patch the initialized
values in &(struct nand_chip *chip)->ecc were used (and which are still
used in the warning message above).
Do you have a direction how this should be fixed?
Thanks
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2024-04-11 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 10:06 Sascha Hauer [this message]
2024-05-07 12:30 ` nand_ecc_is_strong_enough() doesn't trigger 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=Zhe2JtvvN1M4Ompw@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.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.