Skip to content

Test/backport DPU migration#160

Merged
minlexx merged 3 commits intoqcom-sdm660-6.18.yfrom
alexeymin/dpu-migration
Jan 13, 2026
Merged

Test/backport DPU migration#160
minlexx merged 3 commits intoqcom-sdm660-6.18.yfrom
alexeymin/dpu-migration

Conversation

@minlexx
Copy link
Copy Markdown
Member

@minlexx minlexx commented Jan 10, 2026

Test & backport this series: https://patchwork.freedesktop.org/series/159224/

This will swith every device to use DPU display driver instead of MDP5.

Needs testing specifically on devices with command mode panels. And just to be extra sure, validated it doesn't break video mode panels.

Contributes to #148

@minlexx
Copy link
Copy Markdown
Member Author

minlexx commented Jan 11, 2026

Command mode panel works again on sony-pioneer!

And it keeps working on video mode as well (tested on xiaomi-whyred).

lumag added 3 commits January 13, 2026 16:38
DPU 3.x don't have separate intr_start interrupt, drop it from catalog
files.

Fixes: 94391a1 ("drm/msm/dpu1: Add MSM8998 to hw catalog")
Fixes: 7204df5 ("drm/msm/dpu: add support for SDM660 and SDM630 platforms")
Signed-off-by: Dmitry Baryshkov <[email protected]>
DPU units before 4.x don't have a separate CTL_START IRQ to mark the
begin of the data transfer. In such a case, wait for the frame transfer
to complete rather than trying to wait for the CTL_START interrupt (and
obviously hitting the timeout).

Fixes: 050770c ("drm/msm/dpu: Fix timeout issues on command mode panels")
Reported-by: Alexey Minnekhanov <[email protected]>
Closes: https://lore.kernel.org/r/[email protected]
Signed-off-by: Dmitry Baryshkov <[email protected]>
Currently MDP5 3.x (MSM8998, SDM630 and SDM660) platforms are support
by both DPU and MDP5 drivers. Support for them in the DPU driver is
mature enough, so it's no longer sensible to keep them enabled in the
MDP5 driver. Not to mention that MSM8998 never used an MDP5 compatible
string. Drop support for the MDP5 3.x genration inside the MDP5
driver and migrate those to the DPU driver only.

Note: this will break if one uses the DT generated before v6.3 as they
had only the generic, "qcom,mdp5" compatible string for SDM630 and
SDM660. However granted that we had two LTS releases inbetween I don't
think it is an issue.

Signed-off-by: Dmitry Baryshkov <[email protected]>
@minlexx minlexx force-pushed the alexeymin/dpu-migration branch from 0a67e03 to 9af2bfc Compare January 13, 2026 13:38
@minlexx minlexx merged commit b10422c into qcom-sdm660-6.18.y Jan 13, 2026
3 checks passed
@minlexx minlexx deleted the alexeymin/dpu-migration branch January 13, 2026 13:57
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.

2 participants