diff options
| author | Patrice Chotard <patrice.chotard@foss.st.com> | 2021-06-03 10:34:21 +0300 |
|---|---|---|
| committer | Mark Brown <broonie@kernel.org> | 2021-06-03 15:55:36 +0300 |
| commit | d38fa9a155b2829b7e2cfcf8a4171b6dd3672808 (patch) | |
| tree | f3724eeea95ef65c48061506023b63bf86633075 /tools/perf/scripts/python/failed-syscalls-by-pid.py | |
| parent | f131767eefc47de2f8afb7950cdea78397997d66 (diff) | |
| download | linux-d38fa9a155b2829b7e2cfcf8a4171b6dd3672808.tar.xz | |
spi: stm32-qspi: Always wait BUSY bit to be cleared in stm32_qspi_wait_cmd()
In U-boot side, an issue has been encountered when QSPI source clock is
running at low frequency (24 MHz for example), waiting for TCF bit to be
set didn't ensure that all data has been send out the FIFO, we should also
wait that BUSY bit is cleared.
To prevent similar issue in kernel driver, we implement similar behavior
by always waiting BUSY bit to be cleared.
Signed-off-by: Patrice Chotard <patrice.chotard@foss.st.com>
Link: https://lore.kernel.org/r/20210603073421.8441-1-patrice.chotard@foss.st.com
Signed-off-by: Mark Brown <broonie@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions