First, I tried to replace 'mdelay' with 'msleep' and put it after
'unlock'. It gives a certain oops.
With the delay of 50 msec driver remains stable. It has something
to do with hardware initialization, so this value should not be
affected by CPU speed. I hope so.
Signed-off-by: Sergey Yanovich <[EMAIL PROTECTED]>
---
drivers/mmc/tifm.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/mmc/tifm.c b/drivers/mmc/tifm.c
index 30cab30..310f07c 100644
--- a/drivers/mmc/tifm.c
+++ b/drivers/mmc/tifm.c
@@ -361,7 +361,7 @@ mmc_tifm_irq_chip(unsigned long param)
socket->state = READY;
tasklet_schedule(&socket->cmd_end);
}
- mdelay(100);
+ mdelay(50);
spin_unlock_irqrestore(&socket->lock, flags);
mmc_detect_change(mmc, 0);
}
--
1.5.1.2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
