[PATCH v5 14/21] dt-bindings: mtd: Add the nand-ecc-placement property
From: Miquel Raynal <miquel.raynal@bootlin.com>
Date: 2020-05-14 17:24:39
Subsystem:
memory technology devices (mtd), open firmware and flattened device tree bindings, the rest · Maintainers:
Miquel Raynal, Richard Weinberger, Vignesh Raghavendra, Rob Herring, Krzysztof Kozlowski, Conor Dooley, Linus Torvalds
Placement is where the ECC bytes are expected. No value means the controller can do whatever it desires (default is to put ECC bytes at the end of the OOB area). Alternative placement is "interleaved" (also sometimes referred as "syndrome") where data and OOB are mixed. Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com> --- .../devicetree/bindings/mtd/nand-controller.yaml | 10 ++++++++++ 1 file changed, 10 insertions(+)
diff --git a/Documentation/devicetree/bindings/mtd/nand-controller.yaml b/Documentation/devicetree/bindings/mtd/nand-controller.yaml
index d529f8587ba6..35512f2c66fa 100644
--- a/Documentation/devicetree/bindings/mtd/nand-controller.yaml
+++ b/Documentation/devicetree/bindings/mtd/nand-controller.yaml@@ -56,6 +56,16 @@ patternProperties: (Linux will handle the calculations). soft_bch is deprecated and should be replaced by soft and nand-ecc-algo. + nand-ecc-placement: + allOf: + - $ref: /schemas/types.yaml#/definitions/string + - enum: [ free, interleaved ] + description: + Location for the ECC bytes. Free is the default and means the + controller in charge is free to put them where it wants. + Default state is to put ECC bytes at the end of the OOB area. + Otherwise, ECC bytes may be interleaved with data. + nand-ecc-algo: allOf: - $ref: /schemas/types.yaml#/definitions/string
--
2.20.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel