lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c9136f3e-464a-48c8-92d5-c014dd4e9958@collabora.com>
Date: Sun, 7 Sep 2025 21:51:39 +0300
From: Dmitry Osipenko <dmitry.osipenko@...labora.com>
To: Marcin Juszkiewicz <marcin@...zkiewicz.com.pl>,
 Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Heiko Stuebner <heiko@...ech.de>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org, linux-rockchip@...ts.infradead.org
Subject: Re: [PATCH 0/1] Enable HDMI Receiver on NanoPC-T6

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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ