From: Johannes Erdfelt <johannes@erdfelt.com>
To: Jimmy Hon <honyuenkwun@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v7 4/5] arm64: dts: rockchip: Enable HDMI1 on Orange Pi 5 Ultra
Date: Sat, 22 Feb 2025 13:18:20 -0800 [thread overview]
Message-ID: <20250222211820.GY16911@sventech.com> (raw)
In-Reply-To: <20250222193332.1761-5-honyuenkwun@gmail.com>
On Sat, Feb 22, 2025, Jimmy Hon <honyuenkwun@gmail.com> wrote:
> Enable the only HDMI output port on the Orange Pi 5 Ultra
>
> Signed-off-by: Jimmy Hon <honyuenkwun@gmail.com>
> ---
> .../dts/rockchip/rk3588-orangepi-5-ultra.dts | 42 +++++++++++++++++++
> 1 file changed, 42 insertions(+)
I've tested this patchset up to this patch. I unfortunately don't have a
way to test audio on the HDMI port currently.
All of the issues I had previously are fixed in this patchset.
Thanks for the work in putting this together, especially without access
to hardware.
JE
next prev parent reply other threads:[~2025-02-22 21:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-22 19:33 [PATCH v7 0/5] Orange Pi 5 Ultra Jimmy Hon
2025-02-22 19:33 ` [PATCH v7 1/5] arm64: dts: rockchip: Differences in Orange Pi 5 Max Jimmy Hon
2025-02-22 19:33 ` [PATCH v7 2/5] dt-bindings: arm: rockchip: Add Xunlong Orange Pi 5 Ultra Jimmy Hon
2025-02-22 19:33 ` [PATCH v7 3/5] arm64: dts: rockchip: Add Orange Pi 5 Ultra board Jimmy Hon
2025-02-22 23:06 ` Johannes Erdfelt
2025-02-22 19:33 ` [PATCH v7 4/5] arm64: dts: rockchip: Enable HDMI1 on Orange Pi 5 Ultra Jimmy Hon
2025-02-22 21:18 ` Johannes Erdfelt [this message]
2025-02-22 22:36 ` Jimmy Hon
2025-02-22 23:07 ` Johannes Erdfelt
2025-02-22 19:33 ` [PATCH v7 5/5] arm64: dts: rockchip: Enable HDMI1 audio output for " Jimmy Hon
2025-02-27 13:37 ` [PATCH v7 0/5] " Heiko Stuebner
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=20250222211820.GY16911@sventech.com \
--to=johannes@erdfelt.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=honyuenkwun@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).