diff options
| author | Miquel Raynal <[email protected]> | 2020-08-27 10:51:55 +0200 |
|---|---|---|
| committer | Miquel Raynal <[email protected]> | 2020-08-27 10:56:13 +0200 |
| commit | b440915af2e41daff7ee33e1d0ec29af5c37a1bf (patch) | |
| tree | 53966f3b97b947916858bd6f2aaf0ea9db1edfbc | |
| parent | 457700644f58ae4bf97ad35cbdce21710959a7e7 (diff) | |
dt-bindings: mtd: Document boolean NAND ECC properties
Document nand-use-soft-ecc-engine and nand-no-ecc-engine properties.
The former is here to force software correction, the latter prevents
any correction to happen.
These properties (along with nand-ecc-engine) are supposed to be more
accurate than the current nand-ecc-modes wich is very misleading and
very often people think it is mandatory while the core should be
relied upon to decide which correction to handle.
nand-ecc-mode was already inacurate, but it becomes totally
problematic with setups where there are several hardware engines.
Signed-off-by: Miquel Raynal <[email protected]>
Reviewed-by: Rob Herring <[email protected]>
Link: https://lore.kernel.org/linux-mtd/[email protected]
| -rw-r--r-- | Documentation/devicetree/bindings/mtd/nand-controller.yaml | 8 |
1 files changed, 8 insertions, 0 deletions
diff --git a/Documentation/devicetree/bindings/mtd/nand-controller.yaml b/Documentation/devicetree/bindings/mtd/nand-controller.yaml index ba7f8e4db5a5..e79bb6d2c108 100644 --- a/Documentation/devicetree/bindings/mtd/nand-controller.yaml +++ b/Documentation/devicetree/bindings/mtd/nand-controller.yaml @@ -68,6 +68,14 @@ patternProperties: 3/ The ECC engine is external, in this case the phandle should reference the specific ECC engine node. + nand-use-soft-ecc-engine: + type: boolean + description: Use a software ECC engine. + + nand-no-ecc-engine: + type: boolean + description: Do not use any ECC correction. + nand-ecc-placement: allOf: - $ref: /schemas/types.yaml#/definitions/string |