From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Fabio Estevam <festevam@gmail.com>, miquel.raynal@bootlin.com
Cc: vigneshr@ti.com, richard@nod.at, boris.brezillon@collabora.com,
linux-mtd@lists.infradead.org, kernel@pengutronix.de,
han.xu@nxp.com
Subject: Re: [PATCH v2] mtd: rawnand: ifc: Move the ECC engine initialization to the right place
Date: Mon, 26 Oct 2020 18:48:30 +0100 [thread overview]
Message-ID: <20201026184830.338fd9f7@xps13> (raw)
In-Reply-To: <20201026174525.6027-1-miquel.raynal@bootlin.com>
Hello,
Miquel Raynal <miquel.raynal@bootlin.com> wrote on Mon, 26 Oct 2020
18:45:25 +0100:
> On Fri, 2020-10-16 at 13:26:26 UTC, Fabio Estevam wrote:
> > No ECC initialization should happen during the host controller probe.
> >
> > In fact, we need the probe function to call nand_scan() in order to:
> > - identify the device, its capabilities and constraints (nand_scan_ident())
> > - configure the ECC engine accordingly (->attach_chip())
> > - scan its content and prepare the core (nand_scan_tail())
> >
> > Moving these lines to fsl_ifc_attach_chip() fixes a regression caused by
> > a previous commit supposed to clarify these steps.
> >
> > Based on a fix done for the mxc_nand driver by Miquel Raynal.
> >
> > Reported-by: Han Xu <xhnjupt@gmail.com>
> > Signed-off-by: Fabio Estevam <festevam@gmail.com>
> > Tested-by: Han Xu <xhnjupt@gmail.com>
>
> Applied to https://git.kernel.org/pub/scm/linux/kernel/git/mtd/linux.git mtd/fixes, thanks.
FYI I've added a Fixes tag.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2020-10-26 17:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 13:26 [PATCH v2] mtd: rawnand: ifc: Move the ECC engine initialization to the right place Fabio Estevam
2020-10-19 17:15 ` [EXT] " Han Xu
2020-10-26 17:45 ` Miquel Raynal
2020-10-26 17:48 ` 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=20201026184830.338fd9f7@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=boris.brezillon@collabora.com \
--cc=festevam@gmail.com \
--cc=han.xu@nxp.com \
--cc=kernel@pengutronix.de \
--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 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).