Lines Matching +full:boot +full:- +full:ecc +full:- +full:strength

1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/mtd/raw-nand-chip.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10   - Miquel Raynal <[email protected]>
13   - $ref: nand-chip.yaml#
16   The ECC strength and ECC step size properties define the user
18   they request the ECC engine to correct {strength} bit errors per
21   The interpretation of these parameters is implementation-defined, so
28     pattern: "^nand@[a-f0-9]$"
32       Contains the chip-select IDs.
34   nand-ecc-placement:
36       Location of the ECC bytes. This location is unknown by default
37       but can be explicitly set to "oob", if all ECC bytes are
38       known to be stored in the OOB area, or "interleaved" if ECC
44   nand-ecc-mode:
46       Legacy ECC configuration mixing the ECC engine choice and
49     enum: [none, soft, soft_bch, hw, hw_syndrome, on-die]
52   nand-bus-width:
59   nand-on-flash-bbt:
64       it as the device ages. Otherwise, the out-of-band area of a
65       few pages of all the blocks will be scanned at boot time to
70   nand-ecc-maximize:
72       Whether or not the ECC strength should be maximized. The
73       maximum ECC strength is both controller and chip
74       dependent. The ECC engine has to select the ECC config
75       providing the best strength and taking the OOB area size
77       only the in-band area is used by the upper layers, and you
81   nand-is-boot-medium:
83       Whether or not the NAND chip is a boot medium. Drivers might
84       use this information to select ECC algorithms supported by
85       the boot ROM or similar restrictions.
88   nand-rb:
91     $ref: /schemas/types.yaml#/definitions/uint32-array
93   rb-gpios:
100   wp-gpios:
108   - reg