1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
2 # Copyright (C) 2020 SiFive, Inc.
5 $id: http://devicetree.org/schemas/interrupt-controller/sifive,plic-1.0.0.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: SiFive Platform-Level Interrupt Controller (PLIC)
11 SiFive SoCs and other RISC-V SoCs include an implementation of the
12 Platform-Level Interrupt Controller (PLIC) high-level specification in
13 the RISC-V Privileged Architecture specification. The PLIC connects all
14 external interrupts in the system to all hart contexts in the system, via
15 the external interrupt source in each hart.
17 A hart context is a privilege mode in a hardware execution thread. For example,
18 in an 4 core system with 2-way SMT, you have 8 harts and probably at least two
19 privilege modes per hart; machine mode and supervisor mode.
21 Each interrupt can be enabled on per-context basis. Any context can claim
22 a pending enabled interrupt and then release it once it has been handled.
24 Each interrupt has a configurable priority. Higher priority interrupts are
25 serviced first. Each context can specify a priority threshold. Interrupts
26 with priority below this threshold will not cause the PLIC to raise its
27 interrupt line leading to the context.
29 The PLIC supports both edge-triggered and level-triggered interrupts. For
30 edge-triggered interrupts, the RISC-V PLIC spec allows two responses to edges
31 seen while an interrupt handler is active; the PLIC may either queue them or
32 ignore them. In the first case, handlers are oblivious to the trigger type, so
33 it is not included in the interrupt specifier. In the second case, software
34 needs to know the trigger type, so it can reorder the interrupt flow to avoid
35 missing interrupts. This special handling is needed by at least the Renesas
36 RZ/Five SoC (AX45MP AndesCore with a NCEPLIC100) and the T-HEAD C900 PLIC.
38 While the RISC-V ISA doesn't specify a memory layout for the PLIC, the
39 "sifive,plic-1.0.0" device is a concrete implementation of the PLIC that
40 contains a specific memory layout, which is documented in chapter 8 of the
41 SiFive U5 Coreplex Series Manual <https://static.dev.sifive.com/U54-MC-RVCoreIP.pdf>.
43 The thead,c900-plic is different from sifive,plic-1.0.0 in opensbi, the
44 T-HEAD PLIC implementation requires setting a delegation bit to allow access
45 from S-mode. So add thead,c900-plic to distinguish them.
48 - Paul Walmsley <paul.walmsley@sifive.com>
49 - Palmer Dabbelt <palmer@dabbelt.com>
56 - renesas,r9a07g043-plic
57 - const: andestech,nceplic100
61 - sifive,fu540-c000-plic
62 - starfive,jh7100-plic
63 - starfive,jh7110-plic
64 - const: sifive,plic-1.0.0
67 - allwinner,sun20i-d1-plic
73 - const: thead,c900-plic
75 - const: sifive,plic-1.0.0
78 description: For the QEMU virt machine only
86 '#interrupt-cells': true
88 interrupt-controller: true
94 Specifies which contexts are connected to the PLIC, with "-1" specifying
95 that a context is not present. Each node pointed to should be a
96 riscv,cpu-intc node, which has a riscv node as parent.
99 $ref: /schemas/types.yaml#/definitions/uint32
101 Specifies how many external interrupts are supported by this controller.
113 - interrupt-controller
115 - interrupts-extended
124 - andestech,nceplic100
141 const: renesas,r9a07g043-plic
159 additionalProperties: false
163 plic: interrupt-controller@c000000 {
164 #address-cells = <0>;
165 #interrupt-cells = <1>;
166 compatible = "sifive,fu540-c000-plic", "sifive,plic-1.0.0";
167 interrupt-controller;
168 interrupts-extended = <&cpu0_intc 11>,
169 <&cpu1_intc 11>, <&cpu1_intc 9>,
170 <&cpu2_intc 11>, <&cpu2_intc 9>,
171 <&cpu3_intc 11>, <&cpu3_intc 9>,
172 <&cpu4_intc 11>, <&cpu4_intc 9>;
173 reg = <0xc000000 0x4000000>;