summaryrefslogtreecommitdiffstats
path: root/drivers/gpu/drm/i915/intel_pm.c
diff options
context:
space:
mode:
authorPaulo Zanoni2015-10-14 00:13:25 +0200
committerPaulo Zanoni2015-12-03 14:32:13 +0100
commit754d113304aa640b9b3ffa5535a1565b95e5fdb6 (patch)
treef45e09bcc4ea029f30ca29c283717f1da24451a5 /drivers/gpu/drm/i915/intel_pm.c
parentdrm/i915: set dev_priv->fbc.crtc before scheduling the enable work (diff)
downloadkernel-qcow2-linux-754d113304aa640b9b3ffa5535a1565b95e5fdb6.tar.gz
kernel-qcow2-linux-754d113304aa640b9b3ffa5535a1565b95e5fdb6.tar.xz
kernel-qcow2-linux-754d113304aa640b9b3ffa5535a1565b95e5fdb6.zip
drm/i915: pass the crtc as an argument to intel_fbc_update()
There's no need to reevaluate the status of every single crtc when a single crtc changes its state. With this, we're cutting the case where due to a change in pipe B, intel_fbc_update() is called, then intel_fbc_find_crtc() concludes FBC should be enabled on pipe A, then it completely rechecks the state of pipe A only to conclude FBC should remain enabled on pipe A. If any change on pipe A triggers a need to recompute whether FBC is valid on pipe A, then at some point someone is going to call intel_fbc_update(PIPE_A). The addition of intel_fbc_deactivate() is necessary so we keep track of the previously selected CRTC when we do invalidate/flush. We're also going to continue the enable/disable/activate/deactivate concept in the next patches. v2: Rebase. v3: Rebase after changing the patch order. Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Paulo Zanoni <paulo.r.zanoni@intel.com> Link: http://patchwork.freedesktop.org/patch/msgid/
Diffstat (limited to 'drivers/gpu/drm/i915/intel_pm.c')
0 files changed, 0 insertions, 0 deletions