summaryrefslogtreecommitdiffstats
path: root/drivers/mtd/inftlcore.c
diff options
context:
space:
mode:
authorKonstantin Baidarov <kbaidarov@ru.mvista.com>2005-11-07 09:00:05 +0000
committerThomas Gleixner <tglx@mtd.linutronix.de>2005-11-07 10:47:08 +0100
commitb95f9609c761a14d1e7be1a89f2a66399b5ae343 (patch)
treed0f097e82deb18ebc0c854ac1ae627865b63a130 /drivers/mtd/inftlcore.c
parentbe30c10fd8015a00c97c9b473263fe3c581389de (diff)
downloadop-kernel-dev-b95f9609c761a14d1e7be1a89f2a66399b5ae343.zip
op-kernel-dev-b95f9609c761a14d1e7be1a89f2a66399b5ae343.tar.gz
[MTD] chips cfi_cmdset_0002: Prevent timeout race
We've noticed that sometimes "MTD do_write_buffer(): software timeout" message was printed out when writing to a Fujitsu NOR flash. It turned out that this was because of a race in the timeout handling do_write_buffer(). A small timeout of (HZ / 1000) + 1 is used there, and sometimes if the timer interrupt handling takes more than one or even two jiffies (which is 1-2 ms with HZ == 1000) and that interrupt happens just after chip_ready() call, the driver bails out from a ready polling loop despite the chip has actually become ready while all those interrupts were handled. To deal with this issue, extra check for chip ready is neccessary on timeout expiration (and the checks should better be reordered). As do_write_oneword() uses the same approach, it needs to also be changed. Signed-off-by: Konstantin Baidarov <kbaidarov@ru.mvista.com> Signed-off-by: Sergei Shtylyov <sshtylyov@ru.mvista.com> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Diffstat (limited to 'drivers/mtd/inftlcore.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud