diff options
| author | Kamal Dasu <kdasu.kdev@gmail.com> | 2019-05-21 16:44:22 +0200 |
|---|---|---|
| committer | Miquel Raynal <miquel.raynal@bootlin.com> | 2019-06-27 20:06:38 +0200 |
| commit | 78933218f5c658195124456904cc56e5b52988bd (patch) | |
| tree | 24de33665ab931e7d2571776cc6abc6c2495d73e /drivers/mtd/mtdblock.c | |
| parent | dt-bindings: mtd: brcmnand: Make nand-ecc-strength and nand-ecc-step-size opt... (diff) | |
| download | linux-78933218f5c658195124456904cc56e5b52988bd.tar.xz linux-78933218f5c658195124456904cc56e5b52988bd.zip | |
mtd: rawnand: brcmnand: fallback to detected ecc-strength, ecc-step-size
This change supports nand-ecc-step-size and nand-ecc-strength fields in
brcmnand DT node to be optional.
see: Documentation/devicetree/bindings/mtd/brcm,brcmnand.txt
If both nand-ecc-strength and nand-ecc-step-size are not specified in
device tree node for NAND, raw NAND layer does detect ECC information by
reading ONFI extended parameter page for parts using ONFI >= 2.1.
In case of non-ONFI NAND parts there could be a nand_id table entry with
ECC information. If there is valid device tree entry for nand-ecc-strength
and nand-ecc-step-size fields it still shall override the detected values.
Signed-off-by: Kamal Dasu <kdasu.kdev@gmail.com>
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Diffstat (limited to 'drivers/mtd/mtdblock.c')
0 files changed, 0 insertions, 0 deletions