On Tue, 20 Sep 2016, Alexandre Torgue wrote: > On 09/20/2016 02:44 PM, Thomas Gleixner wrote: > > Free will be called when a interrupt in the child domain is torn down, > > i.e. when irq_domain_free_irqs() is called. And it will be called for both > > domains like the alloc callback is invoked on both domains via > > irq_domain_alloc_irqs(). > > Thanks Thomas for this clarification (I'm sure now that we need .free > callbacks). > irq_domain_free_irqs() is called in 2 scenario: > 1- when issue occurs in irq_create_fwspec_mapping() > 2- when irq_dispose_mapping() is called > > Case 2 is the one I tested some times ago. In this case, I need to mask > interrupts in .free callback of EXTI (parent) domain to avoid spurious > interrupts. And why would irq_dispose_mapping() be called on an unmasked, i.e. active, interrupt? The masking is just papering over that. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
