diff options
| author | Yang Xiwen <forbidden405@outlook.com> | 2024-02-01 22:05:43 +0800 |
|---|---|---|
| committer | Jaehoon Chung <jh80.chung@samsung.com> | 2024-04-15 16:01:32 +0900 |
| commit | 1fa6dc2879899a42ba85d4ece617c2356d048308 (patch) | |
| tree | cfdedf517ae3648f72732cd53d2bdc01c8ffc31b /drivers | |
| parent | 4685d6fbe47f9aab196558334ec89c3ca7bdb642 (diff) | |
| download | u-boot-1fa6dc2879899a42ba85d4ece617c2356d048308.zip u-boot-1fa6dc2879899a42ba85d4ece617c2356d048308.tar.gz u-boot-1fa6dc2879899a42ba85d4ece617c2356d048308.tar.bz2 | |
mmc: dw_mmc: Don't return error if data busy timeout
As described in [1], some poor hardware or cards would fail to release
the bus and keep driving data lines low. Ignore it and send the next cmd
directly seems okay for most cases.
[1]: https://patchwork.kernel.org/project/linux-mmc/patch/1424458179-5456-1-git-send-email-dianders@chromium.org/
Signed-off-by: Yang Xiwen <forbidden405@outlook.com>
Tested-by: Jaehoon Chung <jh80.chung@samsung.com>
Diffstat (limited to 'drivers')
| -rw-r--r-- | drivers/mmc/dw_mmc.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/drivers/mmc/dw_mmc.c b/drivers/mmc/dw_mmc.c index 400066f..e103664 100644 --- a/drivers/mmc/dw_mmc.c +++ b/drivers/mmc/dw_mmc.c @@ -262,8 +262,8 @@ static int dwmci_send_cmd(struct mmc *mmc, struct mmc_cmd *cmd, while (dwmci_readl(host, DWMCI_STATUS) & DWMCI_BUSY) { if (get_timer(start) > timeout) { - debug("%s: Timeout on data busy\n", __func__); - return -ETIMEDOUT; + debug("%s: Timeout on data busy, continue anyway\n", __func__); + break; } } |