[MTD] [NOR] Prevent erase command invocation on suspended chip
authorAlexander Belyakov <abelyako@googlemail.com>
Wed, 7 Nov 2007 08:58:07 +0000 (11:58 +0300)
committerDavid Woodhouse <dwmw2@infradead.org>
Mon, 26 Nov 2007 15:54:16 +0000 (15:54 +0000)
commit6c24e4161e80a5c03e9d969b5db73d8553846037
tree56c24fb17325d89259fc1ce27148a58c2d5523b1
parent5f4d47d5d1060a93be83e33a167a53a7f8c08b20
[MTD] [NOR] Prevent erase command invocation on suspended chip

while running stress tests we have met cfi_cmdset_0001.c driver issue.
Working on multipartitional devices with erase suspend on write
feature enabled it is possible to get erase operation invoked on chip
with suspended erase. get_chip() looses information about earlier
suspended erase and new erase operation gets issued. New erase
operations report successful completion, but blocks remain dirty
causing, for example, JFFS2 error messages like:

...
Newly-erased block contained word 0x20031985 at offset 0x00200000
Newly-erased block contained word 0x20031985 at offset 0x00280000
Newly-erased block contained word 0x20031985 at offset 0x00240000
...

The patch below fixes that issue.

Signed-off-by: Alexander Belyakov <alexander.belyakov@intel.com>
Acked-by: Nicolas Pitre <nico@cam.org>
Signed-off-by: David Woodhouse <dwmw2@infradead.org>
drivers/mtd/chips/cfi_cmdset_0001.c