All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Richard Weinberger <richard@nod.at>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Tudor Ambarus <Tudor.Ambarus@microchip.com>,
	<linux-mtd@lists.infradead.org>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>
Subject: [PATCH 08/19] mtd: rawnand: fsmc: Move the ECC initialization to ->attach_chip()
Date: Fri, 13 Nov 2020 13:34:13 +0100	[thread overview]
Message-ID: <20201113123424.32233-9-miquel.raynal@bootlin.com> (raw)
In-Reply-To: <20201113123424.32233-1-miquel.raynal@bootlin.com>

The probe function is only supposed to initialize the controller
hardware but not the ECC engine. Indeed, we don't know anything about
the NAND chip(s) at this stage. Let's move the logic initializing the
ECC engine, even pretty simple, to the ->attach_chip() hook which gets
called during nand_scan() routine, after the NAND chip discovery. As
the previously mentioned logic is supposed to parse the DT for us, it
is likely that the chip->ecc.* entries be overwritten. So let's avoid
this by moving these lines to ->attach_chip().

Fixes: d7157ff49a5b ("mtd: rawnand: Use the ECC framework user input parsing bits")
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
---
 drivers/mtd/nand/raw/fsmc_nand.c | 30 +++++++++++++++---------------
 1 file changed, 15 insertions(+), 15 deletions(-)

diff --git a/drivers/mtd/nand/raw/fsmc_nand.c b/drivers/mtd/nand/raw/fsmc_nand.c
index d0855d4f5627..0101c0fab50a 100644
--- a/drivers/mtd/nand/raw/fsmc_nand.c
+++ b/drivers/mtd/nand/raw/fsmc_nand.c
@@ -879,6 +879,20 @@ static int fsmc_nand_attach_chip(struct nand_chip *nand)
 	struct mtd_info *mtd = nand_to_mtd(nand);
 	struct fsmc_nand_data *host = nand_to_fsmc(nand);
 
+	if (nand->ecc.engine_type == NAND_ECC_ENGINE_TYPE_INVALID)
+		nand->ecc.engine_type = NAND_ECC_ENGINE_TYPE_ON_HOST;
+
+	if (!nand->ecc.size)
+		nand->ecc.size = 512;
+
+	if (AMBA_REV_BITS(host->pid) >= 8) {
+		nand->ecc.read_page = fsmc_read_page_hwecc;
+		nand->ecc.calculate = fsmc_read_hwecc_ecc4;
+		nand->ecc.correct = fsmc_bch8_correct_data;
+		nand->ecc.bytes = 13;
+		nand->ecc.strength = 8;
+	}
+
 	if (AMBA_REV_BITS(host->pid) >= 8) {
 		switch (mtd->oobsize) {
 		case 16:
@@ -904,6 +918,7 @@ static int fsmc_nand_attach_chip(struct nand_chip *nand)
 		dev_info(host->dev, "Using 1-bit HW ECC scheme\n");
 		nand->ecc.calculate = fsmc_read_hwecc_ecc1;
 		nand->ecc.correct = rawnand_sw_hamming_correct;
+		nand->ecc.hwctl = fsmc_enable_hwecc;
 		nand->ecc.bytes = 3;
 		nand->ecc.strength = 1;
 		nand->ecc.options |= NAND_ECC_SOFT_HAMMING_SM_ORDER;
@@ -1054,13 +1069,6 @@ static int __init fsmc_nand_probe(struct platform_device *pdev)
 
 	mtd->dev.parent = &pdev->dev;
 
-	/*
-	 * Setup default ECC mode. nand_dt_init() called from nand_scan_ident()
-	 * can overwrite this value if the DT provides a different value.
-	 */
-	nand->ecc.engine_type = NAND_ECC_ENGINE_TYPE_ON_HOST;
-	nand->ecc.hwctl = fsmc_enable_hwecc;
-	nand->ecc.size = 512;
 	nand->badblockbits = 7;
 
 	if (host->mode == USE_DMA_ACCESS) {
@@ -1083,14 +1091,6 @@ static int __init fsmc_nand_probe(struct platform_device *pdev)
 		nand->options |= NAND_KEEP_TIMINGS;
 	}
 
-	if (AMBA_REV_BITS(host->pid) >= 8) {
-		nand->ecc.read_page = fsmc_read_page_hwecc;
-		nand->ecc.calculate = fsmc_read_hwecc_ecc4;
-		nand->ecc.correct = fsmc_bch8_correct_data;
-		nand->ecc.bytes = 13;
-		nand->ecc.strength = 8;
-	}
-
 	nand_controller_init(&host->base);
 	host->base.ops = &fsmc_nand_controller_ops;
 	nand->controller = &host->base;
-- 
2.20.1


______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  parent reply	other threads:[~2020-11-13 12:35 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-13 12:34 [PATCH 00/19] Ensure good ECC settings Miquel Raynal
2020-11-13 12:34 ` [PATCH 01/19] mtd: rawnand: gpio: Move the ECC initialization to ->attach_chip() Miquel Raynal
2020-11-19 20:48   ` Miquel Raynal
2020-11-13 12:34 ` [PATCH 02/19] mtd: rawnand: xway: " Miquel Raynal
2020-11-19 20:48   ` Miquel Raynal
2020-11-13 12:34 ` [PATCH 03/19] mtd: rawnand: ams-delta: " Miquel Raynal
2020-11-19 20:47   ` Miquel Raynal
2020-11-13 12:34 ` [PATCH 04/19] mtd: rawnand: au1550: " Miquel Raynal
2020-11-19 20:47   ` Miquel Raynal
2020-11-13 12:34 ` [PATCH 05/19] mtd: rawnand: cs553x: " Miquel Raynal
2020-11-13 12:34 ` [PATCH 06/19] mtd: rawnand: davinci: " Miquel Raynal
2020-11-19 20:47   ` Miquel Raynal
2020-11-13 12:34 ` [PATCH 07/19] mtd: rawnand: diskonchip: " Miquel Raynal
2020-11-19 20:47   ` Miquel Raynal
2020-11-13 12:34 ` Miquel Raynal [this message]
2020-11-13 12:34 ` [PATCH 09/19] mtd: rawnand: lpc32xx_mlc: " Miquel Raynal
2020-11-19 20:47   ` Miquel Raynal
2020-11-13 12:34 ` [PATCH 10/19] mtd: rawnand: lpc32xx_slc: " Miquel Raynal
2020-11-13 12:34 ` [PATCH 11/19] mtd: rawnand: mpc5121: " Miquel Raynal
2020-11-19 20:47   ` Miquel Raynal
2020-11-13 12:34 ` [PATCH 12/19] mtd: rawnand: orion: " Miquel Raynal
2020-11-19 20:47   ` Miquel Raynal
2020-11-13 12:34 ` [PATCH 13/19] mtd: rawnand: txx9ndfmc: " Miquel Raynal
2020-11-19 20:47   ` Miquel Raynal
2020-11-13 12:34 ` [PATCH 14/19] mtd: rawnand: tmio: " Miquel Raynal
2020-11-19 20:47   ` Miquel Raynal
2020-11-13 12:34 ` [PATCH 15/19] mtd: rawnand: pasemi: " Miquel Raynal
2020-11-19 20:47   ` Miquel Raynal
2020-11-13 12:34 ` [PATCH 16/19] mtd: rawnand: plat_nand: " Miquel Raynal
2020-11-19 20:46   ` Miquel Raynal
2020-11-13 12:34 ` [PATCH 17/19] mtd: rawnand: r852: " Miquel Raynal
2020-11-19 20:46   ` Miquel Raynal
2020-11-30  1:07   ` Nathan Chancellor
2020-11-30  8:04     ` Miquel Raynal
2020-11-13 12:34 ` [PATCH 18/19] mtd: rawnand: sharpsl: " Miquel Raynal
2020-11-13 12:34 ` [PATCH 19/19] mtd: rawnand: socrates: " Miquel Raynal
2020-11-19 20:46   ` 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=20201113123424.32233-9-miquel.raynal@bootlin.com \
    --to=miquel.raynal@bootlin.com \
    --cc=Tudor.Ambarus@microchip.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    --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.