We do this during enabling, but not during disabling. BSpec doesn't require this explicitly in either case, however based on my tests nothing clears it after it gets set, so let's do this during disabling as well.
Signed-off-by: Imre Deak <[email protected]> --- drivers/gpu/drm/i915/display/intel_dp_mst.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c b/drivers/gpu/drm/i915/display/intel_dp_mst.c index 1c3654a117a9..566fe469940d 100644 --- a/drivers/gpu/drm/i915/display/intel_dp_mst.c +++ b/drivers/gpu/drm/i915/display/intel_dp_mst.c @@ -368,6 +368,8 @@ static void intel_mst_disable_dp(struct intel_atomic_state *state, drm_dp_mst_reset_vcpi_slots(&intel_dp->mst_mgr, connector->port); + clear_act_sent(old_crtc_state, intel_dp); + ret = drm_dp_update_payload_part1(&intel_dp->mst_mgr); if (ret) { drm_dbg_kms(&i915->drm, "failed to update payload %d\n", ret); -- 2.23.1 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
