]> nv-tegra.nvidia Code Review - linux-2.6.git/commit
[MTD] [NOR] cfi_cmdset_0001: Timeouts for erase, write and unlock operations
authorAnders Grafström <grfstrm@users.sourceforge.net>
Tue, 5 Aug 2008 16:37:41 +0000 (18:37 +0200)
committerDavid Woodhouse <David.Woodhouse@intel.com>
Wed, 6 Aug 2008 08:44:54 +0000 (09:44 +0100)
commite93cafe45fd74935e0aca2b79e533f0e3ed9640f
treef30b1eb1df5eed94145ad85c05f7b911c393d046
parent2e489e077a6ad118c4f247faedf330117b107cce
[MTD] [NOR] cfi_cmdset_0001: Timeouts for erase, write and unlock operations

Timeouts are currently given by the typical operation time times 8.
It works in the general well-behaved case but not when an erase block is
failing. For erase operations, it seems that a failing erase block will
keep the device state machine in erasing state until the vendor
specified maximum timeout period has passed. By this time the driver
would have long since timed out, left erasing state and attempted
further operations which all fail. This patch implements timeouts using
values from the CFI Query structure when available.
The patch also sets a longer timeout for locking operations. The current
value used for locking/unlocking given by 1000000/HZ microseconds is too
short for devices like J3 and J5 Strataflash which have a typical clear
lock-bits time of 0.5 seconds.

Signed-off-by: Anders Grafström <grfstrm@users.sourceforge.net>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
drivers/mtd/chips/cfi_cmdset_0001.c
include/linux/mtd/flashchip.h