Messages in this thread | | | Date | Thu, 26 Jul 2007 23:49:56 +0900 (JST) | Subject | Re: [PATCH] fix return value of i8042_aux_test_irq | From | fernando@oss ... |
| |
On Thu, July 26, 2007 11:10 pm, Alan Cox wrote: >> The handler does handle the interrupt - both status and data registers >> are read so from the keyboard controller point of view the interrupt >> has been handled even if we happen to discard the data. As far as I >> know IRQ12 is never shared by BIOS... Vojtech, do you remember why we >> request IRQ12 with IRQF_SHARED? > > A small number of boxes do share IRQ12 and it was switched to shared for > them. If that is the case interrupt handlers should be able to determine whether a certain interrupt comes from their respective devices, and return IRQ_HANDLED or IRQ_NONE accordingly. Returning IRQ_HANDLED unconditionally when IRQF_SHARED is set seems strange. Is this behavior intended?
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |