diff options
| author | Kamal Dasu <[email protected]> | 2019-05-21 10:44:22 -0400 |
|---|---|---|
| committer | Miquel Raynal <[email protected]> | 2019-06-27 20:06:38 +0200 |
| commit | 78933218f5c658195124456904cc56e5b52988bd (patch) | |
| tree | 24de33665ab931e7d2571776cc6abc6c2495d73e /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | edd3e620ab15e66b0d5477dc3bd4732a2b3baddb (diff) | |
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 <[email protected]>
Signed-off-by: Miquel Raynal <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions