[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20210113104057.GF10351@alpha.franken.de>
Date: Wed, 13 Jan 2021 11:40:57 +0100
From: Thomas Bogendoerfer <tsbogend@...ha.franken.de>
To: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Cc: linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org,
john@...ozen.org, hauke@...ke-m.de
Subject: Re: [PATCH] MIPS: lantiq: irq: register the interrupt controllers
with irqchip_init
On Sat, Jan 09, 2021 at 08:53:51PM +0100, Martin Blumenstingl wrote:
> Add support for more interrupt controllers by switching from
> of_irq_init() to irqchip_init() in Lantiq's arch_init_irq(). This
> requires switching the ICU interrupt controller to use
> IRQCHIP_DECLARE(), like a real irqchip driver would do.
>
> This is needed for future changes when new irqchip drivers are
> implemented:
> - a dedicated driver for the EIU interrupt controller
> - a driver for the MSI PIC (Programmable Interrupt Controller) found on
> VRX200 and newer SoCs
> - ..or any other driver which uses IRQCHIP_DECLARE
>
> Signed-off-by: Martin Blumenstingl <martin.blumenstingl@...glemail.com>
> ---
> arch/mips/lantiq/irq.c | 8 +++-----
> 1 file changed, 3 insertions(+), 5 deletions(-)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
Powered by blists - more mailing lists