<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Commit 0c06fa15600 (Add support of BT.2020 Colorimetry to DP MSA) causing 4K monitor corruption" href="https://bugs.freedesktop.org/show_bug.cgi?id=112212#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Commit 0c06fa15600 (Add support of BT.2020 Colorimetry to DP MSA) causing 4K monitor corruption" href="https://bugs.freedesktop.org/show_bug.cgi?id=112212">bug 112212</a> from <a class="email" href="mailto:elongbug@gmail.com" title="Mun, Gwan-gyeong <elongbug@gmail.com>"> Mun, Gwan-gyeong</a> <pre>A sympton of weird screen seems that MSA uses wrong configuration. The commit "drm/i915/dp: Add support of BT.2020 Colorimetry to DP MSA" 1) checks use case of BT.2020 and enables MSA for VSC SDP for BT.2020 Colorimetry. 2) changes a calling of intel_ddi_set_pipe_settings() function into intel_ddi_pre_enable_dp() to handle colorspace of drm_connector_state. The changed MSA setting timing might lead (I am not sure) weird setting of MSA, I am on digging it in detail. Ken, could you share the kernel log which Lakshmi said.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>