From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Han Xu <han.xu@nxp.com>
Cc: sbabic@denx.de, sean@geanix.com, frieder.schrempf@kontron.de,
festevam@gmail.com, ye.li@nxp.com, peng.fan@nxp.com,
linux-mtd@lists.infradead.org
Subject: Re: [PATCH v2 1/2] mtd: rawnand: gpmi: Refactor bch geometry settings function
Date: Mon, 28 Mar 2022 11:17:51 +0200 [thread overview]
Message-ID: <20220328111751.011e3f3e@xps13> (raw)
In-Reply-To: <20220325211411.30714-1-han.xu@nxp.com>
Hi Han,
han.xu@nxp.com wrote on Fri, 25 Mar 2022 16:14:10 -0500:
> The code change refactor the bch geometry setting function, which still
> use the legacy bch setting as default option, while user may choose to
> use chips required minimum ecc strength by DT flag "fsl,use-minimum-ecc".
> It also improve the gpmi_check_ecc function to check if the selected ecc
> strength is strong enough.
That should be a dedicated patch?
Otherwise looks fine.
>
> The driver uses legacy bch geometry settings by default, if the NAND
> chips oob size is less than 1KB. The legacy_set_geometry() sets the data
> chunk size(step_size) larger than oob size to make sure BBM locates in
> data chunk, then set the maximum ecc stength oob can hold. It always use
> unbalanced ECC layout, which ecc0 will cover both meta and data0 chunk.
>
> For all other cases,set the bch geometry by chip required strength and
> step size, which uses the minimum ecc strength chip required. It can be
> explicitly enabled by DT flag "fsl,use-minimum-ecc", but need to be
> en/disabled in both u-boot and kernel at the same time.
>
> Signed-off-by: Han Xu <han.xu@nxp.com>
> Tested-by: Sean Nyekjaer <sean@geanix.com>
>
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2022-03-28 9:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 21:14 [PATCH v2 1/2] mtd: rawnand: gpmi: Refactor bch geometry settings function Han Xu
2022-03-25 21:14 ` [PATCH v2 2/2] mtd: rawnand: gpmi: Add large oob bch setting support Han Xu
2022-03-28 9:10 ` Miquel Raynal
2022-03-28 9:17 ` 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=20220328111751.011e3f3e@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=festevam@gmail.com \
--cc=frieder.schrempf@kontron.de \
--cc=han.xu@nxp.com \
--cc=linux-mtd@lists.infradead.org \
--cc=peng.fan@nxp.com \
--cc=sbabic@denx.de \
--cc=sean@geanix.com \
--cc=ye.li@nxp.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.