target/linux/bmips/patches-5.10/203-nand-brcmnand-fix-OOB-R-W-with-Hamming-ECC.patch

   1 From cf0d2fbaae9e962d91a321de75e0d4f9f9ccbdfe Mon Sep 17 00:00:00 2001
   2 From: =?UTF-8?q?=C3=81lvaro=20Fern=C3=A1ndez=20Rojas?= <noltari@gmail.com>
   3 Date: Thu, 21 Jan 2021 18:17:37 +0100
   4 Subject: [PATCH] nand: brcmnand: fix OOB R/W with Hamming ECC
   5 MIME-Version: 1.0
   6 Content-Type: text/plain; charset=UTF-8
   7 Content-Transfer-Encoding: 8bit
   8
   9 Hamming ECC doesn't cover the OOB data, so reading or writing OOB shall
  10 always be done without ECC enabled.
  11 This is a problem when adding JFFS2 cleanmarkers to erased blocks. When JFFS2
  12 clenmarkers are added to the OOB with ECC enabled, OOB bytes will be changed
  13 from ff ff ff to 00 00 00, reporting incorrect ECC errors.
  14
  15 Signed-off-by: Álvaro Fernández Rojas <noltari@gmail.com>
  16 ---
  17  drivers/mtd/nand/raw/brcmnand/brcmnand.c | 6 ++++++
  18  1 file changed, 6 insertions(+)
  19
  20 --- a/drivers/mtd/nand/raw/brcmnand/brcmnand.c
  21 +++ b/drivers/mtd/nand/raw/brcmnand/brcmnand.c
  22 @@ -2688,6 +2688,12 @@ static int brcmnand_attach_chip(struct n
  23
  24         ret = brcmstb_choose_ecc_layout(host);
  25
  26 +       /* If OOB is written with ECC enabled it will cause ECC errors */
  27 +       if (is_hamming_ecc(host->ctrl, &host->hwcfg)) {
  28 +               chip->ecc.write_oob = brcmnand_write_oob_raw;
  29 +               chip->ecc.read_oob = brcmnand_read_oob_raw;
  30 +       }
  31 +
  32         return ret;
  33  }
  34