mtd: docg3 increase write/erase timeout

After several tries with ubifs, it appears empirically that constructor
provided figures for erase/write timeouts are underestimated. A timeout
of 100ms seems to work with a 5 years worn chip, and no timeouts occur
anymore.

Signed-off-by: Robert Jarzmik <robert.jarzmik@free.fr>
Signed-off-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
This commit is contained in:
Robert Jarzmik 2012-03-22 21:00:51 +01:00 коммит произвёл David Woodhouse
Родитель a7baef1211
Коммит a2b3d284ed
1 изменённых файлов: 3 добавлений и 3 удалений

Просмотреть файл

@ -1116,10 +1116,10 @@ static int doc_get_op_status(struct docg3 *docg3)
*/
static int doc_write_erase_wait_status(struct docg3 *docg3)
{
int status, ret = 0;
int i, status, ret = 0;
if (!doc_is_ready(docg3))
usleep_range(3000, 3000);
for (i = 0; !doc_is_ready(docg3) && i < 5; i++)
msleep(20);
if (!doc_is_ready(docg3)) {
doc_dbg("Timeout reached and the chip is still not ready\n");
ret = -EAGAIN;