Can't enable HDMI RX on Orange Pi 5+

[pcislocked]

Not sure what I'm missing, i am in no way an arm sbc expert. the only place before this board where i had to deal with the abomination called uboot was openwrt. As far as I understand, HDMI RX is disabled because it's drivers are dogshit and it spams interrupts which causes higher load which is undesirable for most users so it's disabled on driver level by default, and simply toggleable with a device tree tweak on /etc/default/u-boot. I tried and it didn't work. And yes, like any ordinary guy who cant find it on google, I asked ai. Tried bunch of stuff. Didn't work. Here's what I've tried; and yes i used chatgpt for this too, am lazy as fuck

Absolutely! Here’s a more polished GitHub issue draft for you.
Also, I’ll include a detailed note explaining exactly what I gathered and included based on your troubleshooting steps and logs from this chat.

Hello, I am working with Orange pi 5 Plus, a RK3588-based device running Ubuntu 24.04 with kernel version 6.1.0-1025-rockchip. The goal is to use the HDMI RX input, but the corresponding video device node (e.g., /dev/video0) does not appear.

Here’s what I’ve tried:

• Edited U-Boot to enable HDMI RX support, as told on wiki
• Installed all relevant media and video-related packages (v4l-utils, etc.)., as in [Orange Pi 5+] HDMI IN - Not a video capture device #252
• Checked /proc/config.gz and confirmed kernel config has HDMI RX and videobuf2 enabled (mostly built-in or modules).
• Tried loading hdmirx and related modules with modprobe, but modules aren’t found in /lib/modules/.
• Verified device tree settings appear to have HDMI RX configured.
• Used dmesg to look for HDMI or video related messages, found some HDMI PHY and DWC HDMI logs, but no video device created.
• Confirmed the HDMI RX port has a proper video signal connected during all tests.
• However only /dev/video-dec0 and /dev/video-enc0 exist, but no /dev/video0.

--

My final goal is to use hdmi rx as some sort of network-connected capture card to be used in another obs rig. in a similar fashion to NDI but it can also be a simple rtsp output as well.

Normally I'd use belabox image for that but since I am using the board with some other server purposes, I want to do the hdmi stuff without that abomination of an image running on my board.

pls help
thx

[pcislocked]

root@opi:~# cat /proc/config.gz | grep -i hdmirx
CONFIG_VIDEO_ROCKCHIP_HDMIRX_CLASS=y
CONFIG_VIDEO_ROCKCHIP_HDMIRX=y
root@opi:~# zcat /proc/config.gz | grep -i videobuf
CONFIG_VIDEOBUF2_CORE=y
CONFIG_VIDEOBUF2_V4L2=y
CONFIG_VIDEOBUF2_MEMOPS=y
CONFIG_VIDEOBUF2_CMA_SG=y
CONFIG_VIDEOBUF2_DMA_CONTIG=y
CONFIG_VIDEOBUF2_VMALLOC=y
CONFIG_VIDEOBUF2_DMA_SG=y
CONFIG_VIDEOBUF2_DVB=m
root@opi:~# ls -l /dev/video*
-rw-rw---- 1 root video 71 Jun 14 23:36 /dev/video-dec0
-rw-rw---- 1 root video  4 Jun 14 23:36 /dev/video-enc0
root@opi:~# dmesg | grep -i hdmi
[   18.116512] platform fde80000.hdmi: Fixed dependency cycle(s) with /vop@fdd90000/ports/port@0/endpoint@2
[   18.132476] platform fdea0000.hdmi: Fixed dependency cycle(s) with /vop@fdd90000/ports/port@1/endpoint@5
[   18.773306] phy phy-fed60000.hdmiphy.9: Looking up phy-supply from device tree
[   18.773311] phy phy-fed60000.hdmiphy.9: Looking up phy-supply property in node /hdmiphy@fed60000 failed
[   18.773913] rockchip-hdptx-phy-hdmi fed60000.hdmiphy: hdptx phy init success
[   18.774107] phy phy-fed70000.hdmiphy.10: Looking up phy-supply from device tree
[   18.774112] phy phy-fed70000.hdmiphy.10: Looking up phy-supply property in node /hdmiphy@fed70000 failed
[   18.774674] rockchip-hdptx-phy-hdmi fed70000.hdmiphy: hdptx phy init success
[   19.121136] dwhdmi-rockchip fde80000.hdmi: Looking up avdd-0v9-supply from device tree
[   19.121140] dwhdmi-rockchip fde80000.hdmi: Looking up avdd-0v9-supply property in node /hdmi@fde80000 failed
[   19.121147] dwhdmi-rockchip fde80000.hdmi: Looking up avdd-1v8-supply from device tree
[   19.121151] dwhdmi-rockchip fde80000.hdmi: Looking up avdd-1v8-supply property in node /hdmi@fde80000 failed
[   19.121823] dwhdmi-rockchip fde80000.hdmi: registered ddc I2C bus driver
[   19.122471] rockchip-drm display-subsystem: bound fde80000.hdmi (ops dw_hdmi_rockchip_ops)
[   19.122536] dwhdmi-rockchip fdea0000.hdmi: Looking up avdd-0v9-supply from device tree
[   19.122540] dwhdmi-rockchip fdea0000.hdmi: Looking up avdd-0v9-supply property in node /hdmi@fdea0000 failed
[   19.122551] dwhdmi-rockchip fdea0000.hdmi: Looking up avdd-1v8-supply from device tree
[   19.122554] dwhdmi-rockchip fdea0000.hdmi: Looking up avdd-1v8-supply property in node /hdmi@fdea0000 failed
[   19.122907] dwhdmi-rockchip fdea0000.hdmi: registered ddc I2C bus driver
[   19.123163] rockchip-drm display-subsystem: bound fdea0000.hdmi (ops dw_hdmi_rockchip_ops)
[   19.124512] dw-hdmi-qp-hdcp dw-hdmi-qp-hdcp.8.auto: dw_hdcp_qp_hdcp_probe success
[   19.125079] dw-hdmi-qp-hdcp dw-hdmi-qp-hdcp.12.auto: dw_hdcp_qp_hdcp_probe success
[   19.136343] rockchip-dmc dmc: hdmirx_rate = 2112000000
[   19.139375] input: rockchip-hdmi0 rockchip-hdmi0 as /devices/platform/hdmi0-sound/sound/card2/input6
[   19.140110] input: rockchip-hdmi1 rockchip-hdmi1 as /devices/platform/hdmi1-sound/sound/card3/input7
[   19.181696]   #2: rockchip-hdmi0
[   19.181701]   #3: rockchip-hdmi1
root@opi:~# dmesg | grep -i video
[   18.709798] videodev: Linux video capture interface: v2.00
[   18.911409] usbcore: registered new interface driver uvcvideo
[   19.136313] rockchip-dmc dmc: video_4k_rate = 1560000000
[   19.136318] rockchip-dmc dmc: video_4k_10b_rate = 1560000000
[   19.136323] rockchip-dmc dmc: video_svep_rate = 1560000000
root@opi:~# cat /boot/dtbs/$(uname -r)/rockchip/*.dtb | strings | grep -i hdmi
cat: '/boot/dtbs/6.1.0-1025-rockchip/rockchip/*.dtb': No such file or directory
root@opi:~# v4l2-ctl --list-devices
Cannot open device /dev/video0, exiting.
root@opi:~# fw_printenv | grep -i hdmi
Cannot initialize environment
root@opi:~# cat /etc/default/u-boot
U_BOOT_UPDATE="true"
U_BOOT_FDT_OVERLAYS="6.1.0-1025-rockchip/device-tree/rockchip/overlay/rk3588-hdmirx.dtbo"
U_BOOT_FDT_OVERLAYS_DIR="/lib/firmware/"
root@opi:~# ls /lib/firmware/6.1.0-1025-rockchip/device-tree/rockchip/overlay/rk3588-hdmirx.dtbo
/lib/firmware/6.1.0-1025-rockchip/device-tree/rockchip/overlay/rk3588-hdmirx.dtbo
root@opi:~#

[kurkovpavel]

just sudo orangepi-config -> enable HDMI RX and restart, when you enable/disable in orangepi-config some hardware it adds or removes overlay in /boot/OrangepiEnv.txt, dtbo file will assign hdmi-rx node in your device-tree and you will see many /dev/videoX devices, choose one /dev/video0 or /dev/video10 or etc...

[pcislocked]

just sudo orangepi-config -> enable HDMI RX and restart, when you enable/disable in orangepi-config some hardware it adds or removes overlay in /boot/OrangepiEnv.txt, dtbo file will assign hdmi-rx node in your device-tree and you will see many /dev/videoX devices, choose one /dev/video0 or /dev/video10 or etc...

can't confirm, swapped orange pi 5 plus for another orange pi sbc.