linux-kernel - Re: [PATCH] irqchip/irq-imx-gpcv2: add IRQCHIP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Mon, 17 Dec 2018 16:51:21 +0100
From:   Lucas Stach <l.stach@...gutronix.de>
To:     Marc Zyngier <marc.zyngier@....com>,
        Andrey Smirnov <andrew.smirnov@...il.com>
Cc:     Thomas Gleixner <tglx@...utronix.de>, patchwork-lst@...gutronix.de,
        Jason Cooper <jason@...edaemon.net>, kernel@...gutronix.de,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH] irqchip/irq-imx-gpcv2: add IRQCHIP_DECLARE for i.MX8MQ
 compatible

Hi Marc,

Am Freitag, den 14.12.2018, 13:15 +0100 schrieb Lucas Stach:
> The GPC node on i.MX8MQ can not claim to be compatible with the i.MX7D
> GPC, as the power gating part has some significant differences. Thus we
> can not rely on the irqchip being probed with the old compatible.
> 
> > Signed-off-by: Lucas Stach <l.stach@...gutronix.de>
> ---
>  drivers/irqchip/irq-imx-gpcv2.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/irqchip/irq-imx-gpcv2.c b/drivers/irqchip/irq-imx-gpcv2.c
> index 17a2dad2d4c2..68b9cca24044 100644
> --- a/drivers/irqchip/irq-imx-gpcv2.c
> +++ b/drivers/irqchip/irq-imx-gpcv2.c
> @@ -289,4 +289,5 @@ static int __init imx_gpcv2_irqchip_init(struct device_node *node,
> >  	return 0;
>  }
>  
> -IRQCHIP_DECLARE(imx_gpcv2, "fsl,imx7d-gpc", imx_gpcv2_irqchip_init);
> +IRQCHIP_DECLARE(imx_gpcv2_imx7d, "fsl,imx7d-gpc", imx_gpcv2_irqchip_init);
> +IRQCHIP_DECLARE(imx_gpcv2_imx8mq, "fsl,imx8mq-gpc", imx_gpcv2_irqchip_init);

It would be nice if we could get this into 4.21, as this is the last
missing bit preventing me from pushing forward on the patches
describing the i.MX8MQ IRQ hierarchy properly for the next cycle.

Regards,
Lucas