From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
Subject: [PATCH 0/1] Enable HDMI Receiver on NanoPC-T6
Date: Fri, 5 Sep 2025 13:02:29 +0200 [thread overview]
Message-ID: <cover.1757068166.git.marcin@juszkiewicz.com.pl> (raw)
For quite a while I had this patch in my local tree but never made it
work. Kernel generates the following messages all the time:
fdee0000.hdmi_receiver: hdmirx_wait_signal_lock: signal not lock, tmds_clk_ratio:0
fdee0000.hdmi_receiver: hdmirx_wait_signal_lock: mu_st:0x2, scdc_st:0x0, dma_st10:0x10
"v4l2-ctrl --all" reports that HDMI In is detected, /dev/video[0-4]
exist.
I tried two signal sources:
- AMD Radeon WX2100 (via passive DisplayPort -> HDMI adapter)
- AMD Radeon RX6700XT (HDMI port)
Same situation with both - kernel messages as above on RK3588 system, no
connected monitor on host side.
Usually I used MPlayer or MPV to check v4l2 devices but here it fails
too:
$ mpv av://v4l2:/dev/video3
[ffmpeg/demuxer] video4linux2,v4l2: Not a video capture device.
[lavf] avformat_open_input() failed
Failed to recognize file format.
Exiting... (Errors when loading file)
Checked SBC schematics again and HDMIIRX_DET_L line is GPIO1_D5 like it
my patch.
What I go wrong?
Marcin Juszkiewicz (1):
arm64: dts: rockchip: enable HDMI Receiver on NanoPC T6
.../boot/dts/rockchip/rk3588-nanopc-t6.dtsi | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
--
2.51.0
WARNING: multiple messages have this Message-ID (diff)
From: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org
Subject: [PATCH 0/1] Enable HDMI Receiver on NanoPC-T6
Date: Fri, 5 Sep 2025 13:02:29 +0200 [thread overview]
Message-ID: <cover.1757068166.git.marcin@juszkiewicz.com.pl> (raw)
For quite a while I had this patch in my local tree but never made it
work. Kernel generates the following messages all the time:
fdee0000.hdmi_receiver: hdmirx_wait_signal_lock: signal not lock, tmds_clk_ratio:0
fdee0000.hdmi_receiver: hdmirx_wait_signal_lock: mu_st:0x2, scdc_st:0x0, dma_st10:0x10
"v4l2-ctrl --all" reports that HDMI In is detected, /dev/video[0-4]
exist.
I tried two signal sources:
- AMD Radeon WX2100 (via passive DisplayPort -> HDMI adapter)
- AMD Radeon RX6700XT (HDMI port)
Same situation with both - kernel messages as above on RK3588 system, no
connected monitor on host side.
Usually I used MPlayer or MPV to check v4l2 devices but here it fails
too:
$ mpv av://v4l2:/dev/video3
[ffmpeg/demuxer] video4linux2,v4l2: Not a video capture device.
[lavf] avformat_open_input() failed
Failed to recognize file format.
Exiting... (Errors when loading file)
Checked SBC schematics again and HDMIIRX_DET_L line is GPIO1_D5 like it
my patch.
What I go wrong?
Marcin Juszkiewicz (1):
arm64: dts: rockchip: enable HDMI Receiver on NanoPC T6
.../boot/dts/rockchip/rk3588-nanopc-t6.dtsi | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
--
2.51.0
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next reply other threads:[~2025-09-05 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 11:02 Marcin Juszkiewicz [this message]
2025-09-05 11:02 ` [PATCH 0/1] Enable HDMI Receiver on NanoPC-T6 Marcin Juszkiewicz
2025-09-05 11:02 ` [PATCH 1/1] arm64: dts: rockchip: enable HDMI Receiver on NanoPC T6 Marcin Juszkiewicz
2025-09-05 11:02 ` Marcin Juszkiewicz
2025-09-07 17:30 ` [PATCH 0/1] Enable HDMI Receiver on NanoPC-T6 Heiko Stuebner
2025-09-07 17:30 ` Heiko Stuebner
2025-09-07 18:51 ` Dmitry Osipenko
2025-09-07 18:51 ` Dmitry Osipenko
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=cover.1757068166.git.marcin@juszkiewicz.com.pl \
--to=marcin@juszkiewicz.com.pl \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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.