On Mon, Oct 22, 2012 at 10:08 PM, Stephen Warren <swar...@wwwdotorg.org> wrote: > On 10/22/2012 02:14 AM, Linus Walleij wrote:
>> It's an IRQ handler so it should be robust to spurious IRQs due to >> transient hardware states etc I believe. >> >> So if there is a transient IRQ before gpio_to_irq() is called -> boom. > > I wonder though (a) why it would be unmasked in HW, and (b) why the > software would even look at the status bit if no handler were registered? That's true of course ... OK I'll update the patch. Still I'm not feeling good about the irq_create_mapping/irq_find_mapping separation, I think a lot of drivers just get this wrong and it's causing bugs... it'd be way better if there was just one of them and we could count on descriptors being allocated after adding any kind of irqdomain but I have no clue how hard it would be to achieve this. Yours, Linus Walleij -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
