summaryrefslogtreecommitdiff
path: root/colorize.h
AgeCommit message (Expand)AuthorFilesLines
2013-06-04misc: cleanup header commentsDaniel Borkmann1-0/+8
d>space:mode:
authorBin Liu <b-liu@ti.com>2017-01-03 18:13:46 -0600
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2017-01-05 19:18:05 +0100
commit6def85a396ce7796bd9f4561c6ae8138833f7a52 (patch)
tree18423397671999746ea8e1cd4d28e8cd99e6da94
parentc8d204b38a558d74fafb6915e2593602b7f4b823 (diff)
usb: musb: core: add clear_ep_rxintr() to musb_platform_ops
During dma teardown for dequque urb, if musb load is high, musb might generate bogus rx ep interrupt even when the rx fifo is flushed. In such case any of the follow log messages could happen. musb_host_rx 1853: BOGUS RX2 ready, csr 0000, count 0 musb_host_rx 1936: RX3 dma busy, csr 2020 As mentioned in the current inline comment, clearing ep interrupt in the teardown path avoids the bogus interrupt. Clearing ep interrupt is platform dependent, so this patch adds a platform callback to allow glue driver to clear the ep interrupt. This bug seems to be existing since the initial driver for musb support, but I only validated the fix back to v4.1, so only cc stable for v4.1+. cc: stable@vger.kernel.org # 4.1+ Signed-off-by: Bin Liu <b-liu@ti.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat