From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: linux-mtd@lists.infradead.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org
Subject: Re: Kernel 5.10-rc1 not mounting NAND flash (Bisected to d7157ff49a5b ("mtd: rawnand: Use the ECC framework user input parsing bits"))
Date: Thu, 5 Nov 2020 10:13:19 +0100 [thread overview]
Message-ID: <20201105101319.644782a6@xps13> (raw)
In-Reply-To: <20201105100651.Horde.jOAklfLApjH2WjmauwW9Gg1@messagerie.c-s.fr>
Hi Christophe,
Christophe Leroy <christophe.leroy@csgroup.eu> wrote on Thu, 05 Nov
2020 10:06:51 +0100:
> Quoting Miquel Raynal <miquel.raynal@bootlin.com>:
>
> > Hi Christophe,
> >
> > Christophe Leroy <christophe.leroy@csgroup.eu> wrote on Wed, 4 Nov 2020
> > 19:37:57 +0100:
> >
> >> Hi Miquel,
> >>
> >> Le 04/11/2020 à 18:38, Miquel Raynal a écrit :
> >> > Hi Christophe,
> >> >
> >> > Christophe Leroy <christophe.leroy@csgroup.eu> wrote on Wed, 04 Nov
> >> > 2020 18:33:53 +0100:
> >> >
> >> >> Hi Miquel,
> >> >>
> >> >> I'm unable to boot 5.10-rc1 on my boards. I get the following error:
> >> >>
> >> >> [ 4.125811] nand: device found, Manufacturer ID: 0xad, Chip ID: 0x
> 76
> >> >> [ 4.131992] nand: Hynix NAND 64MiB 3,3V 8-bit
> >> >> [ 4.136173] nand: 64 MiB, SLC, erase size: 16 KiB, page size:>> 512, OOB size: 16
> >> >> [ 4.143534] ------------[ cut here ]------------
> >> >> [ 4.147934] Unsupported ECC algorithm!
> >> >> [ 4.152142] WARNING: CPU: 0 PID: 1 at >> drivers/mtd/nand/raw/nand_base.c:5244 >> nand_scan_with_ids+0x1260/0x1640
> >> >> ...
> >> >> [ 4.332052] ---[ end trace e3a36f62cae4ac56 ]---
> >> >> [ 4.336882] gpio-nand: probe of c0000000.nand failed with error -2
> 2
> >> >>
> >> >> Bisected to commit d7157ff49a5b ("mtd: rawnand: Use the ECC >> framework user input parsing bits")
> >> >>
> >> >> My first impression is that with that change, the value set in >> chip->ecc.algo
> >> >> by gpio_nand_probe() in drivers/mtd/nand/raw/gpio.c gets >> overwritten in rawnand_dt_init()
> >> >>
> >> >> The following change fixes the problem, though I'm not sure it >> is the right fix. Can you have a look ?
> >> >>
> >> >> diff --git a/drivers/mtd/nand/raw/nand_base.c >> b/drivers/mtd/nand/raw/nand_base.c
> >> >> index 1f0d542d5923..aa74797cf2da 100644
> >> >> --- a/drivers/mtd/nand/raw/nand_base.c
> >> >> +++ b/drivers/mtd/nand/raw/nand_base.c
> >> >> @@ -5032,7 +5032,8 @@ static int rawnand_dt_init(struct nand_chip *ch
> ip)
> >> >> chip->ecc.engine_type = nand->ecc.defaults.engine_type;
> >> >>
> >> >> chip->ecc.placement = nand->ecc.user_conf.placement;
> >> >> - chip->ecc.algo = nand->ecc.user_conf.algo;
> >> >> + if (chip->ecc.algo == NAND_ECC_ALGO_UNKNOWN)
> >> >> + chip->ecc.algo = nand->ecc.user_conf.algo;
> >> >> chip->ecc.strength = nand->ecc.user_conf.strength;
> >> >> chip->ecc.size = nand->ecc.user_conf.step_size;
> >> >>
> >> >> ---
> >> >>
> >> >> Thanks
> >> >> Christophe
> >> >
> >> > Sorry for introducing this issue, I didn't had the time to send the
> >> > Fixes PR yet but I think this issue has been solved already. Could
> >> > you please try with a recent linux-next?
> >> >
> >>
> >> Sorry, same problem with "Linux version 5.10.0-rc2-next-20201104"
> >
> > Can you please give this patch a try, please?
> >
> > ---8<---
> >
> > Author: Miquel Raynal <miquel.raynal@bootlin.com>
> > Date: Thu Nov 5 08:44:48 2020 +0100
> >
> > mtd: rawnand: gpio: Move the ECC initialization to ->attach_chip()
> >
> > While forcing a Hamming software ECC looks clearly wrong, let's just
> > fix the situation for now and move these lines to the ->attach_chip()
> > hook which gets executed after the user input parsing and NAND chip
> > discovery.
> >
> > Fixes: d7157ff49a5b ("mtd: rawnand: Use the ECC framework user > input parsing bits")
> > Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> >
> > diff --git a/drivers/mtd/nand/raw/gpio.c b/drivers/mtd/nand/raw/gpio.c
> > index 3bd847ccc3f3..6feab847f5e0 100644
> > --- a/drivers/mtd/nand/raw/gpio.c
> > +++ b/drivers/mtd/nand/raw/gpio.c
> > @@ -161,8 +161,15 @@ static int gpio_nand_exec_op(struct nand_chip *chip,
> > return ret;
> > }
> >
> > +static int gpio_nand_attach_chip(struct nand_chip *chip)
> > +{
> > + chip->ecc.mode = NAND_ECC_SOFT;
> > + chip->ecc.algo = NAND_ECC_HAMMING;
> > +}
> > +
> > static const struct nand_controller_ops gpio_nand_ops = {
> > .exec_op = gpio_nand_exec_op,
> > + .attach_chip = gpio_nand_attach_chip,
> > };
> >
> > #ifdef CONFIG_OF
> > @@ -342,8 +349,6 @@ static int gpio_nand_probe(struct platform_device *pd
> ev)
> > gpiomtd->base.ops = &gpio_nand_ops;
> >
> > nand_set_flash_node(chip, pdev->dev.of_node);
> > - chip->ecc.mode = NAND_ECC_SOFT;
> > - chip->ecc.algo = NAND_ECC_HAMMING;
> > chip->options = gpiomtd->plat.options;
> > chip->controller = &gpiomtd->base;
>
>
> Works with the following:
>
> diff --git a/drivers/mtd/nand/raw/gpio.c b/drivers/mtd/nand/raw/gpio.c
> index 4ec0a1e10867..66d3f1eb788c 100644
> --- a/drivers/mtd/nand/raw/gpio.c
> +++ b/drivers/mtd/nand/raw/gpio.c
> @@ -161,8 +161,17 @@ static int gpio_nand_exec_op(struct nand_chip *chip,
> return ret;
> }
>
> +static int gpio_nand_attach_chip(struct nand_chip *chip)
> +{
> + chip->ecc.engine_type = NAND_ECC_ENGINE_TYPE_SOFT;
> + chip->ecc.algo = NAND_ECC_ALGO_HAMMING;
> +
> + return 0;
> +}
Yup indeed it was not even compile tested. Good to know, I'll check
the other drivers and send the patch soon.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2020-11-05 9:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 17:33 Kernel 5.10-rc1 not mounting NAND flash (Bisected to d7157ff49a5b ("mtd: rawnand: Use the ECC framework user input parsing bits")) Christophe Leroy
2020-11-04 17:38 ` Miquel Raynal
2020-11-04 18:37 ` Christophe Leroy
2020-11-05 7:49 ` Miquel Raynal
2020-11-05 9:06 ` Christophe Leroy
2020-11-05 9:13 ` Miquel Raynal [this message]
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=20201105101319.644782a6@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=christophe.leroy@csgroup.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linuxppc-dev@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).