Skip to content

drm/msm/dsi: Skip the video mode wait when the hardware blocks DMA - #456

Closed
vlw wants to merge 1 commit into
msm8916-mainline:wip/msm8916/7.0from
vlw:msm-dsi-block-dma-wait
Closed

vlw wants to merge 1 commit into
msm8916-mainline:wip/msm8916/7.0from
vlw:msm-dsi-block-dma-wait

Conversation

@vlw

@vlw vlw commented Nov 15, 2026

Copy link
Copy Markdown

The 2–4 ms software wait before each command in video mode is longer than the vertical blanking of many panels, so each command cost about two frames. The hardware already holds the DMA until blanking on DSI 6G v1.2+.

Tested on a Samsung Galaxy A3 (SM-A300F, MSM8916) running LineageOS 24. A brightness update to the S6E88A0 panel takes about 36 ms instead of about 275 ms.

Per CONTRIBUTING.md this touches a shared upstream driver, so it is posted here for early review before going to the upstream lists.

Since DSI 6G v1.2.0 the host sets DSI_TRIG_CTRL.BLOCK_DMA_WITHIN_FRAME,
which holds a command DMA until the video stream is in blanking.
dsi_wait4video_eng_busy() still waits for VIDEO_DONE and then sleeps
2-4 ms before every command.

The sleep is longer than the vertical blanking of many panels. A
Samsung S6E88A0 panel (540x960, 24 blanking lines) has 0.41 ms of it.
The command then waits in hardware for the next blanking, so every
command costs about two frames.

Skip the software wait when the hardware blocks the DMA itself. On
MSM8916 a brightness update of six commands to that panel now takes
about 36 ms instead of about 275 ms.

Assisted-by: Claude Code:claude-opus-5-5
Signed-off-by: Vladimir Bely <vlwwwwww@gmail.com>
@vlw vlw closed this Nov 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant