Commit 72f4901e authored by Daniel Vetter's avatar Daniel Vetter

drm/i915: check fb->pixel_format instead of bits_per_pixel

We've mostly switched over to the new more flexible schema, but
there's one check left in the modeset code.

Motivated by a question from Ville whether there's really no way an
unsupported pixel_format can escape into our platform update_plane
callbacks.

v2: Ville noticed that the fb->depth check is redudant when we already
check fb->pixel_format.

Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
Reviewed-by: default avatarVille Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: default avatarDaniel Vetter <daniel.vetter@ffwll.ch>
parent 1d5bfac9
...@@ -7954,10 +7954,8 @@ intel_set_config_compute_mode_changes(struct drm_mode_set *set, ...@@ -7954,10 +7954,8 @@ intel_set_config_compute_mode_changes(struct drm_mode_set *set,
config->mode_changed = true; config->mode_changed = true;
} else if (set->fb == NULL) { } else if (set->fb == NULL) {
config->mode_changed = true; config->mode_changed = true;
} else if (set->fb->depth != set->crtc->fb->depth) { } else if (set->fb->pixel_format !=
config->mode_changed = true; set->crtc->fb->pixel_format) {
} else if (set->fb->bits_per_pixel !=
set->crtc->fb->bits_per_pixel) {
config->mode_changed = true; config->mode_changed = true;
} else } else
config->fb_changed = true; config->fb_changed = true;
......
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