diff options
| author | 2011-06-29 09:28:43 +0100 | |
|---|---|---|
| committer | 2011-07-20 17:21:05 -0400 | |
| commit | 03e8cb534e7cc3f71a07528a44da7ce68e5b5708 (patch) | |
| tree | 989d0a96a03d8838de7617f6eb0062ed2a7065e6 /tools/lib/python/kdoc/python_version.py | |
| parent | mmc: sdhci-s3c: Fix return value in sdhci_s3c_suspend/resume() (diff) | |
mmc: dw_mmc: fix stop when fallen back to PIO
There are several situations when dw_mci_submit_data_dma() decides to
fall back to PIO mode instead of using DMA, due to a short (to avoid
overhead) or "complex" (e.g. with unaligned buffers) transaction, even
though host->use_dma is set. However dw_mci_stop_dma() decides whether
to stop DMA or set the EVENT_XFER_COMPLETE event based on host->use_dma.
When falling back to PIO mode this results in data timeout errors
getting missed and the driver locking up.
Therefore add host->using_dma to indicate whether the current
transaction is using dma or not, and adjust dw_mci_stop_dma() to use
that instead.
Signed-off-by: James Hogan <james.hogan@imgtec.com>
Acked-by: Will Newton <will.newton@imgtec.com>
Tested-by: Jaehoon Chung <jh80.chung@samsung.com>
Signed-off-by: Chris Ball <cjb@laptop.org>
Diffstat (limited to 'tools/lib/python/kdoc/python_version.py')
0 files changed, 0 insertions, 0 deletions
