On Tue, 09 Sep 2014, Charles Keepax wrote: > We use a dummy IRQ chip to dispatch interrupts to the two seperate IRQ > domains on the Arizona devices. This is just a simple software IRQ chip > and thus the current handle_edge_irq is unnecessary for its needs. > > Signed-off-by: Charles Keepax <[email protected]> > --- > drivers/mfd/arizona-irq.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-)
Applied, thanks. > diff --git a/drivers/mfd/arizona-irq.c b/drivers/mfd/arizona-irq.c > index 5e2f450..3a3fe7c 100644 > --- a/drivers/mfd/arizona-irq.c > +++ b/drivers/mfd/arizona-irq.c > @@ -172,7 +172,7 @@ static int arizona_irq_map(struct irq_domain *h, unsigned > int virq, > struct regmap_irq_chip_data *data = h->host_data; > > irq_set_chip_data(virq, data); > - irq_set_chip_and_handler(virq, &arizona_irq_chip, handle_edge_irq); > + irq_set_chip_and_handler(virq, &arizona_irq_chip, handle_simple_irq); > irq_set_nested_thread(virq, 1); > > /* ARM needs us to explicitly flag the IRQ as valid -- Lee Jones Linaro STMicroelectronics Landing Team Lead Linaro.org │ Open source software for ARM SoCs Follow Linaro: Facebook | Twitter | Blog -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
