[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <55B3904B.3050408@free-electrons.com>
Date: Sat, 25 Jul 2015 15:34:03 +0200
From: Gregory CLEMENT <gregory.clement@...e-electrons.com>
To: Rob Herring <robh@...nel.org>
CC: linux-arm-kernel@...ts.infradead.org,
Russell King <linux@....linux.org.uk>,
Krzysztof Kozlowski <k.kozlowski@...sung.com>,
linux-samsung-soc@...r.kernel.org, arm@...nel.org,
Alexander Shiyan <shc_work@...l.ru>,
Stephen Warren <swarren@...dotorg.org>,
Lee Jones <lee@...nel.org>, linux-kernel@...r.kernel.org,
Kukjin Kim <kgene@...nel.org>,
linux-rpi-kernel@...ts.infradead.org,
Thomas Gleixner <tglx@...utronix.de>,
Maxime Ripard <maxime.ripard@...e-electrons.com>,
Jason Cooper <jason@...edaemon.net>
Subject: Re: [PATCH v2 06/13] irqchip: kill off set_irq_flags usage
Hi Rob,
On 12/07/2015 16:26, Rob Herring wrote:
> set_irq_flags is ARM specific with custom flags which have genirq
> equivalents. Convert drivers to use the genirq interfaces directly, so we
> can kill off set_irq_flags. The translation of flags is as follows:
>
> IRQF_VALID -> !IRQ_NOREQUEST
> IRQF_PROBE -> !IRQ_NOPROBE
> IRQF_NOAUTOEN -> IRQ_NOAUTOEN
>
> For IRQs managed by an irqdomain, the irqdomain core code handles clearing
> and setting IRQ_NOREQUEST already, so there is no need to do this in
> .map() functions and we can simply remove the set_irq_flags calls. Some
> users also set IRQ_NOPROBE and this has been maintained although it is not
> clear that is really needed. There appears to be a great deal of blind
> copy and paste of this code.
>
> Signed-off-by: Rob Herring <robh@...nel.org>
> Cc: Thomas Gleixner <tglx@...utronix.de>
> Cc: Jason Cooper <jason@...edaemon.net>
> Cc: Kukjin Kim <kgene@...nel.org>
> Cc: Krzysztof Kozlowski <k.kozlowski@...sung.com>
> Cc: Stephen Warren <swarren@...dotorg.org>
> Cc: Lee Jones <lee@...nel.org>
> Cc: Alexander Shiyan <shc_work@...l.ru>
> Cc: Maxime Ripard <maxime.ripard@...e-electrons.com>
> Cc: linux-arm-kernel@...ts.infradead.org
> Cc: linux-samsung-soc@...r.kernel.org
> Cc: linux-rpi-kernel@...ts.infradead.org
> ---
> v2:
> - Fix build error on clps711x
>
[...]
> diff --git a/drivers/irqchip/irq-armada-370-xp.c b/drivers/irqchip/irq-armada-370-xp.c
> index 0d3b0fe..b8bf8b0 100644
> --- a/drivers/irqchip/irq-armada-370-xp.c
> +++ b/drivers/irqchip/irq-armada-370-xp.c
> @@ -201,7 +201,6 @@ static int armada_370_xp_msi_map(struct irq_domain *domain, unsigned int virq,
> {
> irq_set_chip_and_handler(virq, &armada_370_xp_msi_irq_chip,
> handle_simple_irq);
> - set_irq_flags(virq, IRQF_VALID);
OK
>
> return 0;
> }
> @@ -318,7 +317,7 @@ static int armada_370_xp_mpic_irq_map(struct irq_domain *h,
> irq_set_chip_and_handler(virq, &armada_370_xp_irq_chip,
> handle_level_irq);
> }
> - set_irq_flags(virq, IRQF_VALID | IRQF_PROBE);
> + irq_set_noprobe(virq);
I think it should be irq_set_probe(virq), I don't see why you inverted the probe flag.
Thanks,
Gregory
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
--
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