aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/i915/intel_psr.c
diff options
context:
space:
mode:
authorJosé Roberto de Souza <jose.souza@intel.com>2019-03-07 16:00:44 -0800
committerJosé Roberto de Souza <jose.souza@intel.com>2019-03-08 10:31:42 -0800
commitd168da8cfc7c49895fabc5570bfb2656013eb12c (patch)
tree23ae23b86bb68a4c11b27979a0c543aac24a965f /drivers/gpu/drm/i915/intel_psr.c
parentdrm/i915/psr: Only lookup for enabled CRTCs when forcing a fastset (diff)
downloadlinux-dev-d168da8cfc7c49895fabc5570bfb2656013eb12c.tar.xz
linux-dev-d168da8cfc7c49895fabc5570bfb2656013eb12c.zip
drm/i915: Compute and commit color features in fastsets
In any commit, intel_modeset_pipe_config() will initialilly clear and then recalculate most of the pipe states but it leave intel specific color features states in reset state. If after intel_pipe_config_compare() is detected that a fastset is possible it will mark update_pipe as true and unsed mode_changed, causing the color features state to be kept in reset state and then latter being committed to hardware disabling the color features. This issue can be reproduced by any code patch that duplicates the actual(with color features already enabled) state and only mark mode_changed as true. Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com> Cc: Ville Syrjälä <ville.syrjala@linux.intel.com> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com> Signed-off-by: José Roberto de Souza <jose.souza@intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20190308000050.6226-3-jose.souza@intel.com
Diffstat (limited to 'drivers/gpu/drm/i915/intel_psr.c')
0 files changed, 0 insertions, 0 deletions