Skip to content

Commit d9351ea

Browse files
committed
Merge branch 'irq-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip
Pull IRQ chip updates from Ingo Molnar: "A late irqchips update: - New TI INTR/INTA set of drivers - Rewrite of the stm32mp1-exti driver as a platform driver - Update the IOMMU MSI mapping API to be RT friendly - A number of cleanups and other low impact fixes" * 'irq-urgent-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip: (34 commits) iommu/dma-iommu: Remove iommu_dma_map_msi_msg() irqchip/gic-v3-mbi: Don't map the MSI page in mbi_compose_m{b, s}i_msg() irqchip/ls-scfg-msi: Don't map the MSI page in ls_scfg_msi_compose_msg() irqchip/gic-v3-its: Don't map the MSI page in its_irq_compose_msi_msg() irqchip/gicv2m: Don't map the MSI page in gicv2m_compose_msi_msg() iommu/dma-iommu: Split iommu_dma_map_msi_msg() in two parts genirq/msi: Add a new field in msi_desc to store an IOMMU cookie arm64: arch_k3: Enable interrupt controller drivers irqchip/ti-sci-inta: Add msi domain support soc: ti: Add MSI domain bus support for Interrupt Aggregator irqchip/ti-sci-inta: Add support for Interrupt Aggregator driver dt-bindings: irqchip: Introduce TISCI Interrupt Aggregator bindings irqchip/ti-sci-intr: Add support for Interrupt Router driver dt-bindings: irqchip: Introduce TISCI Interrupt router bindings gpio: thunderx: Use the default parent apis for {request,release}_resources genirq: Introduce irq_chip_{request,release}_resource_parent() apis firmware: ti_sci: Add helper apis to manage resources firmware: ti_sci: Add RM mapping table for am654 firmware: ti_sci: Add support for IRQ management firmware: ti_sci: Add support for RM core ops ...
2 parents 39feaa3 + fb4e059 commit d9351ea

38 files changed

+2511
-229
lines changed

Documentation/devicetree/bindings/arm/keystone/ti,sci.txt

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,8 @@ relationship between the TI-SCI parent node to the child node.
2424

2525
Required properties:
2626
-------------------
27-
- compatible: should be "ti,k2g-sci"
27+
- compatible: should be "ti,k2g-sci" for TI 66AK2G SoC
28+
should be "ti,am654-sci" for for TI AM654 SoC
2829
- mbox-names:
2930
"rx" - Mailbox corresponding to receive path
3031
"tx" - Mailbox corresponding to transmit path
Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,66 @@
1+
Texas Instruments K3 Interrupt Aggregator
2+
=========================================
3+
4+
The Interrupt Aggregator (INTA) provides a centralized machine
5+
which handles the termination of system events to that they can
6+
be coherently processed by the host(s) in the system. A maximum
7+
of 64 events can be mapped to a single interrupt.
8+
9+
10+
Interrupt Aggregator
11+
+-----------------------------------------+
12+
| Intmap VINT |
13+
| +--------------+ +------------+ |
14+
m ------>| | vint | bit | | 0 |.....|63| vint0 |
15+
. | +--------------+ +------------+ | +------+
16+
. | . . | | HOST |
17+
Globalevents ------>| . . |------>| IRQ |
18+
. | . . | | CTRL |
19+
. | . . | +------+
20+
n ------>| +--------------+ +------------+ |
21+
| | vint | bit | | 0 |.....|63| vintx |
22+
| +--------------+ +------------+ |
23+
| |
24+
+-----------------------------------------+
25+
26+
Configuration of these Intmap registers that maps global events to vint is done
27+
by a system controller (like the Device Memory and Security Controller on K3
28+
AM654 SoC). Driver should request the system controller to get the range
29+
of global events and vints assigned to the requesting host. Management
30+
of these requested resources should be handled by driver and requests
31+
system controller to map specific global event to vint, bit pair.
32+
33+
Communication between the host processor running an OS and the system
34+
controller happens through a protocol called TI System Control Interface
35+
(TISCI protocol). For more details refer:
36+
Documentation/devicetree/bindings/arm/keystone/ti,sci.txt
37+
38+
TISCI Interrupt Aggregator Node:
39+
-------------------------------
40+
- compatible: Must be "ti,sci-inta".
41+
- reg: Should contain registers location and length.
42+
- interrupt-controller: Identifies the node as an interrupt controller
43+
- msi-controller: Identifies the node as an MSI controller.
44+
- interrupt-parent: phandle of irq parent.
45+
- ti,sci: Phandle to TI-SCI compatible System controller node.
46+
- ti,sci-dev-id: TISCI device ID of the Interrupt Aggregator.
47+
- ti,sci-rm-range-vint: Array of TISCI subtype ids representing vints(inta
48+
outputs) range within this INTA, assigned to the
49+
requesting host context.
50+
- ti,sci-rm-range-global-event: Array of TISCI subtype ids representing the
51+
global events range reaching this IA and are assigned
52+
to the requesting host context.
53+
54+
Example:
55+
--------
56+
main_udmass_inta: interrupt-controller@33d00000 {
57+
compatible = "ti,sci-inta";
58+
reg = <0x0 0x33d00000 0x0 0x100000>;
59+
interrupt-controller;
60+
msi-controller;
61+
interrupt-parent = <&main_navss_intr>;
62+
ti,sci = <&dmsc>;
63+
ti,sci-dev-id = <179>;
64+
ti,sci-rm-range-vint = <0x0>;
65+
ti,sci-rm-range-global-event = <0x1>;
66+
};
Lines changed: 82 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,82 @@
1+
Texas Instruments K3 Interrupt Router
2+
=====================================
3+
4+
The Interrupt Router (INTR) module provides a mechanism to mux M
5+
interrupt inputs to N interrupt outputs, where all M inputs are selectable
6+
to be driven per N output. An Interrupt Router can either handle edge triggered
7+
or level triggered interrupts and that is fixed in hardware.
8+
9+
Interrupt Router
10+
+----------------------+
11+
| Inputs Outputs |
12+
+-------+ | +------+ +-----+ |
13+
| GPIO |----------->| | irq0 | | 0 | | Host IRQ
14+
+-------+ | +------+ +-----+ | controller
15+
| . . | +-------+
16+
+-------+ | . . |----->| IRQ |
17+
| INTA |----------->| . . | +-------+
18+
+-------+ | . +-----+ |
19+
| +------+ | N | |
20+
| | irqM | +-----+ |
21+
| +------+ |
22+
| |
23+
+----------------------+
24+
25+
There is one register per output (MUXCNTL_N) that controls the selection.
26+
Configuration of these MUXCNTL_N registers is done by a system controller
27+
(like the Device Memory and Security Controller on K3 AM654 SoC). System
28+
controller will keep track of the used and unused registers within the Router.
29+
Driver should request the system controller to get the range of GIC IRQs
30+
assigned to the requesting hosts. It is the drivers responsibility to keep
31+
track of Host IRQs.
32+
33+
Communication between the host processor running an OS and the system
34+
controller happens through a protocol called TI System Control Interface
35+
(TISCI protocol). For more details refer:
36+
Documentation/devicetree/bindings/arm/keystone/ti,sci.txt
37+
38+
TISCI Interrupt Router Node:
39+
----------------------------
40+
Required Properties:
41+
- compatible: Must be "ti,sci-intr".
42+
- ti,intr-trigger-type: Should be one of the following:
43+
1: If intr supports edge triggered interrupts.
44+
4: If intr supports level triggered interrupts.
45+
- interrupt-controller: Identifies the node as an interrupt controller
46+
- #interrupt-cells: Specifies the number of cells needed to encode an
47+
interrupt source. The value should be 2.
48+
First cell should contain the TISCI device ID of source
49+
Second cell should contain the interrupt source offset
50+
within the device.
51+
- ti,sci: Phandle to TI-SCI compatible System controller node.
52+
- ti,sci-dst-id: TISCI device ID of the destination IRQ controller.
53+
- ti,sci-rm-range-girq: Array of TISCI subtype ids representing the host irqs
54+
assigned to this interrupt router. Each subtype id
55+
corresponds to a range of host irqs.
56+
57+
For more details on TISCI IRQ resource management refer:
58+
http://downloads.ti.com/tisci/esd/latest/2_tisci_msgs/rm/rm_irq.html
59+
60+
Example:
61+
--------
62+
The following example demonstrates both interrupt router node and the consumer
63+
node(main gpio) on the AM654 SoC:
64+
65+
main_intr: interrupt-controller0 {
66+
compatible = "ti,sci-intr";
67+
ti,intr-trigger-type = <1>;
68+
interrupt-controller;
69+
interrupt-parent = <&gic500>;
70+
#interrupt-cells = <2>;
71+
ti,sci = <&dmsc>;
72+
ti,sci-dst-id = <56>;
73+
ti,sci-rm-range-girq = <0x1>;
74+
};
75+
76+
main_gpio0: gpio@600000 {
77+
...
78+
interrupt-parent = <&main_intr>;
79+
interrupts = <57 256>, <57 257>, <57 258>,
80+
<57 259>, <57 260>, <57 261>;
81+
...
82+
};

MAINTAINERS

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15547,6 +15547,12 @@ F: Documentation/devicetree/bindings/reset/ti,sci-reset.txt
1554715547
F: Documentation/devicetree/bindings/clock/ti,sci-clk.txt
1554815548
F: drivers/clk/keystone/sci-clk.c
1554915549
F: drivers/reset/reset-ti-sci.c
15550+
F: Documentation/devicetree/bindings/interrupt-controller/ti,sci-intr.txt
15551+
F: Documentation/devicetree/bindings/interrupt-controller/ti,sci-inta.txt
15552+
F: drivers/irqchip/irq-ti-sci-intr.c
15553+
F: drivers/irqchip/irq-ti-sci-inta.c
15554+
F: include/linux/soc/ti/ti_sci_inta_msi.h
15555+
F: drivers/soc/ti/ti_sci_inta_msi.c
1555015556

1555115557
Texas Instruments ASoC drivers
1555215558
M: Peter Ujfalusi <[email protected]>

arch/arm64/Kconfig.platforms

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -87,6 +87,11 @@ config ARCH_EXYNOS
8787
config ARCH_K3
8888
bool "Texas Instruments Inc. K3 multicore SoC architecture"
8989
select PM_GENERIC_DOMAINS if PM
90+
select MAILBOX
91+
select TI_MESSAGE_MANAGER
92+
select TI_SCI_PROTOCOL
93+
select TI_SCI_INTR_IRQCHIP
94+
select TI_SCI_INTA_IRQCHIP
9095
help
9196
This enables support for Texas Instruments' K3 multicore SoC
9297
architecture.

0 commit comments

Comments
 (0)