From: Han Xu <han.xu@nxp.com>
To: sean@geanix.com, han.xu@nxp.com, miquel.raynal@bootlin.com,
richard@nod.at, vigneshr@ti.com, robh+dt@kernel.org
Cc: linux-mtd@lists.infradead.org, devicetree@vger.kernel.org
Subject: [PATCH 2/2] dt-bindings: mtd: gpmi-nand: add new fsl, legacy-bch-geometry flag
Date: Sat, 22 May 2021 15:51:36 -0500 [thread overview]
Message-ID: <20210522205136.19465-2-han.xu@nxp.com> (raw)
In-Reply-To: <20210522205136.19465-1-han.xu@nxp.com>
New bch geometry setting uses the minimum NAND chip required ecc
strength and step size by default. This flag was designed for backward
compatible. The fsl,use-minimum-ecc flag can be deprecated.
Signed-off-by: Han Xu <han.xu@nxp.com>
---
Documentation/devicetree/bindings/mtd/gpmi-nand.yaml | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/Documentation/devicetree/bindings/mtd/gpmi-nand.yaml b/Documentation/devicetree/bindings/mtd/gpmi-nand.yaml
index 9d764e654e1d..5f4eddd132a1 100644
--- a/Documentation/devicetree/bindings/mtd/gpmi-nand.yaml
+++ b/Documentation/devicetree/bindings/mtd/gpmi-nand.yaml
@@ -62,6 +62,7 @@ properties:
fsl,use-minimum-ecc:
type: boolean
+ deprecated: true
description: |
Protect this NAND flash with the minimum ECC strength required.
The required ECC strength is automatically discoverable for some
@@ -69,6 +70,14 @@ properties:
if this strength is not discoverable or this property is not enabled,
the software may chooses an implementation-defined ECC scheme.
+ fsl,legacy-bch-geometry:
+ type: boolean
+ description: |
+ Enable the legacy bch geometry setting, which will set the data chunk
+ size larger than oob size and chose the maximum ecc strength oob can
+ hold. This flag was designed for backward compatible or old NAND chip
+ support, should be en/disabled in u-boot and kernel at the same time.
+
fsl,no-blockmark-swap:
type: boolean
description: |
--
2.17.1
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2021-05-22 20:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-22 20:51 [PATCH 1/2] mtd: nand: raw: gpmi: new bch geometry settings Han Xu
2021-05-22 20:51 ` Han Xu [this message]
2021-05-23 17:44 ` Sean Nyekjaer
2021-05-25 19:13 ` Han Xu
2021-05-26 7:41 ` Miquel Raynal
2021-05-26 14:17 ` Han Xu
2021-05-26 15:31 ` Miquel Raynal
2021-07-05 10:46 ` Sean Nyekjaer
2021-07-06 2:50 ` Han Xu
2021-10-12 9:15 ` Sean Nyekjaer
2021-10-15 7:44 ` 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=20210522205136.19465-2-han.xu@nxp.com \
--to=han.xu@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=sean@geanix.com \
--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).