Skip to contentSkip to conversation

dt-bindings: interrupt-controller: Convert nvidia,tegra20-ictlr to DT schema

PATCH Applied Rob Herring (Arm) 2 participants 2 messages May 5, 2025 – May 8, 2025

Subsystems (3)
lore
Share & tools
lore

Rob Herring (Arm)

author maintainer
#0 lore raw

PATCH 1/1 dt-bindings: interrupt-controller: Convert nvidia,tegra20-ictlr to DT schema

Convert the NVIDIA Legacy interrupt controller binding to schema format. It's a straight-forward conversion of the typical interrupt controller.

All the possible compatibles were not documented, so add the ones in use.

---
 .../nvidia,tegra20-ictlr.txt                  | 41 ----------
 .../nvidia,tegra20-ictlr.yaml                 | 82 +++++++++++++++++++
 2 files changed, 82 insertions(+), 41 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.txt
 create mode 100644 Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.yaml
Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.txt deleted +0 -41
deleted file mode 100644
index 2ff356640100..000000000000
@@ -1,41 +0,0 @@
-NVIDIA Legacy Interrupt Controller
-
-All Tegra SoCs contain a legacy interrupt controller that routes
-interrupts to the GIC, and also serves as a wakeup source. It is also
-referred to as "ictlr", hence the name of the binding.
-
-The HW block exposes a number of interrupt controllers, each
-implementing a set of 32 interrupts.
-
-Required properties:
-
-- compatible : should be: "nvidia,tegra<chip>-ictlr". The LIC on
-  subsequent SoCs remained backwards-compatible with Tegra30, so on
-  Tegra generations later than Tegra30 the compatible value should
-  include "nvidia,tegra30-ictlr".	
-- reg : Specifies base physical address and size of the registers.
-  Each controller must be described separately (Tegra20 has 4 of them,
-  whereas Tegra30 and later have 5).
-- interrupt-controller : Identifies the node as an interrupt controller.
-- #interrupt-cells : Specifies the number of cells needed to encode an
-  interrupt source. The value must be 3.
-
-Notes:
-
-- Because this HW ultimately routes interrupts to the GIC, the
-  interrupt specifier must be that of the GIC.
-- Only SPIs can use the ictlr as an interrupt parent. SGIs and PPIs
-  are explicitly forbidden.
-
-Example:
-
-	ictlr: interrupt-controller@60004000 {
-		compatible = "nvidia,tegra20-ictlr", "nvidia,tegra-ictlr";
-		reg = <0x60004000 64>,
-		      <0x60004100 64>,
-		      <0x60004200 64>,
-		      <0x60004300 64>;
-		interrupt-controller;
-		#interrupt-cells = <3>;
-		interrupt-parent = <&intc>;
-	};
Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.yaml new file +82 -0

82 lines not on this page · raw message

Signature · 1 line
2.47.2
#1 lore raw
Quoted 7 lines · Rob Herring (Arm)

Convert the NVIDIA Legacy interrupt controller binding to schema format. It's a straight-forward conversion of the typical interrupt controller.

All the possible compatibles were not documented, so add the ones in use.

Quoted 7 lines
---
 .../nvidia,tegra20-ictlr.txt                  | 41 ----------
 .../nvidia,tegra20-ictlr.yaml                 | 82 +++++++++++++++++++
 2 files changed, 82 insertions(+), 41 deletions(-)
 delete mode 100644 Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.txt
 create mode 100644 Documentation/devicetree/bindings/interrupt-controller/nvidia,tegra20-ictlr.yaml

Applied, thanks.

Thierry