This is a note to let you know that I've just added the patch titled mtd: rawnand: au1550nd: Keep the driver compatible with on-die ECC engines to the 5.14-stable tree which can be found at: http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary The filename of the patch is: mtd-rawnand-au1550nd-keep-the-driver-compatible-with-on-die-ecc-engines.patch and it can be found in the queue-5.14 subdirectory. If you, or anyone else, feels it should not be added to the stable tree, please let <stable@xxxxxxxxxxxxxxx> know about it. >From 7e3cdba176ba59eaf4d463d273da0718e3626140 Mon Sep 17 00:00:00 2001 From: Miquel Raynal <miquel.raynal@xxxxxxxxxxx> Date: Wed, 29 Sep 2021 00:22:41 +0200 Subject: mtd: rawnand: au1550nd: Keep the driver compatible with on-die ECC engines From: Miquel Raynal <miquel.raynal@xxxxxxxxxxx> commit 7e3cdba176ba59eaf4d463d273da0718e3626140 upstream. Following the introduction of the generic ECC engine infrastructure, it was necessary to reorganize the code and move the ECC configuration in the ->attach_chip() hook. Failing to do that properly lead to a first series of fixes supposed to stabilize the situation. Unfortunately, this only fixed the use of software ECC engines, preventing any other kind of engine to be used, including on-die ones. It is now time to (finally) fix the situation by ensuring that we still provide a default (eg. software ECC) but will still support different ECC engines such as on-die ECC engines if properly described in the device tree. There are no changes needed on the core side in order to do this, but we just need to leverage the logic there which allows: 1- a subsystem default (set to Host engines in the raw NAND world) 2- a driver specific default (here set to software ECC engines) 3- any type of engine requested by the user (ie. described in the DT) As the raw NAND subsystem has not yet been fully converted to the ECC engine infrastructure, in order to provide a default ECC engine for this driver we need to set chip->ecc.engine_type *before* calling nand_scan(). During the initialization step, the core will consider this entry as the default engine for this driver. This value may of course be overloaded by the user if the usual DT properties are provided. Fixes: dbffc8ccdf3a ("mtd: rawnand: au1550: Move the ECC initialization to ->attach_chip()") Cc: stable@xxxxxxxxxxxxxxx Signed-off-by: Miquel Raynal <miquel.raynal@xxxxxxxxxxx> Link: https://lore.kernel.org/linux-mtd/20210928222258.199726-3-miquel.raynal@xxxxxxxxxxx Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx> --- drivers/mtd/nand/raw/au1550nd.c | 12 +++++++++--- 1 file changed, 9 insertions(+), 3 deletions(-) --- a/drivers/mtd/nand/raw/au1550nd.c +++ b/drivers/mtd/nand/raw/au1550nd.c @@ -239,9 +239,8 @@ static int au1550nd_exec_op(struct nand_ static int au1550nd_attach_chip(struct nand_chip *chip) { - chip->ecc.engine_type = NAND_ECC_ENGINE_TYPE_SOFT; - - if (chip->ecc.algo == NAND_ECC_ALGO_UNKNOWN) + if (chip->ecc.engine_type == NAND_ECC_ENGINE_TYPE_SOFT && + chip->ecc.algo == NAND_ECC_ALGO_UNKNOWN) chip->ecc.algo = NAND_ECC_ALGO_HAMMING; return 0; @@ -310,6 +309,13 @@ static int au1550nd_probe(struct platfor if (pd->devwidth) this->options |= NAND_BUSWIDTH_16; + /* + * This driver assumes that the default ECC engine should be TYPE_SOFT. + * Set ->engine_type before registering the NAND devices in order to + * provide a driver specific default value. + */ + this->ecc.engine_type = NAND_ECC_ENGINE_TYPE_SOFT; + ret = nand_scan(this, 1); if (ret) { dev_err(&pdev->dev, "NAND scan failed with %d\n", ret); Patches currently in stable-queue which might be from miquel.raynal@xxxxxxxxxxx are queue-5.14/mtd-rawnand-intel-fix-potential-buffer-overflow-in-p.patch queue-5.14/mtd-rawnand-socrates-keep-the-driver-compatible-with-on-die-ecc-engines.patch queue-5.14/mtd-rawnand-ams-delta-keep-the-driver-compatible-with-on-die-ecc-engines.patch queue-5.14/mtd-rawnand-gpio-keep-the-driver-compatible-with-on-die-ecc-engines.patch queue-5.14/mtd-rawnand-fsmc-fix-use-of-sm-order.patch queue-5.14/mtd-rawnand-au1550nd-keep-the-driver-compatible-with-on-die-ecc-engines.patch queue-5.14/mtd-rawnand-arasan-prevent-an-unsupported-configurat.patch queue-5.14/mtd-rawnand-plat_nand-keep-the-driver-compatible-with-on-die-ecc-engines.patch queue-5.14/mtd-rawnand-mpc5121-keep-the-driver-compatible-with-on-die-ecc-engines.patch queue-5.14/mtd-rawnand-orion-keep-the-driver-compatible-with-on-die-ecc-engines.patch queue-5.14/mtd-rawnand-xway-keep-the-driver-compatible-with-on-die-ecc-engines.patch queue-5.14/mtd-rawnand-pasemi-keep-the-driver-compatible-with-on-die-ecc-engines.patch queue-5.14/mtd-core-don-t-remove-debugfs-directory-if-device-is.patch