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 UNTESTED v5 0/4] Orange Pi 5 Ultra
Date: Fri, 21 Feb 2025 20:36:32 -0800 [thread overview]
Message-ID: <20250222043632.GU16911@sventech.com> (raw)
In-Reply-To: <CALWfF7KW8_vAx49nNygKpLHNJQVpjvVdVpzYiTAWgQvSopHikw@mail.gmail.com>
On Fri, Feb 21, 2025, Jimmy Hon <honyuenkwun@gmail.com> wrote:
> On Fri, Feb 21, 2025 at 5:13 PM Johannes Erdfelt <johannes@erdfelt.com> wrote:
> > I'll also see if I can give HDMI a test.
>
> Please report your results when you do. This is one of the differences
> from the Orange Pi 5 Max. The HDMI1 pinctrls does not use the default
> pinctrls like other RK3588 boards (including the Orange Pi 5 Plus).
No luck yet. I do see this message in the kernel logs 8 times at boot:
[ 41.552751] rockchip-drm display-subsystem: [drm] *ERROR* failed to
get pll_hdmiphy0
I'll confirm with the vendor image that my HDMI setup is correct.
JE
WARNING: multiple messages have this Message-ID (diff)
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 UNTESTED v5 0/4] Orange Pi 5 Ultra
Date: Fri, 21 Feb 2025 20:36:32 -0800 [thread overview]
Message-ID: <20250222043632.GU16911@sventech.com> (raw)
In-Reply-To: <CALWfF7KW8_vAx49nNygKpLHNJQVpjvVdVpzYiTAWgQvSopHikw@mail.gmail.com>
On Fri, Feb 21, 2025, Jimmy Hon <honyuenkwun@gmail.com> wrote:
> On Fri, Feb 21, 2025 at 5:13 PM Johannes Erdfelt <johannes@erdfelt.com> wrote:
> > I'll also see if I can give HDMI a test.
>
> Please report your results when you do. This is one of the differences
> from the Orange Pi 5 Max. The HDMI1 pinctrls does not use the default
> pinctrls like other RK3588 boards (including the Orange Pi 5 Plus).
No luck yet. I do see this message in the kernel logs 8 times at boot:
[ 41.552751] rockchip-drm display-subsystem: [drm] *ERROR* failed to
get pll_hdmiphy0
I'll confirm with the vendor image that my HDMI setup is correct.
JE
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-02-22 4:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-20 4:10 [PATCH UNTESTED v5 0/4] Orange Pi 5 Ultra Jimmy Hon
2025-02-20 4:10 ` Jimmy Hon
2025-02-20 4:10 ` [PATCH UNTESTED v5 1/4] dt-bindings: arm: rockchip: Add Xunlong " Jimmy Hon
2025-02-20 4:10 ` Jimmy Hon
2025-02-21 22:28 ` Rob Herring (Arm)
2025-02-21 22:28 ` Rob Herring (Arm)
2025-02-20 4:10 ` [PATCH UNTESTED v5 2/4] arm64: dts: rockchip: Add Orange Pi 5 Ultra board Jimmy Hon
2025-02-20 4:10 ` Jimmy Hon
2025-02-20 4:10 ` [PATCH UNTESTED v5 3/4] arm64: dts: rockchip: Enable HDMI1 on Orange Pi 5 Ultra Jimmy Hon
2025-02-20 4:10 ` Jimmy Hon
2025-02-20 4:10 ` [PATCH UNTESTED v5 4/4] arm64: dts: rockchip: Enable HDMI1 audio output for " Jimmy Hon
2025-02-20 4:10 ` Jimmy Hon
2025-02-21 23:13 ` [PATCH UNTESTED v5 0/4] " Johannes Erdfelt
2025-02-21 23:13 ` Johannes Erdfelt
2025-02-22 1:23 ` Jimmy Hon
2025-02-22 1:23 ` Jimmy Hon
2025-02-22 4:31 ` Johannes Erdfelt
2025-02-22 4:31 ` Johannes Erdfelt
2025-02-22 5:30 ` Jimmy Hon
2025-02-22 5:30 ` Jimmy Hon
2025-02-22 4:36 ` Johannes Erdfelt [this message]
2025-02-22 4:36 ` Johannes Erdfelt
2025-02-22 5:12 ` Jimmy Hon
2025-02-22 5:12 ` Jimmy Hon
2025-02-22 6:05 ` Johannes Erdfelt
2025-02-22 6:05 ` Johannes Erdfelt
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=20250222043632.GU16911@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.