diff options
| author | Łukasz Majewski <l.majewski@samsung.com> | 2015-09-25 18:25:25 +0200 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2015-09-28 11:03:56 -0400 |
| commit | 4d58e10e3e4900dbad3f44e65769092c631101cb (patch) | |
| tree | cbb4956389139f96f5170194a98d2e33c6035b2a /drivers | |
| parent | 4440ececed2d7c7494e03e462b395bdf4e8a418c (diff) | |
| download | talos-obmc-uboot-4d58e10e3e4900dbad3f44e65769092c631101cb.tar.gz talos-obmc-uboot-4d58e10e3e4900dbad3f44e65769092c631101cb.zip | |
mmc: dw_mmc: Increase timeout to 4 minutes (as in Linux kernel)
The commit: d9dbb97be0e4a550457aec5f11afefb446169c90
"mmc: dw_mmc: Zap endless timeout" removed endless loop waiting for end
of dw mmc transfer.
For some workloads - dfu test @ Odroid XU3 (sending 8MiB file) -
and SD cards (e.g. MicroSD Kingston 4GiB, Adata 4GiB)
the default timeout is to short.
The new value - 4 minutes (240 seconds) - is the same as the one used in
Linux kernel driver. Such fix should be good enough until we come up
with better fix for this issue.
Signed-off-by: Lukasz Majewski <l.majewski@samsung.com>
Cc: Marek Vasut <marex@denx.de>
Cc: Pantelis Antoniou <panto@antoniou-consulting.com>
Cc: Tom Rini <trini@konsulko.com>
Tested-by: Przemyslaw Marczak <p.marczak@samsung.com>
Diffstat (limited to 'drivers')
| -rw-r--r-- | drivers/mmc/dw_mmc.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/mmc/dw_mmc.c b/drivers/mmc/dw_mmc.c index a84c1e16d8..26d34ae5cc 100644 --- a/drivers/mmc/dw_mmc.c +++ b/drivers/mmc/dw_mmc.c @@ -214,7 +214,7 @@ static int dwmci_send_cmd(struct mmc *mmc, struct mmc_cmd *cmd, if (data) { start = get_timer(0); - timeout = 1000; + timeout = 240000; for (;;) { mask = dwmci_readl(host, DWMCI_RINTSTS); /* Error during data transfer. */ |
