[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1609201600490.6905@nanos>
Date: Tue, 20 Sep 2016 16:02:03 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Alexandre Torgue <alexandre.torgue@...com>
cc: Mark Rutland <mark.rutland@....com>, devicetree@...r.kernel.org,
Daniel Thompson <daniel.thompson@...aro.org>,
Jason Cooper <jason@...edaemon.net>, arnd@...db.de,
Marc Zyngier <marc.zyngier@....com>, bruherrera@...il.com,
Linus Walleij <linus.walleij@...aro.org>,
linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>,
Maxime Coquelin <mcoquelin.stm32@...il.com>,
lee.jones@...aro.org, linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH v5 2/9] drivers: irqchip: Add STM32 external interrupts
support
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
Powered by blists - more mailing lists