summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVille Syrjälä <ville.syrjala@linux.intel.com>2022-02-17 12:32:20 +0200
committerVille Syrjälä <ville.syrjala@linux.intel.com>2022-02-23 13:29:21 +0200
commit7d7007686b0f999f90690d27eb013aba2eb8dc30 (patch)
tree2a56891fa9ec6c94dfc3cf0b246ed04341e1a74e
parent03a62c40544c057a4b0df86b7c4f17da7f7bb2ac (diff)
downloadlinux-7d7007686b0f999f90690d27eb013aba2eb8dc30.tar.bz2
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: 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>
-rw-r--r--drivers/gpu/drm/i915/display/intel_display.c4
1 files changed, 1 insertions, 3 deletions
diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
index d4cc4546564e..19f191b19979 100644
--- a/drivers/gpu/drm/i915/display/intel_display.c
+++ b/drivers/gpu/drm/i915/display/intel_display.c
@@ -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;
}