From: Linus Walleij <linusw@kernel.org>
To: Daniel Scally <dan.scally@ideasonboard.com>,
Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Linus Walleij <linusw@kernel.org>
Subject: [PATCH v3 5/5] arm64: dts: renesas: r9a09g057h44-rzv2h-evk: Add ISP and IVC nodes
Date: Mon, 28 Sep 2026 14:21:51 +0200 [thread overview]
Message-ID: <20260928-mali-c55-renesas-dts-v3-5-2cf7eb746ebb@kernel.org> (raw)
In-Reply-To: <20260928-mali-c55-renesas-dts-v3-0-2cf7eb746ebb@kernel.org>
From: Daniel Scally <dan.scally@ideasonboard.com>
Add nodes to devicetree enabling the ISP and IVC that are found on
the RZ/V2H(P) SoC.
[Rebase onto v7.3-rc1 and sort the board overrides by label.
- Linus Walleij]
Assisted-by: LLM
Signed-off-by: Daniel Scally <dan.scally@ideasonboard.com>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Linus Walleij <linusw@kernel.org>
---
arch/arm64/boot/dts/renesas/r9a09g057h44-rzv2h-evk.dts | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/arch/arm64/boot/dts/renesas/r9a09g057h44-rzv2h-evk.dts b/arch/arm64/boot/dts/renesas/r9a09g057h44-rzv2h-evk.dts
index 637fc92dcc26..74b75be599ae 100644
--- a/arch/arm64/boot/dts/renesas/r9a09g057h44-rzv2h-evk.dts
+++ b/arch/arm64/boot/dts/renesas/r9a09g057h44-rzv2h-evk.dts
@@ -305,6 +305,14 @@ versa3: clock-generator@69 {
};
};
+&isp {
+ status = "okay";
+};
+
+&ivc {
+ status = "okay";
+};
+
&mdio0 {
phy0: ethernet-phy@0 {
compatible = "ethernet-phy-id0022.1640";
--
2.55.0
next prev parent reply other threads:[~2026-09-28 12:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 12:21 [PATCH v3 0/5] arm64: dts: renesas: Enable ISP and IVC on RZ/V2H EVK Linus Walleij
2026-09-28 12:21 ` [PATCH v3 1/5] dt-bindings: media: renesas,r9a09g057-ivc: Describe additional interrupts Linus Walleij
2026-10-06 11:07 ` Lad, Prabhakar
2026-10-07 10:43 ` Dan Scally
2026-09-28 12:21 ` [PATCH v3 2/5] dt-bindings: media: arm,mali-c55: Describe DMA line-tick interrupts Linus Walleij
2026-10-05 17:39 ` Rob Herring (Arm)
2026-10-06 11:11 ` Lad, Prabhakar
2026-10-07 10:49 ` Dan Scally
2026-10-08 13:26 ` Linus Walleij
2026-09-28 12:21 ` [PATCH v3 3/5] dt-bindings: media: arm,mali-c55: Add power domain Linus Walleij
2026-10-05 17:39 ` Rob Herring (Arm)
2026-10-06 11:13 ` Lad, Prabhakar
2026-10-07 10:50 ` Dan Scally
2026-09-28 12:21 ` [PATCH v3 4/5] arm64: dts: renesas: r9a09g057: Add IVC and ISP nodes Linus Walleij
2026-09-28 12:21 ` Linus Walleij [this message]
2026-10-06 18:33 ` [PATCH v3 5/5] arm64: dts: renesas: r9a09g057h44-rzv2h-evk: Add ISP and IVC nodes Lad, Prabhakar
2026-10-08 13:18 ` Linus Walleij
2026-10-05 22:14 ` [PATCH v3 0/5] arm64: dts: renesas: Enable ISP and IVC on RZ/V2H EVK Linus Walleij
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260928-mali-c55-renesas-dts-v3-5-2cf7eb746ebb@kernel.org \
--to=linusw@kernel.org \
--cc=conor+dt@kernel.org \
--cc=dan.scally@ideasonboard.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jacopo.mondi@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox