CRTC CTM state lost on next-20240709 with 0001-drm-msm-dpu1-don-t-choke-on-disabling-the-writeback-.patch
CRTC state isn't being restored correctly when running with 0001-drm-msm-dpu1-don-t-choke-on-disabling-the-writeback-.patch from #57 (comment 2483176). After resume, Color Transform Matrix (CTM) property is lost. (If internal panel/screen used CTM for Night Light, it no longer is active after resume.) Toggling CTM related functionality on and off after resume, triggers a large number of the following error messages:
[drm:_dpu_rm_check_lm_and_get_connected_blks] [dpu error]failed to get dspp on lm 0
[drm:_dpu_rm_make_reservation] [dpu error]unable to find appropriate mixers
[drm:dpu_rm_reserve] [dpu error]failed to reserve hw resources: -119Attached are the dmesg logs based on next-20240709 with 0002-drm-msm-dpu-don-t-play-tricks-with-debug-macros.patch but without 0001-drm-msm-dpu1-don-t-choke-on-disabling-the-writeback-.patch: dmesg-linux-next-suspend-debug-patch.txt as well as with both pacthes applied: dmesg-linux-next-patched-suspend.txt. The CTM issue only occurs with both patches applied. For each file, I start recording with Night Light enabled, then 1/ suspend and resume the system 2/ toggle "Night Light" (CTM use) off and on again. With your patch, step 2 does not result in visible behavior. I also notice slight screen flickering on the internal display when moving the mouse on the internal display with your patch