Skip to content

Commit

Permalink
drm/i915: Remove odd any_ms=true assignment
Browse files Browse the repository at this point in the history
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: Ville Syrjälä <ville.syrjala@linux.intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20220217103221.10405-4-ville.syrjala@linux.intel.com
Reviewed-by: Manasi Navare <manasi.d.navare@intel.com>
  • Loading branch information
Ville Syrjälä committed Feb 23, 2022
1 parent 03a62c4 commit 7d70076
Showing 1 changed file with 1 addition and 3 deletions.
4 changes: 1 addition & 3 deletions drivers/gpu/drm/i915/display/intel_display.c
Original file line number Diff line number Diff line change
Expand Up @@ -7628,10 +7628,8 @@ static int intel_atomic_check(struct drm_device *dev,
}

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);
any_ms = true;
}
continue;
}

Expand Down

0 comments on commit 7d70076

Please sign in to comment.