From: Thomas Gleixner <tglx@linutronix.de>
To: Rob Herring <robh@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
Russell King <linux@arm.linux.org.uk>,
linux-kernel@vger.kernel.org, arm@kernel.org,
Jason Cooper <jason@lakedaemon.net>,
Kukjin Kim <kgene@kernel.org>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Stephen Warren <swarren@wwwdotorg.org>,
Lee Jones <lee@kernel.org>, Alexander Shiyan <shc_work@mail.ru>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
linux-samsung-soc@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH v2 06/13] irqchip: kill off set_irq_flags usage
Date: Sun, 12 Jul 2015 18:43:56 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.11.1507121737030.20072@nanos> (raw)
In-Reply-To: <1436711211-18223-7-git-send-email-robh@kernel.org>
On Sun, 12 Jul 2015, 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 IRQ_NOPROBE, right?
> clear that is really needed. There appears to be a great deal of blind
> copy and paste of this code.
Looking at the irq probe users:
drivers/input/touchscreen/ucb1400_ts.c
drivers/mfd/ucb1x00-core.c
The probe function was added in the initial implementation of the
driver (2006), so it predates device tree.
drivers/net/appletalk/ltpc.c
drivers/net/arcnet/com20020-isa.c
drivers/net/arcnet/com90io.c
drivers/net/arcnet/com90xx.c
Surely not stuff you find on todays ARM systems
drivers/net/ethernet/8390/ne.c
drivers/net/ethernet/8390/wd.c
drivers/net/ethernet/amd/lance.c
drivers/net/ethernet/amd/ni65.c
drivers/net/ethernet/amd/pcnet32.c
Ditto
drivers/net/ethernet/smsc/smc911x.c
drivers/net/ethernet/smsc/smc9194.c
drivers/net/ethernet/smsc/smc91x.c
Those might still be, but on the DT based boards the probing should be
completely irrelevant
drivers/net/hamradio/dmascc.c
drivers/net/wan/cosa.c
drivers/net/wan/sbni.c
drivers/parport/parport_pc.c
Surely not stuff you find on todays ARM systems
drivers/pcmcia/yenta_socket.c
Russell might still use that.
drivers/scsi/NCR53c406a.c
drivers/scsi/sym53c416.c
drivers/tty/cyclades.c
Surely not stuff you find on todays ARM systems
drivers/tty/serial/8250/8250_core.c
The irq probing is used by
mach-imx/mach-mx31ads.c
mach-iop32x/n2100.c
and X86
So in most of the irqchip drivers, this is irrelevant.
Thanks,
tglx
next prev parent reply other threads:[~2015-07-12 16:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1436711211-18223-1-git-send-email-robh@kernel.org>
2015-07-12 14:26 ` [PATCH v2 01/13] ARM: kill off set_irq_flags usage Rob Herring
2015-07-13 3:19 ` Shawn Guo
2015-07-14 21:14 ` Robert Jarzmik
2015-07-12 14:26 ` [PATCH v2 06/13] irqchip: " Rob Herring
2015-07-12 16:43 ` Thomas Gleixner [this message]
2015-07-13 16:26 ` Rob Herring
2015-07-16 11:10 ` Thomas Gleixner
2015-07-16 13:26 ` Russell King - ARM Linux
2015-07-16 19:32 ` Robert Jarzmik
2015-07-16 20:34 ` Russell King - ARM Linux
2015-07-25 13:34 ` Gregory CLEMENT
2015-07-27 18:39 ` Rob Herring
2015-07-12 14:26 ` [PATCH v2 10/13] pinctrl: " Rob Herring
2015-07-12 15:45 ` Tomasz Figa
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=alpine.DEB.2.11.1507121737030.20072@nanos \
--to=tglx@linutronix.de \
--cc=arm@kernel.org \
--cc=jason@lakedaemon.net \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=maxime.ripard@free-electrons.com \
--cc=robh@kernel.org \
--cc=shc_work@mail.ru \
--cc=swarren@wwwdotorg.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox