[deliverable/linux.git] / Documentation / devicetree / bindings / mtd / nand.txt

* MTD generic binding

- nand-ecc-mode : String, operation mode of the NAND ecc mode.
  Supported values are: "none", "soft", "hw", "hw_syndrome", "hw_oob_first",
  "soft_bch".
- nand-bus-width : 8 or 16 bus width if not present 8
- nand-on-flash-bbt: boolean to enable on flash bbt option if not present false

- nand-ecc-strength: integer representing the number of bits to correct
		     per ECC step.

- nand-ecc-step-size: integer representing the number of data bytes
		      that are covered by a single ECC step.

The ECC strength and ECC step size properties define the correction capability
of a controller. Together, they say a controller can correct "{strength} bit
errors per {size} bytes".

The interpretation of these parameters is implementation-defined, so not all
implementations must support all possible combinations. However, implementations
are encouraged to further specify the value(s) they support.
Commit	Line	Data
770d7c39 JCPV	1	* MTD generic binding
	2
	3	- nand-ecc-mode : String, operation mode of the NAND ecc mode.
	4	Supported values are: "none", "soft", "hw", "hw_syndrome", "hw_oob_first",
	5	"soft_bch".
	6	- nand-bus-width : 8 or 16 bus width if not present 8
	7	- nand-on-flash-bbt: boolean to enable on flash bbt option if not present false
8dd49165 EG	8
	9	- nand-ecc-strength: integer representing the number of bits to correct
	10	per ECC step.
	11
	12	- nand-ecc-step-size: integer representing the number of data bytes
	13	that are covered by a single ECC step.
	14
	15	The ECC strength and ECC step size properties define the correction capability
	16	of a controller. Together, they say a controller can correct "{strength} bit
	17	errors per {size} bytes".
	18
	19	The interpretation of these parameters is implementation-defined, so not all
	20	implementations must support all possible combinations. However, implementations
	21	are encouraged to further specify the value(s) they support.