tree f3724eeea95ef65c48061506023b63bf86633075
parent f131767eefc47de2f8afb7950cdea78397997d66
author Patrice Chotard <patrice.chotard@foss.st.com> 1622705661 +0200
committer Mark Brown <broonie@kernel.org> 1622724936 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAmC40UgACgkQJNaLcl1U
 h9D6ggf9Fep2LRkGRqfgeJjTwC8K457hILW7NodPqTiCXZs7V+jsrTkqf4WIxBy5
 2MS5XHQhD5NGoysZLUWXkSK6UpfIHmdmFiDLUjBKbFGGGh4WbOl8T0EyzKZbYXvD
 +5Tz3LqgXyQmoCKQXEmXe6UX3g2e8Skofo59KhaciZNBvx7MVdVh7SDjdrF7YzA8
 TRqY+r3d/l7dnsPDFcmrjcixmUjAsOS3U4M4pggwDMj2B8/4te4B6JNZ2EEsPX0+
 Oya3k/CYglYLrEKuXy3AuPRArJYWu2W/T/SzsPqHW1zjnCoH+me1QzkHh6cHPhoj
 eLXZBJqoG0cYFLoSpcnw1IZ6XFy/xQ==
 =bbDU
 -----END PGP SIGNATURE-----

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>