From: Drew Fustini <fustini@kernel.org>
To: Robert Mazur <robert.mazur@imgtec.com>
Cc: Guo Ren <guoren@kernel.org>, Fu Wei <wefu@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Paul Walmsley <pjw@kernel.org>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Alexandre Ghiti <alex@ghiti.fr>,
linux-riscv@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: dts: thead: beaglev-ahead: enable HDMI output
Date: Wed, 25 Mar 2026 09:53:44 -0700 [thread overview]
Message-ID: <acQTGPHvoMDvLtDf@x1> (raw)
In-Reply-To: <20260325-hdmi-beaglev-ahead-v1-1-e71b41b98dca@imgtec.com>
On Wed, Mar 25, 2026 at 09:18:59AM +0100, Robert Mazur wrote:
> The BeagleV Ahead board includes a micro HDMI connector (Type-D)
> wired to the TH1520 SoC's HDMI transmitter.
>
> Enable the display pipeline by adding the HDMI connector node,
> connecting it to the HDMI controller, and activating the DPU
> and HDMI nodes.
>
> Signed-off-by: Robert Mazur <robert.mazur@imgtec.com>
> ---
> This patch enables HDMI output on the BeagleV-Ahead board by wiring up
> the DPU and HDMI nodes added in the following series:
>
> Depends-on: https://lore.kernel.org/r/20260129023922.1527729-7-zhengxingda@iscas.ac.cn/
>
> The patch has been tested on BeagleV-Ahead hardware with the above
> series applied. HDMI output is functional.
> ---
> arch/riscv/boot/dts/thead/th1520-beaglev-ahead.dts | 25 ++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
Reviewed-by: Drew Fustini <fustini@kernel.org>
Thanks for getting this working for the BeagleV Ahead and sending the
patch.
Drew
next prev parent reply other threads:[~2026-03-25 16:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-25 8:18 [PATCH] riscv: dts: thead: beaglev-ahead: enable HDMI output Robert Mazur
2026-03-25 16:53 ` Drew Fustini [this message]
2026-03-25 21:57 ` Drew Fustini
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=acQTGPHvoMDvLtDf@x1 \
--to=fustini@kernel.org \
--cc=alex@ghiti.fr \
--cc=aou@eecs.berkeley.edu \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=guoren@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=pjw@kernel.org \
--cc=robert.mazur@imgtec.com \
--cc=robh@kernel.org \
--cc=wefu@redhat.com \
/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