diff options
| author | Brian Norris <[email protected]> | 2010-12-12 00:23:33 -0800 |
|---|---|---|
| committer | David Woodhouse <[email protected]> | 2011-01-06 15:19:20 +0000 |
| commit | b7b1a29d94c17e4341856381bccb4d17495bea60 (patch) | |
| tree | 855932e331bcbb2f9c2889d879786005552a1f72 /tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/Util.py | |
| parent | 0b524fb9314dc852d6a029296545ddbb17709a8b (diff) | |
mtd: nand: rearrange ONFI revision checking, add ONFI 2.3
In checking for the ONFI revision, the first conditional (for checking
"unsupported" ONFI) seems unnecessary. All ONFI revisions should be
backwards-compatible; even if this is not the case on some newer ONFI
revision, it should simply fail the second version-checking if-else block
(i.e., the bit-fields for 1.0, 2.0, etc. would not be set to 1). Thus, we
move our "unsupported" condition after having checked each bit field.
Also, it's simple enough to add a condition for ONFI revision 2.3. Note
that this does *NOT* mean we handle all new features of ONFI versions
above 1.0.
Signed-off-by: Brian Norris <[email protected]>
Acked-by: Florian Fainelli <[email protected]>
Signed-off-by: David Woodhouse <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/Perf-Trace-Util/lib/Perf/Trace/Util.py')
0 files changed, 0 insertions, 0 deletions