Skip to main content
Visitor II
Nov 5, 2026 6:15 AM UTC
Question

STM32MP257F custom board: LTDC/DRM driver (drv.c, ltdc.c) does not probe, LTDC clock stays disabled, DFR0678 MIPI DSI display shows no image

Hello ST team and community,

We are bringing up a custom board based on the STM32MP257F, built with Yocto (OpenSTLinux, linux-stm32mp kernel [version, e.g. 6.6.x]). The board DTS is derived from stm32mp257f-ev1.dts.

Problem
We connected a DFRobot DFR0678 (800x480) MIPI DSI display and get no image. On investigation, the DRM driver for the display controller does not appear to load or probe at all (drivers/gpu/drm/stm/drv.c and ltdc.c).

What we have checked

1.&ltdc and &dsi are set to status = "okay" in the board DTS, and the LTDC port/endpoint links to dsi_in in both directions.

2.Kernel config: CONFIG_DRM_STM=m, CONFIG_DRM_STM_DSI=m, CONFIG_DRM_DW_MIPI_DSI=m, CONFIG_DRM_PANEL=y.

3.In /sys/kernel/debug/clk/clk_summary, the clocks related to LTDC are disabled.

Our expectation
As far as we understand, drv.c should bind to the st,stm32mp25-ltdc node and run probe() even when no display is physically connected, because the match depends only on the device tree and not on the panel hardware. In our case it does not. We understand that a disabled LTDC clock is expected while the driver has not probed, so we see it as a symptom rather than the root cause.

Questions

1.What are the possible reasons for stm32-display not binding or probing on the MP257F when the LTDC node is enabled?

2.Could RIF/resource-isolation settings for LTDC in TF-A or OP-TEE prevent the A35 from using it, and how can we verify this?

3.What is the recommended DT node structure and kernel driver for a DSI panel like the DFR0678 on the MP25 DSI host?

Any guidance on the debug steps, or on what we may be missing in the DTS or the kernel configuration, would be very helpful. 

Thank you,

Mallesh