summaryrefslogtreecommitdiff
path: root/drivers/ipack
diff options
context:
space:
mode:
authorLudovic Barre <ludovic.barre@st.com>2019-10-08 11:56:02 +0200
committerUlf Hansson <ulf.hansson@linaro.org>2019-11-13 16:10:16 +0100
commit8266c585f4897ceff0959bd64d196f164caa0601 (patch)
treea59e6a2e8dc7567aa437d8cbb587af0b7dfc5cb9 /drivers/ipack
parente2b98d83ff0c1aaba31c767673c8000e20ad3524 (diff)
mmc: mmci: add hardware busy timeout feature
In the stm32_sdmmc variant, the datatimer is active not only during data transfers with the DPSM, but also while waiting for the busyend IRQs from commands having the MMC_RSP_BUSY flag set. This leads to an incorrect IRQ being raised to signal MCI_DATATIMEOUT error, which simply breaks the behaviour. Address this by updating the datatimer value before sending a command having the MMC_RSP_BUSY flag set. To inform the mmc core about the maximum supported busy timeout, which also depends on the current clock rate, set ->max_busy_timeout (in ms). Signed-off-by: Ludovic Barre <ludovic.barre@st.com> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Diffstat (limited to 'drivers/ipack')
0 files changed, 0 insertions, 0 deletions