From: Stefan Wahren <wahrenst@gmx.net>
To: "Maíra Canal" <mcanal@igalia.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Florian Fainelli" <florian.fainelli@broadcom.com>,
"Broadcom internal kernel review list"
<bcm-kernel-feedback-list@broadcom.com>
Cc: dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, kernel-dev@igalia.com
Subject: Re: [PATCH v2] arm64: dts: broadcom: bcm2712: Add V3D device node
Date: Fri, 16 Jan 2026 20:09:23 +0100 [thread overview]
Message-ID: <f70c95cf-e048-47b6-aa6d-e65bf47fee47@gmx.net> (raw)
In-Reply-To: <20260114120610.82531-1-mcanal@igalia.com>
Am 14.01.26 um 13:04 schrieb Maíra Canal:
> Commits 0ad5bc1ce463 ("drm/v3d: fix up register addresses for V3D 7.x")
> and 6fd9487147c4 ("drm/v3d: add brcm,2712-v3d as a compatible V3D device")
> added driver support for V3D on BCM2712, but the corresponding device
> tree node is still missing.
>
> Add the V3D device tree node to the BCM2712 DTS.
>
> Signed-off-by: Maíra Canal <mcanal@igalia.com>
Reviewed-by: Stefan Wahren <wahrenst@gmx.net>
next prev parent reply other threads:[~2026-01-16 19:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 12:04 [PATCH v2] arm64: dts: broadcom: bcm2712: Add V3D device node Maíra Canal
2026-01-16 3:53 ` Peter Robinson
2026-01-16 10:15 ` Maíra Canal
2026-01-16 10:56 ` Peter Robinson
2026-01-16 12:41 ` Maíra Canal
2026-01-16 13:02 ` Krzysztof Kozlowski
2026-01-16 19:09 ` Stefan Wahren [this message]
2026-01-28 10:39 ` Maíra Canal
2026-01-28 22:27 ` Florian Fainelli
2026-01-29 0:00 ` Florian Fainelli
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=f70c95cf-e048-47b6-aa6d-e65bf47fee47@gmx.net \
--to=wahrenst@gmx.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=florian.fainelli@broadcom.com \
--cc=kernel-dev@igalia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mcanal@igalia.com \
--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