Murat Demirtas

Hello, friends... The current MIPI DSI driver provided by Rockchip Inc. in older U-Boot versions (v2023 and earlier) is not compatible with U-Boot’s uclass subsystems.(a waste of time if you want to develop). I have done extensive research and made modifications to several files to make it work with the latest U-Boot versions. I have tested it with U-Boot 2023.10, 2024.10 and v2025.rc3 on orange pi 4 lts, and it works perfectly. I'm attaching the necessary files for those who need them. This u-boot driver is nearly identical to Rockchip's Linux kernel driver, uses same driver file but there some limitations because of u-boot system, but it correctly displays the splash image when vidconsole0 probed by u-boot.. Additionally, i want to say that, in linux kernel side, the same dw-rockchip-dsi driver in latest armbian distribitions works with from kernels 5.18 to latest kernel v6.6 and v.6.12. I tested it. Tested with custom 400x1200 60hz 4 lane standart mipi dsi panel from chinese panel manufacturer. I attached all modified files as attachment. Good lucks. dm tree command output from u-boot is reset 1 [ + ] rockchip_reset | `-- reset syscon 27 [ + ] rk3399_syscon |-- syscon@ff770000 nop 3 [ + ] rockchip_iodomain | `-- io-domains video 0 [ + ] rk3399_vop |-- vop@ff8f0000 vidconsole 0 [ + ] vidconsole0 | `-- vop@ff8f0000.vidconsole0 video 1 [ + ] rk3399_vop |-- vop@ff900000 vidconsole 1 [ + ] vidconsole0 | `-- vop@ff900000.vidconsole0 video_brid 0 [ + ] dw-mipi-dsi-rockchip |-- dsi@ff960000 dsi_host 0 [ + ] dw_mipi_dsi | |-- dsihost panel 0 [ + ] rm68200_panel | `-- panel@0 pinctrl 0 [ + ] rockchip_rk3399_pinc |-- pinctrl U-Boot 2024.10-armbian-2024.10-Sf919-Pbfb2-H3d34-Vade7-Bb703-R448a-dirty (Mar 03 2025 - 06:16:04 +0300) SoC: Rockchip rk3399 Reset cause: RST Model: Orange Pi 4 LTS Board DRAM: 4 GiB (effective 3.9 GiB) PMIC: RK808 Core: 285 devices, 32 uclasses, devicetree: separate MMC: mmc@fe320000: 1, mmc@fe330000: 0 Loading Environment from MMC... Reading from MMC(0)... *** Warning - bad CRC, using default environment rm68200_panel_of_to_plat() rm68200_panel panel@0: reset pin set done rm68200_panel_probe() rm68200_panel panel@0: Initializing MIPI DSI Panel Driver rm68200_panel_probe() rm68200_panel panel@0: Reset sequence done rm68200_panel_probe() rm68200_panel panel@0: dsi set 4 lane, video-burst, RGB 24-bit mode rm68200_panel_enable_backlight() rm68200_panel panel@0: Panel set backlight func(), initializing panel rm68200_panel_enable_backlight() rm68200_panel panel@0: attaching mipi dsi panel rm68200_panel_enable_backlight() rm68200_panel panel@0: perform panel initialization sequence rm68200_panel_enable_backlight() rm68200_panel panel@0: panel initialization sequence done, panel probed! rm68200_panel_enable_backlight() rm68200_panel panel@0: Panel set backlight func(), initializing panel rm68200_panel_enable_backlight() rm68200_panel panel@0: attaching mipi dsi panel rm68200_panel_enable_backlight() rm68200_panel panel@0: perform panel initialization sequence rm68200_panel_enable_backlight() rm68200_panel panel@0: panel initialization sequence done, panel probed! In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: Orange Pi 4 LTS Board Net: Could not get PHY for ethernet@fe300000: addr 1 eth_initialize() No ethernet found. Hit any key to stop autoboot: 0 => dcdcddcdcdcdc<INTERRUPT> => setenv splashimage 0x82000000 => setenv splashfile /boot/splash.bmp => load mmc 0:1 ${splashimage} ${splashfile} 1920138 bytes read in 61 ms (30 MiB/s) => bmp display ${splashimage} => <INTERRUPT> => uclass_get_device_by_ofnode() Looking for clock-controller@ff760000 uclass_find_device_by_ofnode() Looking for clock-controller@ff760000 uclass_find_device_by_ofnode() - checking reset uclass_find_device_by_ofnode() - checking reset uclass_find_device_by_ofnode() - result for clock-controller@ff760000: reset (ret=0) uclass_get_device_by_ofnode() - result for clock-controller@ff760000: reset (ret=0) rm68200_panel_enable_backlight() rm68200_panel panel@0: Panel set backlight func(), initializing panel rm68200_panel_enable_backlight() rm68200_panel panel@0: attaching mipi dsi panel rm68200_panel_enable_backlight() rm68200_panel panel@0: perform panel initialization sequence rm68200_panel_enable_backlight() rm68200_panel panel@0: panel initialization sequence done, panel probed! dsi_phy_post_set_mode() dw-mipi-dsi-rockchip dsi@ff960000: Set mode 00000000f4f3b4a0 enable 1 device_bind_common() Bound device vop@ff900000.vidconsole0 to vop@ff900000 notify_dynamic() Sending event 5/(unknown) to spy 'efi_disk add' notify_dynamic() Sending event 5/(unknown) to spy 'efi_disk add' In: serial@ff1a0000 Out: serial@ff1a0000 Err: serial@ff1a0000 Model: Orange Pi 4 LTS Board raydium-rm68200.c dw_mipi_dsi.c rk_vop.c dw_mipi_dsi_rockchip.c clk_rk3399.c .config rk3399-orangepi.dts

hello, i'm trying to run latest uboot v2025.03 rc2 with kernel 6.6 on orange pi 4 lts. i have same error :). In the unofficial image from armbian-build with latest Armbian Edge Kernel version(6.12), I see that this module gives many error messages to the dmesg output. setenv bootargs "root=/dev/mmcblk0p1 rw rootwait console=ttyS2,1500000 modprobe.blacklist=sprdwl_ng" saveenv is only solution for now.

Thank you again, the lcd panel works.. Have a good days!!!.. armbian v25.02 rolling for Orange Pi 4 LTS running Armbian Linux 6.12.13-current-rockchip64 Linux orangepi4-lts 6.6.62-current-rockchip64 #1 SMP PREEMPT Tue Feb 11 11:37:33 +03 2025 aarch64 GNU/Linux

Hello @Werner, you are right, i changed name of the patch file to zzz-kernel-patch-nv3051f1-lcd-panel.patch and its worked. thank you very much.

Hello, I'm trying to make a change for kernel panel driver for custom mipi dsi panel and orangepi-4-lts dts file. I could successfully flashed my armbian and bringed on our orangepi-4-lts board. I have configured to. debian minimal server rootfs and current linux kernel git tree in menuconfig with that command. sudo apt-get -y install git git clone --depth=1 --branch=v24.11 https://github.com/armbian/build cd build/ ./compile.sh ./compile.sh KERNEL_GIT=shallow After bring up, i tried to change existing linux kernel driver to our customized one using userpatches and that worked well. But i forgot the change dts file of orangepi4-lts and i have changed necessary lines in the existing orangepi-4-lts.dts file and linux kernel driver and used same command with kernel patch, but no luck, i got errors. Command for kernel patching, ./compile.sh kernel-patch BOARD=orangepi-4-lts BRANCH=current After changed, the patch file generated successfully. I moved it to userpatches kernel directory with that command sudo mv /home/oem/Desktop/build/output/patch/kernel-rockchip64-current.patch userpatches/kernel/archive/rockchip64-6.6/kernel-rockchip64-current.patch Command for building only kernel, ./compile.sh kernel BOARD=orangepi4-lts BRANCH=current the command works well if i patch only panel-newvision-nv3051d.c in /Desktop/build/cache/sources/linux-kernel-worktree/6.6__rockchip64__arm64/drivers/gpu/drm/panel/panel-newvision-nv3051d.c. If the patch file include changes both panel-newvision-nv3051d.c and rk3399-orangepi-4-lts.dts files then armbian build shows me error message. [🔨] Patch ->kernel-rockchip64-current(:1) (+97/-2)[2M] {rk3399-orangepi-4-lts.dts, panel-newvision-nv3051d.c}<- needs fixing: can't find file to patch. [🔨] Problem with ->kernel-rockchip64-current(:1) (+97/-2)[2M] {rk3399-orangepi-4-lts.dts, panel-newvision-nv3051d.c}<-: Failed to apply patch /home/oem/Desktop/build/userpatches/kernel/archive/rockchip64-6.6/kernel-rockchip64-current.patch those two file is exists in the directory and i will share full log as attachment in here(tried to upload log via armbian-build but it doesnt work). I tried everything and couldnt found a root issue. My host environment is fresh installed ubuntu 22-04 jammy on amd64. Thank you for your help and suggestions. kernel-rockchip64-current.patch build.log