diff options
| author | Kamal Dasu <kdasu.kdev@gmail.com> | 2017-03-04 00:16:53 +0300 |
|---|---|---|
| committer | Boris Brezillon <boris.brezillon@free-electrons.com> | 2017-04-25 15:18:42 +0300 |
| commit | 9d2ee0a60b8bd9bef2a0082c533736d6a7b39873 (patch) | |
| tree | 08104bffea7783a3211f338b5c7cacdc2aa1cd08 /drivers/memstick/core/Kconfig | |
| parent | 65a2c1caa70f71690dcb5afd8fc6afe67fcde599 (diff) | |
| download | linux-9d2ee0a60b8bd9bef2a0082c533736d6a7b39873.tar.xz | |
mtd: nand: brcmnand: Check flash #WP pin status before nand erase/program
On brcmnand controller v6.x and v7.x, the #WP pin is controlled through
the NAND_WP bit in CS_SELECT register.
The driver currently assumes that toggling the #WP pin is
instantaneously enabling/disabling write-protection, but it actually
takes some time to propagate the new state to the internal NAND chip
logic. This behavior is sometime causing data corruptions when an
erase/program operation is executed before write-protection has really
been disabled.
Fixes: 27c5b17cd1b1 ("mtd: nand: add NAND driver "library" for Broadcom STB NAND controller")
Signed-off-by: Kamal Dasu <kdasu.kdev@gmail.com>
Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
Diffstat (limited to 'drivers/memstick/core/Kconfig')
0 files changed, 0 insertions, 0 deletions