Problem
I have a LCD panel using the driver IC panel-jadard-jd9365da-h3, but not in the current mainline compatibility string. I want to use the panel with Raspberry Pi 5.
What I have done
I have added TCON timing and init sequence in panel-jadard-jd9365da-h3.c, compiled the driver.
https://github.com/csvke/panel-jadard-j ... f25f23R826
I have written up a .dtb file to the best of my ability
https://github.com/csvke/panel-jadard-j ... 50113A.dts
compile it to .dtbo and copied it toHere is https://paste.debian.net/hidden/f0703665/
What I have observed
Here ispi@rpi5-raspbian:~ $ dmesg | grep dsiThe driver seem to load up as shows DSI-2 connected.But I cannot see any change despite CAM/DISP 1 is disconnected from the panel (DSI-2 connected is still shown under DISPLAY INFORMATION)
before:
https://paste.debian.net/hidden/959e63ef/
after:
https://paste.debian.net/hidden/d5439669/
Questions:
What are the common debugging tools / utilities / commands for developing a panel driver using MIPI DSI for Raspberry Pi 5?
I have shorten one of the LED backlight ground pin so it's not quite possible to see if the screen is working (replacement coming in a few days), but are there any other ways to verify the driver is working? Or more precisely, how to find out
I have a LCD panel using the driver IC panel-jadard-jd9365da-h3, but not in the current mainline compatibility string. I want to use the panel with Raspberry Pi 5.
What I have done
I have added TCON timing and init sequence in panel-jadard-jd9365da-h3.c, compiled the driver.
https://github.com/csvke/panel-jadard-j ... f25f23R826
I have written up a .dtb file to the best of my ability
https://github.com/csvke/panel-jadard-j ... 50113A.dts
compile it to .dtbo and copied it to
Code:
/boot/firmware/overlays/Code:
/boot/firmware/config.txtWhat I have observed
Here is
Code:
dmesg | grep dsiCode:
[ 2.348547] platform 1f00130000.dsi: Fixed dependency cycle(s) with /axi/pcie@120000/rp1/dsi@128000/BNS080B40HD9650113A@0[ 2.497484] platform 1f00130000.dsi: bcm2712_iommu_probe_device: MMU 1000005280.iommu[ 2.505610] platform 1f00130000.dsi: bcm2712_iommu_device_group: MMU 1000005280.iommu[ 2.513756] platform 1f00130000.dsi: Adding to iommu group 2[ 2.519693] platform 1f00130000.dsi: bcm2712_iommu_attach_dev: MMU 1000005280.iommu[ 6.665577] drm-rp1-dsi 1f00130000.dsi: bcm2712_iommu_of_xlate: MMU 1000005280.iommu[ 6.911502] panel-jadard-jd9365da-h3 1f00130000.dsi.0: supply vdd not found, using dummy regulator[ 6.911591] panel-jadard-jd9365da-h3 1f00130000.dsi.0: supply vccio not found, using dummy regulator[ 6.911602] drm-rp1-dsi 1f00130000.dsi: rp1dsi_host_attach: Attach DSI device name=BNS080B40HD9650113A channel=0 lanes=4 format=0 flags=0x203 hs_rate=0 lp_rate=0[ 6.916288] [drm] Initialized drm-rp1-dsi 1.0.0 0 for 1f00130000.dsi on minor 0[ 6.919768] drm-rp1-dsi 1f00130000.dsi: [drm] fb1: drm-rp1-dsidrmf frame buffer device[ 6.936785] drm-rp1-dsi 1f00130000.dsi: rp1dsi_bind succeeded[ 7.348831] drm-rp1-dsi 1f00130000.dsi: [drm] rp1dsi: Command time (outvact): 10[ 7.349228] drm-rp1-dsi 1f00130000.dsi: [drm] rp1dsi: Nominal Byte clock 51250000 DPI clock 68333220 (parent rate 200000000)[ 9.192776] drm-rp1-dsi 1f00130000.dsi: [drm] rp1dsi: Command time (outvact): 10[ 9.193163] drm-rp1-dsi 1f00130000.dsi: [drm] rp1dsi: Nominal Byte clock 51250000 DPI clock 68333220 (parent rate 200000000)Code:
xrandrCode:
DSI-2 connected primary 800x1280+0+0 (normal left inverted right x axis y axis) 0mm x 0mm 800x1280 58.28*+before:
https://paste.debian.net/hidden/959e63ef/
after:
https://paste.debian.net/hidden/d5439669/
Questions:
What are the common debugging tools / utilities / commands for developing a panel driver using MIPI DSI for Raspberry Pi 5?
I have shorten one of the LED backlight ground pin so it's not quite possible to see if the screen is working (replacement coming in a few days), but are there any other ways to verify the driver is working? Or more precisely, how to find out
Statistics: Posted by csvke — Wed Dec 11, 2024 7:31 pm — Replies 1 — Views 28