Re: xhci irq event bogus return value ffffff94

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 21 Apr 2015, Joe Lawrence wrote:

> 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. :(

I don't have all that hardware either, but changing them sounds like a 
good idea.  I will take care of it.

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




[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux