linux-kernel - Re: [PATCH v5 01/27] dt-bindings: interrupt-controller: Add Arm GICv5

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <175027275990.2508078.7812820935724706534.robh@kernel.org>
Date: Wed, 18 Jun 2025 13:52:41 -0500
From: "Rob Herring (Arm)" <robh@...nel.org>
To: Lorenzo Pieralisi <lpieralisi@...nel.org>
Cc: Thomas Gleixner <tglx@...utronix.de>,
	Jonathan Cameron <Jonathan.Cameron@...wei.com>,
	Catalin Marinas <catalin.marinas@....com>,
	Sascha Bischoff <sascha.bischoff@....com>,
	Bjorn Helgaas <bhelgaas@...gle.com>, linux-kernel@...r.kernel.org,
	devicetree@...r.kernel.org,
	Peter Maydell <peter.maydell@...aro.org>,
	Timothy Hayes <timothy.hayes@....com>,
	Jiri Slaby <jirislaby@...nel.org>, Marc Zyngier <maz@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>, linux-pci@...r.kernel.org,
	"Liam R. Howlett" <Liam.Howlett@...cle.com>,
	linux-arm-kernel@...ts.infradead.org,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Will Deacon <will@...nel.org>, Mark Rutland <mark.rutland@....com>,
	Arnd Bergmann <arnd@...db.de>
Subject: Re: [PATCH v5 01/27] dt-bindings: interrupt-controller: Add Arm GICv5


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@...nel.org>
> Cc: Conor Dooley <conor+dt@...nel.org>
> Cc: Rob Herring <robh@...nel.org>
> Cc: Krzysztof Kozlowski <krzk+dt@...nel.org>
> Cc: Marc Zyngier <maz@...nel.org>
> ---
>  .../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@...nel.org>