From: Marc Zyngier <maz@kernel.org>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: Jason Cooper <jason@lakedaemon.net>,
patchwork-lst@pengutronix.de, NXP Linux Team <linux-imx@nxp.com>,
kernel@pengutronix.de, Thomas Gleixner <tglx@linutronix.de>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] irqchip/irq-imx-gpcv2: forward irq type to parent
Date: Fri, 26 Jul 2019 14:41:30 +0100 [thread overview]
Message-ID: <8636isoqut.wl-maz@kernel.org> (raw)
In-Reply-To: <20190712132905.10671-1-l.stach@pengutronix.de>
On Fri, 12 Jul 2019 14:29:05 +0100,
Lucas Stach <l.stach@pengutronix.de> wrote:
>
> The GPCv2 is a stacked IRQ controller below the ARM GIC. It doesn't
> care about the IRQ type itself, but needs to forward the type to the
> parent IRQ controller, so this one can be configured correctly.
>
> Signed-off-by: Lucas Stach <l.stach@pengutronix.de>
> ---
> drivers/irqchip/irq-imx-gpcv2.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/irqchip/irq-imx-gpcv2.c b/drivers/irqchip/irq-imx-gpcv2.c
> index bf2237ac5d09..4f74c15c4755 100644
> --- a/drivers/irqchip/irq-imx-gpcv2.c
> +++ b/drivers/irqchip/irq-imx-gpcv2.c
> @@ -131,6 +131,7 @@ static struct irq_chip gpcv2_irqchip_data_chip = {
> .irq_unmask = imx_gpcv2_irq_unmask,
> .irq_set_wake = imx_gpcv2_irq_set_wake,
> .irq_retrigger = irq_chip_retrigger_hierarchy,
> + .irq_set_type = irq_chip_set_type_parent,
> #ifdef CONFIG_SMP
> .irq_set_affinity = irq_chip_set_affinity_parent,
> #endif
> --
> 2.20.1
>
Applied, thanks.
M.
--
Jazz is not dead, it just smells funny.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-07-26 13:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 13:29 [PATCH] irqchip/irq-imx-gpcv2: forward irq type to parent Lucas Stach
2019-07-26 13:41 ` Marc Zyngier [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8636isoqut.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=jason@lakedaemon.net \
--cc=kernel@pengutronix.de \
--cc=l.stach@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=patchwork-lst@pengutronix.de \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.