Display: stm32_ltdc: in function stm32_ltdc_display_blanking_off is not working, There is no panel controller to forward blanking_off

[summer4821smartbox]

Describe the bug

I try to run zephyr/samples/drivers/display sample application function on STM32H747I-DISCO with NT35510 panel shell use st_b_lcd40_dsi1_mb1166_a09 and the display_blanking_off() function is not working because no panel controller forward to.
And I found related issue #68527, and followed the steps and get the same result, it’s still not working

1.add display-controller in app.overly and make sure display-controller = < &nt35510 > appear in ltdc DTS in zephyr.dts

&ltdc {
	display-controller = <&nt35510>;
};

2.Change initialization priority implement as #68527 and check initialization priority

  __init___device_dts_ord_137: mipi_dsi_stm32_init(__device_dts_ord_137)
  __init___device_dts_ord_140: nt35510_init(__device_dts_ord_140)
  __init___device_dts_ord_141: stm32_ltdc_init(__device_dts_ord_141)

3. I get Display device nt35510@0 not ready

[00:00:01.222,000] <err> dsi_stm32: Transfer failed! (3)
[00:00:01.222,000] <err> nt35510: Failed reading ID (-5)
[00:00:01.222,000] <err> nt35510: Panel ID check failed! (-5)
*** Booting Zephyr OS build v3.7.0-2665-gcc544803811b ***
[00:00:01.222,000] <inf> sample: Display sample for display-controller@50001000
[00:00:01.234,000] <inf> display_stm32_ltdc: config name display-controller@50001000
[00:00:01.234,000] <err> display_stm32_ltdc: Display device nt35510@0 not ready

To Reproduce
Run zephyr/samples/drivers/display sample application function on STM32H747I-DISCO with NT35510 panel shell use st_b_lcd40_dsi1_mb1166_a09

build command
west build -t initlevels --pristine -b stm32h747i_disco/stm32h747xx/m7 zephyr/samples/drivers/display -DSHIELD=st_b_lcd40_dsi1_mb1166_a0

Expected behavior
display_blanking_off() function work without error

Impact
When developing project,it's not able to use this API to control the backlight. System power saving and suspend modes will not be implemented.

Logs and console output

<err> display_stm32_ltdc: There is no panel controller to forward blanking_off call to name 

Environment (please complete the following information):

Microcontroller: STM32H747I
Zephyr Version: Zephyr main branch Commit cc54480
OS: Ubuntu 23.10

[github-actions]

Hi @summer4821smartbox! We appreciate you submitting your first issue for our open-source project. 🌟

Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙

[JarmouniA]

Hi @summer4821smartbox, when I opened issue #68527, I was trying to implement brightness control on STM32H747I-Disco.
I spent non-negligeable time trying to find a solution for this by playing with the initialization order of LTDC, DSI and looking at their drivers to see what could cz the malfunction but without success.
If you are really pressed, my advice would be to just add LTDC to initialization order ignore-list as done here https://github.com/ajarmouni-st/zephyr_dev/blob/a4440e6d5e2abcd4c532b455ea3a153acf96d543/scripts/build/check_init_priorities.py#L54 and call it a day :).

[summer4821smartbox]

Hey @JarmouniA I tried your advice and it works!! Thank you so much!!

[erian747]

Hi
I just updated from 3.7.0 with a working a09 shield to latest main without any other changes, and i ran in to the same problem
Tried the fix about ignore-list but i still got the "nt35510: Failed reading ID (-5)"
Do you know where support for this shield got broken?

[JarmouniA]

Hi I just updated from 3.7.0 with a working a09 shield to latest main without any other changes, and i ran in to the same problem Tried the fix about ignore-list but i still got the "nt35510: Failed reading ID (-5)" Do you know where support for this shield got broken?

Hi @erian747, I would suspect one of these PRs: #77167, #77854

[github-actions]

This issue has been marked as stale because it has been open (more than) 60 days with no activity. Remove the stale label or add a comment saying that you would like to have the label removed otherwise this issue will automatically be closed in 14 days. Note, that you can always re-open a closed issue at any time.