1 * SPEAr Shared IRQ layer (shirq) 1 * SPEAr Shared IRQ layer (shirq)
2 2
3 SPEAr3xx architecture includes shared/multiple 3 SPEAr3xx architecture includes shared/multiplexed irqs for certain set
4 of devices. The multiplexor provides a single 4 of devices. The multiplexor provides a single interrupt to parent
5 interrupt controller (VIC) on behalf of a grou 5 interrupt controller (VIC) on behalf of a group of devices.
6 6
7 There can be multiple groups available on SPEA 7 There can be multiple groups available on SPEAr3xx variants but not
8 exceeding 4. The number of devices in a group 8 exceeding 4. The number of devices in a group can differ, further they
9 may share same set of status/mask registers sp 9 may share same set of status/mask registers spanning across different
10 bit masks. Also in some cases the group may no 10 bit masks. Also in some cases the group may not have enable or other
11 registers. This makes software little complex. 11 registers. This makes software little complex.
12 12
13 A single node in the device tree is used to de 13 A single node in the device tree is used to describe the shared
14 interrupt multiplexor (one node for all groups 14 interrupt multiplexor (one node for all groups). A group in the
15 interrupt controller shares config/control reg 15 interrupt controller shares config/control registers with other groups.
16 For example, a 32-bit interrupt enable/disable 16 For example, a 32-bit interrupt enable/disable config register can
17 accommodate up to 4 interrupt groups. 17 accommodate up to 4 interrupt groups.
18 18
19 Required properties: 19 Required properties:
20 - compatible: should be, either of 20 - compatible: should be, either of
21 - "st,spear300-shirq" 21 - "st,spear300-shirq"
22 - "st,spear310-shirq" 22 - "st,spear310-shirq"
23 - "st,spear320-shirq" 23 - "st,spear320-shirq"
24 - interrupt-controller: Identifies the node 24 - interrupt-controller: Identifies the node as an interrupt controller.
25 - #interrupt-cells: should be <1> which basi 25 - #interrupt-cells: should be <1> which basically contains the offset
26 (starting from 0) of interrupts for all th 26 (starting from 0) of interrupts for all the groups.
27 - reg: Base address and size of shirq regist 27 - reg: Base address and size of shirq registers.
28 - interrupts: The list of interrupts generat 28 - interrupts: The list of interrupts generated by the groups which are
29 then connected to a parent interrupt contr 29 then connected to a parent interrupt controller. Each group is
30 associated with one of the interrupts, hen 30 associated with one of the interrupts, hence number of interrupts (to
31 parent) is equal to number of groups. The 31 parent) is equal to number of groups. The format of the interrupt
32 specifier depends in the interrupt parent 32 specifier depends in the interrupt parent controller.
33 33
>> 34 Optional properties:
>> 35 - interrupt-parent: pHandle of the parent interrupt controller, if not
>> 36 inherited from the parent node.
>> 37
34 Example: 38 Example:
35 39
36 The following is an example from the SPEAr320 40 The following is an example from the SPEAr320 SoC dtsi file.
37 41
38 shirq: interrupt-controller@b3000000 { 42 shirq: interrupt-controller@b3000000 {
39 compatible = "st,spear320-shirq"; 43 compatible = "st,spear320-shirq";
40 reg = <0xb3000000 0x1000>; 44 reg = <0xb3000000 0x1000>;
41 interrupts = <28 29 30 1>; 45 interrupts = <28 29 30 1>;
42 #interrupt-cells = <1>; 46 #interrupt-cells = <1>;
43 interrupt-controller; 47 interrupt-controller;
44 }; 48 };
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.