[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.10.1409052056400.5472@nanos>
Date: Fri, 5 Sep 2014 21:05:50 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: Andrew Bresticker <abrestic@...omium.org>
cc: Ralf Baechle <ralf@...ux-mips.org>,
Rob Herring <robh+dt@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Mark Rutland <mark.rutland@....com>,
Ian Campbell <ijc+devicetree@...lion.org.uk>,
Kumar Gala <galak@...eaurora.org>,
Jason Cooper <jason@...edaemon.net>,
Jeffrey Deans <jeffrey.deans@...tec.com>,
Markos Chandras <markos.chandras@...tec.com>,
Paul Burton <paul.burton@...tec.com>,
Arnd Bergmann <arnd@...db.de>,
John Crispin <blogic@...nwrt.org>,
David Daney <ddaney.cavm@...il.com>, linux-mips@...ux-mips.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2 14/16] irqchip: mips-gic: Support local interrupts
On Fri, 5 Sep 2014, Andrew Bresticker wrote:
> static void gic_mask_irq(struct irq_data *d)
> {
> - GIC_CLR_INTR_MASK(d->irq - gic_irq_base);
> + unsigned int irq = d->irq - gic_irq_base;
> +
> + if (gic_is_local_irq(irq)) {
> + GICWRITE(GIC_REG(VPE_LOCAL, GIC_VPE_RMASK),
> + 1 << GIC_INTR_BIT(gic_hw_to_local_irq(irq)));
> + } else {
> + GIC_CLR_INTR_MASK(irq);
> + }
> }
>
> static void gic_unmask_irq(struct irq_data *d)
> {
> - GIC_SET_INTR_MASK(d->irq - gic_irq_base);
> + unsigned int irq = d->irq - gic_irq_base;
> +
> + if (gic_is_local_irq(irq)) {
> + GICWRITE(GIC_REG(VPE_LOCAL, GIC_VPE_SMASK),
> + 1 << GIC_INTR_BIT(gic_hw_to_local_irq(irq)));
> + } else {
> + GIC_SET_INTR_MASK(irq);
> + }
Why are you adding a conditional in all these functions instead of
having two interrupt chips with separate callbacks and irqdata?
And looking at GIC_SET_INTR_MASK(irq) makes me shudder even more. The
whole thing can be replaced with the generic interrupt chip functions.
If you set it up proper, then there is not a single conditional or
runtime calculation of bitmasks, address offsets etc.
Thanks,
tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists