diff options
author | John Crispin <[email protected]> | 2016-06-20 23:32:09 +0200 |
---|---|---|
committer | Boris Brezillon <[email protected]> | 2016-07-11 08:40:15 +0200 |
commit | f45eb7b522359260606852d79a8899e5db37d8f3 (patch) | |
tree | 5e11a4959ee19d1c4f52c10a93f574b3867a2fd4 /tools/perf/util/scripting-engines/trace-event-python.c | |
parent | 024366750c2e04fdcda8bca685194ef0196b35fe (diff) |
mtd: nand: xway: Avoid messing up with IO_ADDR_W in ->cmd_ctrl()
The ->cmd_ctrl() function is adjusting the ->IO_ADDR_W value depending
on the command type each time NAND_CTRL_CHANGE is passed. This is not
only useless but can lead to an ->IO_ADDR_W corruption.
Get rid of this logic and rely on the NAND_CLE and NAND_ALE flags to
deduce the iomem address to write the cmd argument to.
Signed-off-by: John Crispin <[email protected]>
Signed-off-by: Hauke Mehrtens <[email protected]>
Signed-off-by: Boris Brezillon <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions