In several cases the drm/msm can cause an SMMU fault on modesetting (due to the display controller still scanning the BO which is being unmapped). Fix two cases which I stumbled upon.
Signed-off-by: Dmitry Baryshkov <[email protected]> --- Dmitry Baryshkov (2): drm/msm: fix framebuffer pin refcount leak on prepare failure drm/msm: release scanout framebuffers only after a vblank drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c | 2 +- .../gpu/drm/msm/disp/dpu1/dpu_encoder_phys_wb.c | 2 +- drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c | 3 +- drivers/gpu/drm/msm/disp/mdp4/mdp4_crtc.c | 2 +- drivers/gpu/drm/msm/disp/mdp4/mdp4_plane.c | 2 +- drivers/gpu/drm/msm/disp/mdp5/mdp5_crtc.c | 2 +- drivers/gpu/drm/msm/disp/mdp5/mdp5_plane.c | 2 +- drivers/gpu/drm/msm/msm_drv.h | 3 +- drivers/gpu/drm/msm/msm_fb.c | 26 ++++++- drivers/gpu/drm/msm/msm_kms.c | 88 ++++++++++++++++++++++ drivers/gpu/drm/msm/msm_kms.h | 29 +++++++ 11 files changed, 150 insertions(+), 11 deletions(-) --- base-commit: 140b13475302601368c0cf4e193e66126a49feb3 change-id: 20260902-fd-kms-fix-smmu-2d4baaf460b0 prerequisite-change-id: 20260202-msm-ci-sm8650-bd3933b73635:v1 Best regards, -- With best wishes Dmitry
