[PATCH v13 06/20] dt-bindings: mtd: Document nand-ecc-engine
miquel.raynal at bootlin.com
Thu Aug 27 04:51:54 EDT 2020
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 at bootlin.com>
Reviewed-by: Rob Herring <robh at kernel.org>
.../devicetree/bindings/mtd/nand-controller.yaml | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/Documentation/devicetree/bindings/mtd/nand-controller.yaml b/Documentation/devicetree/bindings/mtd/nand-controller.yaml
index 02f0347ff102..ba7f8e4db5a5 100644
@@ -55,6 +55,19 @@ patternProperties:
enum: [none, soft, hw, hw_syndrome, hw_oob_first, on-die]
+ - $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.
- $ref: /schemas/types.yaml#/definitions/string
More information about the linux-mtd