summaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/mtd/nand-controller.yaml
diff options
context:
space:
mode:
authorMiquel Raynal <miquel.raynal@bootlin.com>2020-08-27 10:51:54 +0200
committerMiquel Raynal <miquel.raynal@bootlin.com>2020-08-27 10:56:10 +0200
commit457700644f58ae4bf97ad35cbdce21710959a7e7 (patch)
treec60a876172c492d3cdb5b040f373d6f0d4a3576c /Documentation/devicetree/bindings/mtd/nand-controller.yaml
parent2d76f470224617fadfb35853d7d782b5caa56f9a (diff)
downloadlinux-stable-457700644f58ae4bf97ad35cbdce21710959a7e7.tar.gz
linux-stable-457700644f58ae4bf97ad35cbdce21710959a7e7.tar.bz2
linux-stable-457700644f58ae4bf97ad35cbdce21710959a7e7.zip
dt-bindings: mtd: Document nand-ecc-engine
This property is needed to precisely point to the hardware ECC engine to use when there are several of them available. Here, hardware also refers to the on-die possibility. Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com> Reviewed-by: Rob Herring <robh@kernel.org> Link: https://lore.kernel.org/linux-mtd/20200827085208.16276-7-miquel.raynal@bootlin.com
Diffstat (limited to 'Documentation/devicetree/bindings/mtd/nand-controller.yaml')
-rw-r--r--Documentation/devicetree/bindings/mtd/nand-controller.yaml13
1 files changed, 13 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/mtd/nand-controller.yaml b/Documentation/devicetree/bindings/mtd/nand-controller.yaml
index 02f0347ff102..ba7f8e4db5a5 100644
--- a/Documentation/devicetree/bindings/mtd/nand-controller.yaml
+++ b/Documentation/devicetree/bindings/mtd/nand-controller.yaml
@@ -55,6 +55,19 @@ patternProperties:
$ref: /schemas/types.yaml#/definitions/string
enum: [none, soft, hw, hw_syndrome, hw_oob_first, on-die]
+ nand-ecc-engine:
+ allOf:
+ - $ref: /schemas/types.yaml#/definitions/phandle
+ description: |
+ A phandle on the hardware ECC engine if any. There are
+ basically three possibilities:
+ 1/ The ECC engine is part of the NAND controller, in this
+ case the phandle should reference the parent node.
+ 2/ The ECC engine is part of the NAND part (on-die), in this
+ case the phandle should reference the node itself.
+ 3/ The ECC engine is external, in this case the phandle should
+ reference the specific ECC engine node.
+
nand-ecc-placement:
allOf:
- $ref: /schemas/types.yaml#/definitions/string