From: Dmitry Osipenko <dmitry.osipenko@collabora.com>
To: Marcin Juszkiewicz <marcin@juszkiewicz.com.pl>,
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: Re: [PATCH 0/1] Enable HDMI Receiver on NanoPC-T6
Date: Sun, 7 Sep 2025 21:51:39 +0300 [thread overview]
Message-ID: <c9136f3e-464a-48c8-92d5-c014dd4e9958@collabora.com> (raw)
In-Reply-To: <cover.1757068166.git.marcin@juszkiewicz.com.pl>
On 9/5/25 14:02, Marcin Juszkiewicz wrote:
> 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?
Hi, your trouble with HDMI capture sounds very similar to [1]. Make sure
you're using opensource ATF and check whether capture works using
v4l2-ctl tool, see replies to [1]. Post a full kernel driver log if
problem will persist.
[1]
https://lore.kernel.org/linux-media/c71a3f79-71f3-4fd2-a509-c42b24636a2f@timsurber.de/
--
Best regards,
Dmitry
prev parent reply other threads:[~2025-09-07 18:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
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-07 17:30 ` [PATCH 0/1] Enable HDMI Receiver on NanoPC-T6 Heiko Stuebner
2025-09-07 18:51 ` Dmitry Osipenko [this message]
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=c9136f3e-464a-48c8-92d5-c014dd4e9958@collabora.com \
--to=dmitry.osipenko@collabora.com \
--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=marcin@juszkiewicz.com.pl \
--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