tree ffd8dfa5fda756cc396cd2f59db9d3a582d2d5ef
parent 8dedbeac8ab24d2da9271df2c8291971169846f2
author Serge Semin <Sergey.Semin@baikalelectronics.ru> 1602114898 +0300
committer Mark Brown <broonie@kernel.org> 1602194412 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQEzBAABCgAdFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl9/i+wACgkQJNaLcl1U
 h9CEeQf+NhEclw9fzSDOa1ylsF3MBJcyZfHAfclTFTELi9uV8jSJ9CsPsIMe4UR6
 NYowDShqXh6RKWw04TVoiutPHUu7w58Jn0eGvIZz2I71us5Jy7cOhuwmz8DI42tz
 cvXr4TuSGcJMVYyT9AtnTwVsRSc6gVYdmrd4CrHLtgyx46cH8lK1FaZj2YdzmeY2
 rjtgV/tEgDsduNxv+jhICTZbcuLjYvxHkOiumxHytUOUWVqSOpWkDU3hphZGZdYt
 j0pEprFNSFyp3EipRCfoY++u+kjoM025iGm9wJ1CcEbamge5LglUUm/CBiaWv5ZI
 13GrHKn4B2SFf8MW0sH5JL26HEKV7w==
 =hBYT
 -----END PGP SIGNATURE-----

spi: dw: Refactor IRQ-based SPI transfer procedure

Current IRQ-based SPI transfer execution procedure doesn't work well at
the final stage of the execution. If all the Tx data is sent out (written
to the Tx FIFO) but there is some data left to receive, the Tx FIFO Empty
IRQ will constantly happen until all of the requested inbound data is
received. Though for a short period of time, but it will make the system
less responsive. In order to fix that let's refactor the SPI transfer
execution procedure by taking the Rx FIFO Full IRQ into account. We'll read
and write SPI transfer data each time the IRQ happens as before. If all
the outbound data is sent out, we'll disable the Tx FIFO Empty IRQ. If
there is still some data to receive, we'll adjust the Rx FIFO Threshold
level, so the next IRQ would be raised at the moment of all incoming data
being available in the Rx FIFO.

Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Link: https://lore.kernel.org/r/20201007235511.4935-10-Sergey.Semin@baikalelectronics.ru
Signed-off-by: Mark Brown <broonie@kernel.org>