Unfortunately not fully solved, as today I saw a failed command when kernel did automatic blanking of the display.
After automatic unblanking (restart of our Qt application) we seewhich seems OK, but display does not work.
Even repeated blanking/unblanking (via /sys/class/graphics/fb0/blank) does not show any further messages in dmesg and display does not show anything.
AFAIK blanking calls disable() and unprepare(), which means that just two short commands are sent (mipi_dsi_dcs_set_display_off() and mipi_dsi_dcs_enter_sleep_mode(), which should not lead to any timing problems during the interface-blanking periods?
I suppose it was just "bad luck" that a single command did somehow fail? Does that rarely happen?
Additional info:
We do not need the automatic kernel blanking, thus we usein the cmdline.txt!
After a new start of the device this works (display never gets blanked), and even our Qt application (using OpenGL ES 3.1 MESA as backend) is running properly (showing a test video) over days.
BUT when the application is stopped (once running) the kernel does automatic blanking of the display after 15minutes (we measured about 900seconds). Not really knowing why this happens ...
Code:
[ 5215.701643] [drm:vc4_dsi_host_transfer] *ERROR* DSI transfer failed whilst in HS mode stat: 0x05020803[ 5215.701678] panel-sitronix-st7703 fe700000.dsi.0: Failed to enter sleep mode: -110Code:
[ 7162.501658] panel-sitronix-st7703 fe700000.dsi.0: Sending init code for TSONT H35C302_00W ...Even repeated blanking/unblanking (via /sys/class/graphics/fb0/blank) does not show any further messages in dmesg and display does not show anything.
AFAIK blanking calls disable() and unprepare(), which means that just two short commands are sent (mipi_dsi_dcs_set_display_off() and mipi_dsi_dcs_enter_sleep_mode(), which should not lead to any timing problems during the interface-blanking periods?
I suppose it was just "bad luck" that a single command did somehow fail? Does that rarely happen?
Additional info:
We do not need the automatic kernel blanking, thus we use
Code:
consoleblank=0After a new start of the device this works (display never gets blanked), and even our Qt application (using OpenGL ES 3.1 MESA as backend) is running properly (showing a test video) over days.
BUT when the application is stopped (once running) the kernel does automatic blanking of the display after 15minutes (we measured about 900seconds). Not really knowing why this happens ...
Statistics: Posted by RinaMat — Tue Nov 26, 2024 11:08 am