On Tue, 11 Jun 2013, Thomas Gleixner wrote:
> On Thu, 6 Jun 2013, Sebastian Hesselbarth wrote:
>
> > This patch adds an irqchip driver for the main interrupt controller found
> > on Marvell Orion SoCs (Kirkwood, Dove, Orion5x, Discovery Innovation).
> > Corresponding device tree documentation is also added.
> >
> > Signed-off-by: Sebastian Hesselbarth <sebastian.hesselbarth@xxxxxxxxx>
>
> Reviewed-by: Thomas Gleixner <tglx@xxxxxxxxxxxxx>
Second thoughts:
>+static void orion_bridge_irq_handler(unsigned int irq, struct irq_desc *desc)
>+{
>+ struct irq_domain *d = irq_get_handler_data(irq);
>+ struct irq_chip_generic *gc = irq_get_domain_generic_chip(d, irq);
>+ u32 stat = readl_relaxed(gc->reg_base + ORION_BRIDGE_IRQ_CAUSE) &
>+ gc->mask_cache;
In init you map the first irq of that chip and install the chain
handler for it. Now if that first irq fires, isn't that set in the
cause register as well? And what acks that first irq?
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
