forked from ~ljy/RK356X_SDK_RELEASE

hc
2024-05-13 9d77db3c730780c8ef5ccd4b66403ff5675cfe4e
kernel/Documentation/devicetree/bindings/mtd/marvell-nand.txt
....@@ -36,29 +36,29 @@
3636
3737 Required properties:
3838 - reg: shall contain the native Chip Select ids (0-3).
39
-- nand-rb: see nand.txt (0-1).
39
+- nand-rb: see nand-controller.yaml (0-1).
4040
4141 Optional properties:
4242 - marvell,nand-keep-config: orders the driver not to take the timings
4343 from the core and leaving them completely untouched. Bootloader
4444 timings will then be used.
4545 - label: MTD name.
46
-- nand-on-flash-bbt: see nand.txt.
47
-- nand-ecc-mode: see nand.txt. Will use hardware ECC if not specified.
48
-- nand-ecc-algo: see nand.txt. This property is essentially useful when
46
+- nand-on-flash-bbt: see nand-controller.yaml.
47
+- nand-ecc-mode: see nand-controller.yaml. Will use hardware ECC if not specified.
48
+- nand-ecc-algo: see nand-controller.yaml. This property is essentially useful when
4949 not using hardware ECC. Howerver, it may be added when using hardware
5050 ECC for clarification but will be ignored by the driver because ECC
5151 mode is chosen depending on the page size and the strength required by
5252 the NAND chip. This value may be overwritten with nand-ecc-strength
5353 property.
54
-- nand-ecc-strength: see nand.txt.
55
-- nand-ecc-step-size: see nand.txt. Marvell's NAND flash controller does
54
+- nand-ecc-strength: see nand-controller.yaml.
55
+- nand-ecc-step-size: see nand-controller.yaml. Marvell's NAND flash controller does
5656 use fixed strength (1-bit for Hamming, 16-bit for BCH), so the actual
5757 step size will shrink or grow in order to fit the required strength.
5858 Step sizes are not completely random for all and follow certain
5959 patterns described in AN-379, "Marvell SoC NFC ECC".
6060
61
-See Documentation/devicetree/bindings/mtd/nand.txt for more details on
61
+See Documentation/devicetree/bindings/mtd/nand-controller.yaml for more details on
6262 generic bindings.
6363
6464