irqdomain: Avoid activating interrupts more than once

Since commit f3b0946d629c ("genirq/msi: Make sure PCI MSIs are
activated early"), we can end-up activating a PCI/MSI twice (once
at allocation time, and once at startup time).

This is normally of no consequences, except that there is some
HW out there that may misbehave if activate is used more than once
(the GICv3 ITS, for example, uses the activate callback
to issue the MAPVI command, and the architecture spec says that
"If there is an existing mapping for the EventID-DeviceID
combination, behavior is UNPREDICTABLE").

While this could be worked around in each individual driver, it may
make more sense to tackle the issue at the core level. In order to
avoid getting in that situation, let's have a per-interrupt flag
to remember if we have already activated that interrupt or not.

Fixes: f3b0946d629c ("genirq/msi: Make sure PCI MSIs are activated early")
Reported-and-tested-by: Andre Przywara <andre.przywara@arm.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
Cc: stable@vger.kernel.org
Link: http://lkml.kernel.org/r/1484668848-24361-1-git-send-email-marc.zyngier@arm.com
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>

path: root/net/irda/irnet/Kconfig

config IRNET
	tristate "IrNET protocol"
	depends on IRDA && PPP
	help
	  Say Y here if you want to build support for the IrNET protocol.
	  To compile it as a module, choose M here: the module will be
	  called irnet.  IrNET is a PPP driver, so you will also need a
	  working PPP subsystem (driver, daemon and config)...

	  IrNET is an alternate way to transfer TCP/IP traffic over IrDA.  It
	  uses synchronous PPP over a set of point to point IrDA sockets.  You
	  can use it between Linux machine or with W2k.