diff options
author | 2019-10-08 11:56:02 +0200 | |
---|---|---|
committer | 2019-11-13 16:10:16 +0100 | |
commit | 8266c585f4897ceff0959bd64d196f164caa0601 (patch) | |
tree | a59e6a2e8dc7567aa437d8cbb587af0b7dfc5cb9 /tools/perf/scripts/python/bin/export-to-postgresql-record | |
parent | mmc: mmci: make unexported functions static (diff) | |
download | linux-dev-8266c585f4897ceff0959bd64d196f164caa0601.tar.xz linux-dev-8266c585f4897ceff0959bd64d196f164caa0601.zip |
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 'tools/perf/scripts/python/bin/export-to-postgresql-record')
0 files changed, 0 insertions, 0 deletions