On 04/21/2015 08:21 AM, Mathias Nyman wrote: [...] > On the other hand if we just removed xhci, and share the interrupt with somebody else who is > also generating an interrupts, then we would probably continue to read 0xffffffff from the status reg and > should return IRQ_NONE. Yes, I think this was Sergei's concern as well and IRQ_NONE is probably the safer value on a shared line. Unfortunately ehci-hcd.c, fotg210-hcd.c, fusbh200-hcd.c, ohci-hcd.c, oxu210hp-hcd.c all return dead controller irq with IRQ_HANDLED. I don't have all that hardware to test a change across the board. :( > Anyways, not a very likely situation and anything is better than -ESHUTDOWN. > > I tried to figure out the reason behind the -ESHUTDOWN, but looks like it has always just been there. > It was added with the interrupt handler code and wasn't mentioned in the commit message. > > I'll add you patch and send it forward once rc1 is out Thanks! -- Joe -- 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
