On Tue, 3 Mar 2015, Jay Guillory wrote: > Hi, > > I'm doing some usb driver development work and running into an issue where > my urb completion handler is not being called to give my driver back the > urb/buffer. This issue occurs randomly, ie it'll happen anywhere w/in 5 > minutes to over 4 hours. > > With the kernel dynamic debugging enabled for the usbcore and xhci_hcd > modules, I see that the urb I submit to the usbcore appears to be mapped > to the hcd's dma for transfer, but the xhci_irq never gets called to give > the driver back the urb. Unfortunately, it results in my application being > timed out eventually because any urbs I submit after this happens appears > to not be sent to the usb wire according to usb protocol analyzer logs. > This is with sending messages to my Control EP, with very low traffic. > > Could this be an issue with the usb controller that I'm using on my > device? Can someone help me understand under what conditions should the > xhci_irq/interrupt occur? The interrupt will occur when the transfer is complete. The most likely reason for the transfer not to complete is because the device doesn't send any response. Alan Stern -- 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
