summaryrefslogtreecommitdiffstats
path: root/drivers/mtd/nand/omap2.c
diff options
context:
space:
mode:
authorStefan Roese <sr@denx.de>2012-08-28 11:34:13 +0200
committerDavid Woodhouse <David.Woodhouse@intel.com>2012-09-29 15:29:08 +0100
commit7be1f6b9a1ae3476a424380b52aad7c14c3273ab (patch)
tree0d005f8a83ad814b37ec75e72784d658b9b95e85 /drivers/mtd/nand/omap2.c
parenta5ff4f102937a3492bca4a9ff0c341d78813414c (diff)
downloadtalos-op-linux-7be1f6b9a1ae3476a424380b52aad7c14c3273ab.tar.gz
talos-op-linux-7be1f6b9a1ae3476a424380b52aad7c14c3273ab.zip
mtd: cfi_cmdset_0001: Fix problem with unlocking timeout
Unlocking may take up to 1.4 seconds on some Intel flashes. So lets use a max. of 1.5 seconds (1500ms) as timeout. See "Clear Block Lock-Bits Time" on page 40 in "3 Volt Intel StrataFlash Memory" 28F128J3,28F640J3,28F320J3 manual from February 2003 This patch also fixes some other problems with this timeout: - Don't use HZ in timeout "calculation"! While testing we noticed that an unlocking timeout occured with HZ=1000 and didn't occur with HZ=300. This was because the timeout parameter was calculated differently depending on the HZ value. Now a fixed value of 1500ms is used. - The last parameter of WAIT_TIMEOUT (defined to inval_cache_and_wait_for_operation) has to be passed in micro-seconds. So multiply the ms value with 1000 and not 100 to calculate this value. - Use variable name "mdelay" instead of misleading "udelay". Signed-off-by: Stefan Roese <sr@denx.de> Tested-by: Stephan Gatzka <stephan@gatzka.org> Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
Diffstat (limited to 'drivers/mtd/nand/omap2.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud