On Wed, 18 Jun 2025 12:17:16 +0200, Lorenzo Pieralisi wrote: > The GICv5 interrupt controller architecture is composed of: > > - one or more Interrupt Routing Service (IRS) > - zero or more Interrupt Translation Service (ITS) > - zero or more Interrupt Wire Bridge (IWB) > > Describe a GICv5 implementation by specifying a top level node > corresponding to the GICv5 system component. > > IRS nodes are added as GICv5 system component children. > > An ITS is associated with an IRS so ITS nodes are described > as IRS children - use the hierarchy explicitly in the device > tree to define the association. > > IWB nodes are described as a separate schema. > > An IWB is connected to a single ITS, the connection is made explicit > through the msi-parent property and therefore is not required to be > explicit through a parent-child relationship in the device tree. > > Signed-off-by: Lorenzo Pieralisi <lpieralisi@xxxxxxxxxx> > Cc: Conor Dooley <conor+dt@xxxxxxxxxx> > Cc: Rob Herring <robh@xxxxxxxxxx> > Cc: Krzysztof Kozlowski <krzk+dt@xxxxxxxxxx> > Cc: Marc Zyngier <maz@xxxxxxxxxx> > --- > .../interrupt-controller/arm,gic-v5-iwb.yaml | 78 ++++++ > .../bindings/interrupt-controller/arm,gic-v5.yaml | 267 +++++++++++++++++++++ > MAINTAINERS | 7 + > 3 files changed, 352 insertions(+) > Reviewed-by: Rob Herring (Arm) <robh@xxxxxxxxxx>
