summaryrefslogtreecommitdiffstats
path: root/crypto
diff options
context:
space:
mode:
authorDmitry Osipenko <digetx@gmail.com>2020-02-09 19:44:15 +0300
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2020-02-10 12:32:13 -0800
commit1f69a1273b3f204a9c00dc3bbdcc4afcd0787428 (patch)
tree6862f4219935efdd44f7f77f115941091011978e /crypto
parent04b5bfe3dc94e64d0590c54045815cb5183fb095 (diff)
downloadlinux-1f69a1273b3f204a9c00dc3bbdcc4afcd0787428.tar.gz
linux-1f69a1273b3f204a9c00dc3bbdcc4afcd0787428.tar.bz2
linux-1f69a1273b3f204a9c00dc3bbdcc4afcd0787428.zip
tty: serial: tegra: Handle RX transfer in PIO mode if DMA wasn't started
It is possible to get an instant RX timeout or end-of-transfer interrupt before RX DMA was started, if transaction is less than 16 bytes. Transfer should be handled in PIO mode in this case because DMA can't handle it. This patch brings back the original behaviour of the driver that was changed by accident by a previous commit, it fixes occasional Bluetooth HW initialization failures which I started to notice recently. Fixes: d5e3fadb7012 ("tty: serial: tegra: Activate RX DMA transfer by request") Signed-off-by: Dmitry Osipenko <digetx@gmail.com> Link: https://lore.kernel.org/r/20200209164415.9632-1-digetx@gmail.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'crypto')
0 files changed, 0 insertions, 0 deletions