From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Gleixner Subject: Re: [PATCH v3 1/6] irqchip: add support for Marvell Orion SoCs Date: Tue, 11 Jun 2013 15:30:26 +0200 (CEST) Message-ID: References: <1370536034-23956-1-git-send-email-sebastian.hesselbarth@gmail.com> <1370536034-23956-2-git-send-email-sebastian.hesselbarth@gmail.com> Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Return-path: In-Reply-To: Sender: linux-doc-owner@vger.kernel.org To: Sebastian Hesselbarth Cc: Grant Likely , Rob Herring , Rob Landley , John Stultz , Russell King , Jason Cooper , Andrew Lunn , Thomas Petazzoni , Gregory Clement , devicetree-discuss@lists.ozlabs.org, linux-doc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org List-Id: devicetree@vger.kernel.org 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 > > Reviewed-by: Thomas Gleixner 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