Commit 7d700768 authored by Ville Syrjälä's avatar Ville Syrjälä

drm/i915: Remove odd any_ms=true assignment

For some reason we're flagging that we need to run through the
full modeset calculations (any_ms==true -> do cdclk/etc. checks)
if any crtc got initially flagged for a modeset and is not
enabled via the uapi. No idea why this is here since later on
(after all fastset handling) we do full run through the crtcs
and flag any_ms if anything still needs a full modeset. So let's
just throw out this early weirdo.
Signed-off-by: default avatarVille Syrjälä <ville.syrjala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20220217103221.10405-4-ville.syrjala@linux.intel.comReviewed-by: default avatarManasi Navare <manasi.d.navare@intel.com>
parent 03a62c40
...@@ -7628,10 +7628,8 @@ static int intel_atomic_check(struct drm_device *dev, ...@@ -7628,10 +7628,8 @@ static int intel_atomic_check(struct drm_device *dev,
} }
if (!new_crtc_state->uapi.enable) { if (!new_crtc_state->uapi.enable) {
if (!intel_crtc_is_bigjoiner_slave(new_crtc_state)) { if (!intel_crtc_is_bigjoiner_slave(new_crtc_state))
intel_crtc_copy_uapi_to_hw_state_modeset(state, crtc); intel_crtc_copy_uapi_to_hw_state_modeset(state, crtc);
any_ms = true;
}
continue; continue;
} }
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment