Summary: | [IVB, VLV] cursor lp3 latency correction | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Jesse Barnes <jbarnes> | ||||||
Component: | DRM/Intel | Assignee: | Daniel Vetter <daniel> | ||||||
Status: | CLOSED FIXED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||||
Severity: | normal | ||||||||
Priority: | medium | CC: | ben, chris, daniel, jbarnes | ||||||
Version: | XOrg git | ||||||||
Hardware: | Other | ||||||||
OS: | All | ||||||||
Whiteboard: | |||||||||
i915 platform: | i915 features: | ||||||||
Attachments: |
|
Description
Jesse Barnes
2012-05-22 14:53:48 UTC
Created attachment 70991 [details] [review] Double cursor latency for IVB lp3 Created attachment 70992 [details] [review] Double cursor latency for VLV sr commit af6c4575afada1a9c411e42439b5d40908865b11 Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Dec 11 12:01:43 2012 +0000 drm/i915: Double the cursor self-refresh latency on Valleyview It operates at twice the declared latency, so double the latency value used for the cursor watermark calculation. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=50248 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> CC: Jesse Barnes <jbarnes@virtuousgeek.org> Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> commit c43d0188d7be6e45eb52a27ed9df714ca2e04e0a Author: Chris Wilson <chris@chris-wilson.co.uk> Date: Tue Dec 11 12:01:42 2012 +0000 drm/i915: Fixup cursor latency used for IVB lp3 watermarks It operates at twice the declared latency, so adjust the computation to avoid potential flicker at low power. Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=50248 Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> CC: Jesse Barnes <jbarnes@virtuousgeek.org> Reviewed-by: Jesse Barnes <jbarnes@virtuousgeek.org> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch> |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.