irqchip: add basic infrastructure
With the recent creation of the drivers/irqchip/ directory, it is
desirable to move irq controller drivers here. At the moment, the only
driver here is irq-bcm2835, the driver for the irq controller found in
the ARM BCM2835 SoC, present in Rasberry Pi systems. This irq
controller driver was exporting its initialization function and its
irq handling function through a header file in
<linux/irqchip/bcm2835.h>.
When proposing to also move another irq controller driver in
drivers/irqchip, Rob Herring raised the very valid point that moving
things to drivers/irqchip was good in order to remove more stuff from
arch/arm, but if it means adding gazillions of headers files in
include/linux/irqchip/, it would not be very nice.
So, upon the suggestion of Rob Herring and Arnd Bergmann, this commit
introduces a small infrastructure that defines a central
irqchip_init() function in drivers/irqchip/irqchip.c, which is meant
to be called as the ->init_irq() callback of ARM platforms. This
function calls of_irq_init() with an array of match strings and init
functions generated from a special linker section.
Note that the irq controller driver initialization function is
responsible for setting the global handle_arch_irq() variable, so that
ARM platforms no longer have to define the ->handle_irq field in their
DT_MACHINE structure.
A global header, <linux/irqchip.h> is also added to expose the single
irqchip_init() function to the reset of the kernel.
A further commit moves the BCM2835 irq controller driver to this new
small infrastructure, therefore removing the include/linux/irqchip/
directory.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Reviewed-by: Stephen Warren <swarren@wwwdotorg.org>
Reviewed-by: Rob Herring <rob.herring@calxeda.com>
Acked-by: Arnd Bergmann <arnd@arndb.de>
[rob.herring: reword commit message to reflect use of linker sections.]
Signed-off-by: Rob Herring <rob.herring@calxeda.com>
2012-11-20 22:00:52 +00:00
|
|
|
config IRQCHIP
|
|
|
|
|
def_bool y
|
|
|
|
|
depends on OF_IRQ
|
|
|
|
|
|
2012-11-21 03:21:40 +00:00
|
|
|
config ARM_GIC
|
|
|
|
|
bool
|
|
|
|
|
select IRQ_DOMAIN
|
2014-11-25 08:04:19 +00:00
|
|
|
select IRQ_DOMAIN_HIERARCHY
|
2012-11-21 03:21:40 +00:00
|
|
|
select MULTI_IRQ_HANDLER
|
|
|
|
|
|
2015-12-18 09:44:53 +00:00
|
|
|
config ARM_GIC_MAX_NR
|
|
|
|
|
int
|
|
|
|
|
default 2 if ARCH_REALVIEW
|
|
|
|
|
default 1
|
|
|
|
|
|
2014-11-25 18:47:22 +00:00
|
|
|
config ARM_GIC_V2M
|
|
|
|
|
bool
|
|
|
|
|
depends on ARM_GIC
|
|
|
|
|
depends on PCI && PCI_MSI
|
|
|
|
|
select PCI_MSI_IRQ_DOMAIN
|
|
|
|
|
|
2012-11-21 03:21:40 +00:00
|
|
|
config GIC_NON_BANKED
|
|
|
|
|
bool
|
|
|
|
|
|
2014-06-30 15:01:31 +00:00
|
|
|
config ARM_GIC_V3
|
|
|
|
|
bool
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
select MULTI_IRQ_HANDLER
|
2014-11-24 14:35:09 +00:00
|
|
|
select IRQ_DOMAIN_HIERARCHY
|
2014-06-30 15:01:31 +00:00
|
|
|
|
2014-11-24 14:35:19 +00:00
|
|
|
config ARM_GIC_V3_ITS
|
|
|
|
|
bool
|
|
|
|
|
select PCI_MSI_IRQ_DOMAIN
|
2014-06-30 15:01:31 +00:00
|
|
|
|
irqchip/mgigen: Add platform device driver for mbigen device
Mbigen means Message Based Interrupt Generator(MBIGEN).
Its a kind of interrupt controller that collects
the interrupts from external devices and generate msi interrupt.
Mbigen is applied to reduce the number of wire connected interrupts.
As the peripherals increasing, the interrupts lines needed is
increasing much, especially on the Arm64 server SOC.
Therefore, the interrupt pin in GIC is not enough to cover so
many peripherals.
Mbigen is designed to fix this problem.
Mbigen chip locates in ITS or outside of ITS.
Mbigen chip hardware structure shows as below:
mbigen chip
|---------------------|-------------------|
mgn_node0 mgn_node1 mgn_node2
| |-------| |-------|------|
dev1 dev1 dev2 dev1 dev3 dev4
Each mbigen chip contains several mbigen nodes.
External devices can connect to mbigen node through wire connecting way.
Because a mbigen node only can support 128 interrupt maximum, depends
on the interrupt lines number of devices, a device can connects to one
more mbigen nodes.
Also, several different devices can connect to a same mbigen node.
When devices triggered interrupt,mbigen chip detects and collects
the interrupts and generates the MBI interrupts by writing the ITS
Translator register.
To simplify mbigen driver,I used a new conception--mbigen device.
Each mbigen device is initialized as a platform device.
Mbigen device presents the parts(register, pin definition etc.) in
mbigen chip corresponding to a peripheral device.
So from software view, the structure likes below
mbigen chip
|---------------------|-----------------|
mbigen device1 mbigen device2 mbigen device3
| | |
dev1 dev2 dev3
Reviewed-by: Marc Zyngier <marc.zyngier@arm.com>
Signed-off-by: Ma Jun <majun258@huawei.com>
Signed-off-by: Marc Zyngier <marc.zyngier@arm.com>
2015-12-17 11:56:35 +00:00
|
|
|
config HISILICON_IRQ_MBIGEN
|
|
|
|
|
bool "Support mbigen interrupt controller"
|
|
|
|
|
default n
|
|
|
|
|
depends on ARM_GIC_V3 && ARM_GIC_V3_ITS && GENERIC_MSI_IRQ_DOMAIN
|
|
|
|
|
help
|
|
|
|
|
Enable the mbigen interrupt controller used on
|
|
|
|
|
Hisilicon platform.
|
|
|
|
|
|
2013-06-26 07:18:48 +00:00
|
|
|
config ARM_NVIC
|
|
|
|
|
bool
|
|
|
|
|
select IRQ_DOMAIN
|
2015-05-16 09:44:16 +00:00
|
|
|
select IRQ_DOMAIN_HIERARCHY
|
2013-06-26 07:18:48 +00:00
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
|
2012-10-27 22:25:26 +00:00
|
|
|
config ARM_VIC
|
|
|
|
|
bool
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
select MULTI_IRQ_HANDLER
|
|
|
|
|
|
|
|
|
|
config ARM_VIC_NR
|
|
|
|
|
int
|
|
|
|
|
default 4 if ARCH_S5PV210
|
|
|
|
|
default 2
|
|
|
|
|
depends on ARM_VIC
|
|
|
|
|
help
|
|
|
|
|
The maximum number of VICs available in the system, for
|
|
|
|
|
power management.
|
|
|
|
|
|
2016-02-10 14:46:56 +00:00
|
|
|
config ARMADA_370_XP_IRQ
|
|
|
|
|
bool
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
2016-02-10 14:46:57 +00:00
|
|
|
select PCI_MSI_IRQ_DOMAIN if PCI_MSI
|
2016-02-10 14:46:56 +00:00
|
|
|
|
2014-07-10 17:14:18 +00:00
|
|
|
config ATMEL_AIC_IRQ
|
|
|
|
|
bool
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
select MULTI_IRQ_HANDLER
|
|
|
|
|
select SPARSE_IRQ
|
|
|
|
|
|
|
|
|
|
config ATMEL_AIC5_IRQ
|
|
|
|
|
bool
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
select MULTI_IRQ_HANDLER
|
|
|
|
|
select SPARSE_IRQ
|
|
|
|
|
|
2015-07-08 12:46:08 +00:00
|
|
|
config I8259
|
|
|
|
|
bool
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
|
IRQCHIP: Add new driver for BCM7038-style level 1 interrupt controllers
This is the main peripheral IRQ controller on the BCM7xxx MIPS chips;
it has the following characteristics:
- 64 to 160+ level IRQs
- Atomic set/clear registers
- Reasonably predictable register layout (N status words, then N
mask status words, then N mask set words, then N mask clear words)
- SMP affinity supported on most systems
- Typically connected to MIPS IRQ 2,3,2,3 on CPUs 0,1,2,3
This driver registers one IRQ domain and one IRQ chip to cover all
instances of the block. Up to 4 instances of the block may appear, as
it supports 4-way IRQ affinity on BCM7435.
The same block exists on the ARM BCM7xxx chips, but typically the ARM GIC
is used instead. So this driver is primarily intended for MIPS STB chips.
Signed-off-by: Kevin Cernekee <cernekee@gmail.com>
Cc: f.fainelli@gmail.com
Cc: jaedon.shin@gmail.com
Cc: abrestic@chromium.org
Cc: tglx@linutronix.de
Cc: jason@lakedaemon.net
Cc: jogo@openwrt.org
Cc: arnd@arndb.de
Cc: computersforpeace@gmail.com
Cc: linux-mips@linux-mips.org
Cc: devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Patchwork: https://patchwork.linux-mips.org/patch/8844/
Signed-off-by: Ralf Baechle <ralf@linux-mips.org>
2014-12-25 17:49:06 +00:00
|
|
|
config BCM7038_L1_IRQ
|
|
|
|
|
bool
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
|
2014-11-07 06:44:27 +00:00
|
|
|
config BCM7120_L2_IRQ
|
|
|
|
|
bool
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
|
2014-05-24 00:40:53 +00:00
|
|
|
config BRCMSTB_L2_IRQ
|
|
|
|
|
bool
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
|
2013-09-09 12:01:20 +00:00
|
|
|
config DW_APB_ICTL
|
|
|
|
|
bool
|
2014-10-22 12:59:10 +00:00
|
|
|
select GENERIC_IRQ_CHIP
|
2013-09-09 12:01:20 +00:00
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
|
2013-04-22 14:43:50 +00:00
|
|
|
config IMGPDC_IRQ
|
|
|
|
|
bool
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
|
2015-05-26 16:20:06 +00:00
|
|
|
config IRQ_MIPS_CPU
|
|
|
|
|
bool
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
|
2014-02-02 08:07:46 +00:00
|
|
|
config CLPS711X_IRQCHIP
|
|
|
|
|
bool
|
|
|
|
|
depends on ARCH_CLPS711X
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
select MULTI_IRQ_HANDLER
|
|
|
|
|
select SPARSE_IRQ
|
|
|
|
|
default y
|
|
|
|
|
|
2014-05-26 20:31:42 +00:00
|
|
|
config OR1K_PIC
|
|
|
|
|
bool
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
|
2014-09-15 21:15:02 +00:00
|
|
|
config OMAP_IRQCHIP
|
|
|
|
|
bool
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
|
2013-06-06 16:27:09 +00:00
|
|
|
config ORION_IRQCHIP
|
|
|
|
|
bool
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
select MULTI_IRQ_HANDLER
|
|
|
|
|
|
2016-01-14 01:15:35 +00:00
|
|
|
config PIC32_EVIC
|
|
|
|
|
bool
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
|
2013-02-18 14:28:34 +00:00
|
|
|
config RENESAS_INTC_IRQPIN
|
|
|
|
|
bool
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
|
2013-02-27 08:15:01 +00:00
|
|
|
config RENESAS_IRQC
|
|
|
|
|
bool
|
2015-09-28 09:42:37 +00:00
|
|
|
select GENERIC_IRQ_CHIP
|
2013-02-27 08:15:01 +00:00
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
|
2015-02-18 15:13:58 +00:00
|
|
|
config ST_IRQCHIP
|
|
|
|
|
bool
|
|
|
|
|
select REGMAP
|
|
|
|
|
select MFD_SYSCON
|
|
|
|
|
help
|
|
|
|
|
Enables SysCfg Controlled IRQs on STi based platforms.
|
|
|
|
|
|
2013-06-25 16:29:57 +00:00
|
|
|
config TB10X_IRQC
|
|
|
|
|
bool
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
select GENERIC_IRQ_CHIP
|
|
|
|
|
|
2015-12-21 20:11:23 +00:00
|
|
|
config TS4800_IRQ
|
|
|
|
|
tristate "TS-4800 IRQ controller"
|
|
|
|
|
select IRQ_DOMAIN
|
2016-01-25 22:24:17 +00:00
|
|
|
depends on HAS_IOMEM
|
2015-12-21 20:11:23 +00:00
|
|
|
help
|
|
|
|
|
Support for the TS-4800 FPGA IRQ controller
|
|
|
|
|
|
2012-10-31 21:04:31 +00:00
|
|
|
config VERSATILE_FPGA_IRQ
|
|
|
|
|
bool
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
|
|
|
|
|
config VERSATILE_FPGA_IRQ_NR
|
|
|
|
|
int
|
|
|
|
|
default 4
|
|
|
|
|
depends on VERSATILE_FPGA_IRQ
|
2013-12-01 08:04:57 +00:00
|
|
|
|
|
|
|
|
config XTENSA_MX
|
|
|
|
|
bool
|
|
|
|
|
select IRQ_DOMAIN
|
2013-12-03 10:27:23 +00:00
|
|
|
|
|
|
|
|
config IRQ_CROSSBAR
|
|
|
|
|
bool
|
|
|
|
|
help
|
2014-09-18 03:09:42 +00:00
|
|
|
Support for a CROSSBAR ip that precedes the main interrupt controller.
|
2013-12-03 10:27:23 +00:00
|
|
|
The primary irqchip invokes the crossbar's callback which inturn allocates
|
|
|
|
|
a free irq and configures the IP. Thus the peripheral interrupts are
|
|
|
|
|
routed to one of the free irqchip interrupt lines.
|
2014-07-23 14:40:30 +00:00
|
|
|
|
|
|
|
|
config KEYSTONE_IRQ
|
|
|
|
|
tristate "Keystone 2 IRQ controller IP"
|
|
|
|
|
depends on ARCH_KEYSTONE
|
|
|
|
|
help
|
|
|
|
|
Support for Texas Instruments Keystone 2 IRQ controller IP which
|
|
|
|
|
is part of the Keystone 2 IPC mechanism
|
2014-09-18 21:47:19 +00:00
|
|
|
|
|
|
|
|
config MIPS_GIC
|
|
|
|
|
bool
|
|
|
|
|
select MIPS_CM
|
2015-05-09 17:30:47 +00:00
|
|
|
|
2015-05-24 15:11:31 +00:00
|
|
|
config INGENIC_IRQ
|
|
|
|
|
bool
|
|
|
|
|
depends on MACH_INGENIC
|
|
|
|
|
default y
|
2015-06-27 19:44:34 +00:00
|
|
|
|
2015-05-09 17:30:47 +00:00
|
|
|
config RENESAS_H8300H_INTC
|
|
|
|
|
bool
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
|
|
|
|
|
config RENESAS_H8S_INTC
|
|
|
|
|
bool
|
2015-06-27 19:44:34 +00:00
|
|
|
select IRQ_DOMAIN
|
2015-08-24 19:04:15 +00:00
|
|
|
|
|
|
|
|
config IMX_GPCV2
|
|
|
|
|
bool
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
help
|
|
|
|
|
Enables the wakeup IRQs for IMX platforms with GPCv2 block
|
2015-10-12 19:15:34 +00:00
|
|
|
|
|
|
|
|
config IRQ_MXS
|
|
|
|
|
def_bool y if MACH_ASM9260 || ARCH_MXS
|
|
|
|
|
select IRQ_DOMAIN
|
|
|
|
|
select STMP_DEVICE
|
