DSI MIPI panel backlight is on, but displays nothing

Hey all,

I am trying to integrate a DSI MIPI LCD panel to Jetson TX2 4GB.

I modified display-timing in panel-s-wuxga-8-0.dtsi, added dsi node in tegra186-quill-p3489-0888-a00-00-base.dts and enable it under nvdisplay@15200000. After flashing, there are errors for vpp_lcd/vmm_lcd regluators and reset gpio, so I disabled them in driver code.

With all these modifications above, the bcacklight of the panel is on, but nothing is shown…

Messages from “dmesg | grep nvdisplay”:
root@nvidia-desktop:/sys/devices# dmesg | grep nvdisplay
[ 0.430787] iommu: Adding device 15200000.nvdisplay to group 33
[ 0.991915] tegradc 15200000.nvdisplay: disp0 connected to head0->/host1x/dsi
[ 0.992045] tegradc 15200000.nvdisplay: No hpd-gpio in DT
[ 0.992075] tegradc 15200000.nvdisplay: DT parsed successfully
[ 0.992133] tegradc 15200000.nvdisplay: Display dc.ffffff800b650000 registered with id=0
[ 1.000623] tegradc 15200000.nvdisplay: vblank syncpt # 8 for dc 0
[ 1.000628] tegradc 15200000.nvdisplay: vpulse3 syncpt # 9 for dc 0
[ 1.006068] tegradc 15200000.nvdisplay: probed
[ 1.007174] tegradc 15200000.nvdisplay: fb registered
[ 1.042427] tegradc 15200000.nvdisplay: DSI: HS clock rate is 435500
[ 5.543662] tegradc 15200000.nvdisplay: blank - powerdown
[ 9.361856] tegradc 15200000.nvdisplay: blank - powerdown
[ 9.361867] tegradc 15200000.nvdisplay: unblank
[ 10.112224] tegradc 15200000.nvdisplay: sync windows ret = 246
[ 10.116009] tegradc 15200000.nvdisplay: unblank
[ 325.969991] tegradc 15200000.nvdisplay: blank - powerdown

Does anyone know how can I fix this problem? Thanks in advance.

Please attache full dmesg

@WayneWWW Thanks for your reply!

The full dmesg is here: dmesg_jetson_tx2_4gb (60.4 KB)

The display reset gpio error is still there, but I commented goto fail, so it would not cause driver failure. Also, I know the mmc1 errors are from pinmux settings, but they don’t affect anything so far, so I just leave them here. Are they related to the DSI LCD issue?

Thanks!

There is no error log from the display driver.

Maybe you can go do the driver code and dump the info and see if they match your panel.