UbiquitousOS
/
OpenCloudOS-Kernel
mirror of https://gitee.com/OpenCloudOS/OpenCloudOS-Kernel.git
11
0
Fork 0
Code Issues Projects Releases Wiki Activity

dt-bindings: irqchip: ti, sci-inta: Update docs to support different parent. 

Drop the firmware related interrupt ranges and use the hardware specified
interrupt numbers within Interrupt Aggregator. This ensures interrupt
aggregator DT node need not assume any interrupt parent type.

Signed-off-by: Lokesh Vutla <lokeshvutla@ti.com>
Signed-off-by: Marc Zyngier <maz@kernel.org>
Reviewed-by: Rob Herring <robh@kernel.org>
Link: https://lore.kernel.org/r/20200806074826.24607-8-lokeshvutla@ti.com
This commit is contained in:
Lokesh Vutla 2020-08-06 13:18:20 +05:30 committed by Marc Zyngier
parent a5b659bd4b
commit 6dde29dc31
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
Documentation/devicetree/bindings/interrupt-controller/ti,sci-inta.txt
View File

@ -43,13 +43,14 @@ TISCI Interrupt Aggregator Node:
- msi-controller: Identifies the node as an MSI controller. - msi-controller: Identifies the node as an MSI controller.
- interrupt-parent: phandle of irq parent. - interrupt-parent: phandle of irq parent.
- ti,sci: Phandle to TI-SCI compatible System controller node. - ti,sci: Phandle to TI-SCI compatible System controller node.
- ti,sci-dev-id: TISCI device ID of the Interrupt Aggregator. - ti,sci-dev-id: TISCI device id of interrupt controller.
- ti,sci-rm-range-vint: Array of TISCI subtype ids representing vints(inta - ti,interrupt-ranges: Set of triplets containing ranges that convert
outputs) range within this INTA, assigned to the the INTA output interrupt numbers to parent's
requesting host context. interrupt number. Each triplet has following entries:
- ti,sci-rm-range-global-event: Array of TISCI subtype ids representing the - First entry specifies the base for vint
global events range reaching this IA and are assigned - Second entry specifies the base for parent irqs
to the requesting host context. - Third entry specifies the limit
Example: Example:
-------- --------
@ -61,6 +62,5 @@ main_udmass_inta: interrupt-controller@33d00000 {
interrupt-parent = <&main_navss_intr>; interrupt-parent = <&main_navss_intr>;
ti,sci = <&dmsc>; ti,sci = <&dmsc>;
ti,sci-dev-id = <179>; ti,sci-dev-id = <179>;
ti,sci-rm-range-vint = <0x0>; ti,interrupt-ranges = <0 0 256>;
ti,sci-rm-range-global-event = <0x1>;
}; };