diff options
author | 2020-08-27 10:51:59 +0200 | |
---|---|---|
committer | 2020-09-28 15:59:48 +0200 | |
commit | d193792a26c216cb7db3cf12300c9414990fa603 (patch) | |
tree | a4572a219683dcb4580df627f5919ec134c1065e /tools/perf/scripts/python/export-to-postgresql.py | |
parent | mtd: rawnand: Use the new ECC engine type enumeration (diff) | |
download | wireguard-linux-d193792a26c216cb7db3cf12300c9414990fa603.tar.xz wireguard-linux-d193792a26c216cb7db3cf12300c9414990fa603.zip |
mtd: nand: Create a helper to extract the ECC configuration
Despite its current name, the eccreq field actually encodes both the
NAND requirements and the final ECC configuration. That works fine when
using on-die ECC since those 2 concepts match perfectly, but it starts
being a problem as soon as we use on-host ECC engines, where we're not
guaranteed to have a perfect match.
Let's hide the ECC configuration access behind a helper so we can later
split those 2 concepts.
Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
Link: https://lore.kernel.org/linux-mtd/20200827085208.16276-12-miquel.raynal@bootlin.com
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions