On Tue, Jan 03, 2017 at 09:15:06AM -0600, Bin Liu wrote: > During dma teardown for dequque urb, musb might generate bogus rx ep > interrupt even when the rx fifo is flushed. As mentioned in the current > inline comment, clearing ep interrupt in the teardown path avoids the > bogus interrupt. > > Before this change, any of the follow log messages could happen when > musb load is high. What "change" caused this? > > musb_host_rx 1853: BOGUS RX2 ready, csr 0000, count 0 > > musb_host_rx 1936: RX3 dma busy, csr 2020 > > cc: stable@xxxxxxxxxxxxxxx # 4.1+ Do you have a git commit id that caused this issue? thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
