From: Marek Vasut <marek.vasut@mailbox.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-arm-kernel@lists.infradead.org,
Nguyen Tran <nguyen.tran.pz@bp.renesas.com>,
Conor Dooley <conor+dt@kernel.org>,
David Airlie <airlied@gmail.com>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Magnus Damm <magnus.damm@gmail.com>,
Maxime Ripard <mripard@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh@kernel.org>, Simona Vetter <simona@ffwll.ch>,
Stephen Boyd <sboyd@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Tomi Valkeinen <tomi.valkeinen+renesas@ideasonboard.com>,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH 6/7] arm64: dts: renesas: r8a779md: Add Renesas R-Car R8A779MD M3Le DTs
Date: Sun, 3 May 2026 01:39:27 +0200 [thread overview]
Message-ID: <380861ce-b832-4789-93fa-c2340ce487e6@mailbox.org> (raw)
In-Reply-To: <20260429221153.GD132396@killaraus.ideasonboard.com>
On 4/30/26 12:11 AM, Laurent Pinchart wrote:
Hello Laurent,
>> +/delete-node/ &vin4csi20;
>> +/delete-node/ &vin5csi20;
>> +/delete-node/ &vin6csi20;
>> +/delete-node/ &vin7csi20;
>> +/delete-node/ &xhci0;
>> +
>> +&du {
>> + compatible = "renesas,du-r8a779md";
>> + renesas,cmms = <&cmm0>, <&cmm3>;
>
> Shouldn't you then also delete the cmm1 node ?
Please see my reply to [PATCH 1/7] dt-bindings: display: renesas,du:
Document Renesas R-Car R8A779MD M3Le , the CMM0,1,3 all seems to be on
the chip and accessible. I think the CMM driver should be aware of the
IP, even if it is unused, e.g. to bring it into low power state if needed.
> And does the DU still need three clocks and three interrupts ?
The Geist board schematic indicates that DU_DOTCLKIN1 is present on the
SoC package and is supplied by Xtal X22 on the board, so I think the
answer is "yes" for the first clock part of your question.
As for the interrupt part, it seems DU1 is present, but not connected.
That means the DU1 interrupt does exist, but is not going to be used. Do
you prefer to describe it or leave it out ?
next prev parent reply other threads:[~2026-05-02 23:39 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-19 19:35 [PATCH 0/7] arm64: dts: renesas: r8a779md: Add support for R-Car M3Le R8A779MD SoC and Geist board Marek Vasut
2026-04-19 19:35 ` [PATCH 1/7] dt-bindings: display: renesas,du: Document Renesas R-Car R8A779MD M3Le Marek Vasut
2026-04-20 16:17 ` Conor Dooley
2026-04-29 9:57 ` Geert Uytterhoeven
2026-05-02 21:17 ` Marek Vasut
2026-04-19 19:35 ` [PATCH 2/7] drm/rcar-du: Add support for " Marek Vasut
2026-04-29 10:10 ` Geert Uytterhoeven
2026-05-02 21:25 ` Marek Vasut
2026-04-19 19:35 ` [PATCH 3/7] dt-bindings: clock: cs2000-cp: document CS2500 Marek Vasut
2026-04-20 16:13 ` Conor Dooley
2026-04-20 18:38 ` Stephen Boyd
2026-04-29 11:32 ` Geert Uytterhoeven
2026-05-02 19:23 ` Marek Vasut
2026-04-19 19:35 ` [PATCH 4/7] dt-bindings: soc: renesas: Document Renesas R-Car R8A779MD Geist Marek Vasut
2026-04-20 16:14 ` Conor Dooley
2026-04-29 11:44 ` Geert Uytterhoeven
2026-04-19 19:35 ` [PATCH 5/7] soc: renesas: Identify Renesas R-Car R8A779MD M3Le SoC Marek Vasut
2026-04-29 11:46 ` Geert Uytterhoeven
2026-04-19 19:35 ` [PATCH 6/7] arm64: dts: renesas: r8a779md: Add Renesas R-Car R8A779MD M3Le DTs Marek Vasut
2026-04-29 12:16 ` Geert Uytterhoeven
2026-05-03 0:11 ` Marek Vasut
2026-04-29 22:11 ` Laurent Pinchart
2026-05-02 23:39 ` Marek Vasut [this message]
2026-04-19 19:35 ` [PATCH 7/7] arm64: dts: renesas: r8a779md: Add support for R-Car M3Le R8A779MD Geist Marek Vasut
2026-04-29 13:59 ` Geert Uytterhoeven
2026-05-03 1:25 ` Marek Vasut
2026-05-04 9:24 ` Geert Uytterhoeven
2026-05-04 22:53 ` Marek Vasut
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=380861ce-b832-4789-93fa-c2340ce487e6@mailbox.org \
--to=marek.vasut@mailbox.org \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert+renesas@glider.be \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=nguyen.tran.pz@bp.renesas.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=simona@ffwll.ch \
--cc=tomi.valkeinen+renesas@ideasonboard.com \
--cc=tzimmermann@suse.de \
/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