On Sun, Feb 19, 2023 at 5:18 PM Vivian Wang <uwu@xxxxxxxxx> wrote: > > On 1/3/23 22:14, Anup Patel wrote: > > We add DT bindings document for RISC-V advanced platform level > > interrupt controller (APLIC) defined by the RISC-V advanced > > interrupt architecture (AIA) specification. > > > > Signed-off-by: Anup Patel <apatel@xxxxxxxxxxxxxxxx> > > --- > > .../interrupt-controller/riscv,aplic.yaml | 159 ++++++++++++++++++ > > 1 file changed, 159 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/interrupt-controller/riscv,aplic.yaml > > > > diff --git a/Documentation/devicetree/bindings/interrupt-controller/riscv,aplic.yaml b/Documentation/devicetree/bindings/interrupt-controller/riscv,aplic.yaml > > new file mode 100644 > > index 000000000000..b7f20aad72c2 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/interrupt-controller/riscv,aplic.yaml > > @@ -0,0 +1,159 @@ > > > > <snip> > > > > + riscv,children: > > + $ref: /schemas/types.yaml#/definitions/phandle-array > > + minItems: 1 > > + maxItems: 1024 > > + items: > > + maxItems: 1 > > + description: > > + A list of child APLIC domains for the given APLIC domain. Each child > > + APLIC domain is assigned child index in increasing order with the > > + first child APLIC domain assigned child index 0. The APLIC domain > > + child index is used by firmware to delegate interrupts from the > > + given APLIC domain to a particular child APLIC domain. > > + > > + riscv,delegate: > > + $ref: /schemas/types.yaml#/definitions/phandle-array > > + minItems: 1 > > + maxItems: 1024 > > + items: > > + items: > > + - description: child APLIC domain phandle > > + - description: first interrupt number (inclusive) > > + - description: last interrupt number (inclusive) > > + description: > > + A interrupt delegation list where each entry is a triple consisting > > + of child APLIC domain phandle, first interrupt number, and last > > + interrupt number. The firmware will configure interrupt delegation > > + registers based on interrupt delegation list. > > + > > I'm not sure if this is the right place to ask, since it could be more > of a OpenSBI/QEMU problem, but I think a more detailed description about > what 'the firmware' does is appropriate here. > > My main confusion is how to describe wired interrupts connected to > APLICs. Say we have two APLIC nodes with labels aplic_m and aplic_s that > are the APLIC domains for M-mode and S-mode respectively. IIUC, wired > interrupts are connected directly to aplic_m. So how do I refer to it in > the device nodes? Please see my previous reply to Conor about these DT properties. The riscv,children DT property describes HW child numbering whereas the riscv,delegate DT propert is a table of IRQ delegation. In your example, let's assume we have N wired interrupts. This means we will have devices connected to the root APLIC domain (aplic_m). Now since aplic_s is a child of aplic_m, we will have N wired interrupts going from from aplic_m to aplic_s where aplic_m will route a wired/device interrupt x to aplic_s if sourcecfg[x].D = 1 and sourcecfg[x].child = 0. > > 1. <&aplic_s num IRQ_TYPE_foo>, but it would be a lie to M-mode > software, which could be a problem. QEMU 7.2.0 seems to take this > approach. (I could also be misunderstanding QEMU and it actually > does connect wired interrupts to the S-mode APLIC, but then > riscv,children and riscv,delegate would be lies.) No, it's not a lie. The <&aplic_s num IRQ_TYPE_foo> in a device DT node is based on the IRQ delegation fixed by the RISC-V platform. QEMU has its own strategy of delegating IRQs to APLIC S-mode while other platforms can use a different strategy. > 2. <&aplic_m ...>, and when M-mode software gives S-mode software > access to devices, it delegates relevant interrupts and patches it > into <&aplic_s num IRQ_TYPE_foo>. Seems to be the 'correct' > approach, but pretty complicated. The APLIC M-mode domain is not accessible to S-mode software so Linux cannot create an irqdomain using APLIC M-mode DT node. This means device DT nodes must have <&aplic_s num IRQ_TYPE_foo> which points to APLIC S-mode domain. It is totally up to RISC-V firmware and platform if it wants to dynamically add/patch <&aplic_s num IRQ_TYPE_foo> in device DT nodes. Currently, we do not patch device DT nodes in OpenSBI and instead have the device DT nodes point to correct APLIC domain based on the IRQ delegation. > 3. <&aplic_m ...>, S-mode software sees this, and sees that aplic_m has > num in riscv,delegate, so goes to find the child it's been delegated > to, which is (should be) aplic_s. A bit annoyingly abstraction > breaking, since S-mode shouldn't even need to know about aplic_m. Yes, S-mode should know about aplic_m and if it tries to access aplic_m then it will get an access fault. This is exactly why device DT node should have "interrupts" DT property pointing to the actual APLIC domain which is delivering interrupt to S-mode. > > I see that others are also confused by riscv,delegate and riscv,children > properties. It would be great if we could clarify the expected behavior > here rather than just saying 'the firmware will do the thing'. Regards, Anup
