diff options
| author | Brian Norris <[email protected]> | 2016-06-24 10:38:14 -0700 |
|---|---|---|
| committer | Brian Norris <[email protected]> | 2016-07-09 19:29:38 -0700 |
| commit | 06586204714b7befec99e554c71687b0b40f351c (patch) | |
| tree | a9b3b4af144f225b85e44567eebe7342e6d095ff /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | 21a190b970878be8298c3f696aede1de36986817 (diff) | |
mtd: spi-nor: fix wrong "fully unlocked" test
In stm_unlock(), the test to determine whether we've fully unlocked the
flash checks for the lock length to be equal to the flash size. That is
a typo/think-o -- the condition actually means the flash is completely
*locked.* We should be using the inverse condition -- that the lock
length is 0 (i.e., no protection).
The result of this bug is that we never actually turn off the Status
Register Write Disable bit, even if the flash is completely unlocked.
Now we can.
Fixes: 47b8edbf0d43 ("mtd: spi-nor: disallow further writes to SR if WP# is low")
Reported-by: Giorgio <[email protected]>
Signed-off-by: Brian Norris <[email protected]>
Cc: Ezequiel Garcia <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions