public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: hdegoede@redhat.com,
	Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>,
	luto@kernel.org, rodrigo.vivi@intel.com
Subject: [PATCH 0/3] PSR lag fixes
Date: Sun, 11 Feb 2018 22:08:02 -0800	[thread overview]
Message-ID: <20180212060805.3000-1-dhinakaran.pandiyan@intel.com> (raw)

PSR currently when enabled results in semi-permanent freezes or noticeable
cursor lags. 

https://patchwork.freedesktop.org/series/37598/ will fix long freezes due
to frame counter resets.

This series has three more fixes -
Patch 1 eliminates PSR exit for flips and makes us rely on the HW to do it.
Patch 2 fixes cusor move lag by relying on HW to exit PSR.
Patch 3 fixes temporary freeze seen with fbdev.

With both the series applied, PSR on my SKL ThinkPad feels pretty good.

Dhinakaran Pandiyan (2):
  drm/i915/psr: HW tracking for cursor moves to fix lags.
  drm/i915/psr: Wait for PSR transition to complete before exiting.

Rodrigo Vivi (1):
  drm/i915/psr: Use more PSR HW tracking.

 drivers/gpu/drm/i915/i915_drv.h          |  2 ++
 drivers/gpu/drm/i915/i915_gem.c          |  2 +-
 drivers/gpu/drm/i915/intel_drv.h         |  3 ++-
 drivers/gpu/drm/i915/intel_frontbuffer.c |  2 +-
 drivers/gpu/drm/i915/intel_psr.c         | 24 +++++++++++++++++++++++-
 5 files changed, 29 insertions(+), 4 deletions(-)

-- 
2.14.1

_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

             reply	other threads:[~2018-02-12  6:08 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-12  6:08 Dhinakaran Pandiyan [this message]
2018-02-12  6:08 ` [PATCH 1/3] drm/i915/psr: Use more PSR HW tracking Dhinakaran Pandiyan
2018-02-12  6:08 ` [PATCH 2/3] drm/i915/psr: HW tracking for cursor moves to fix lags Dhinakaran Pandiyan
2018-02-12  9:33   ` Chris Wilson
2018-02-13 21:46     ` [PATCH v2] " Dhinakaran Pandiyan
2018-02-13 21:54       ` Chris Wilson
2018-02-13 22:10         ` Pandiyan, Dhinakaran
2018-02-13 22:15           ` Chris Wilson
2018-02-13 22:45             ` Pandiyan, Dhinakaran
2018-02-13 22:59               ` Chris Wilson
2018-02-14  0:20                 ` Pandiyan, Dhinakaran
2018-02-12  6:08 ` [PATCH 3/3] drm/i915/psr: Wait for PSR transition to complete before exiting Dhinakaran Pandiyan
2018-02-12  6:30 ` ✓ Fi.CI.BAT: success for PSR lag fixes Patchwork
2018-02-12  7:19 ` ✗ Fi.CI.IGT: warning " Patchwork
2018-02-12  8:45 ` [PATCH 0/3] " Hans de Goede
2018-02-12 17:42   ` Pandiyan, Dhinakaran
2018-02-14  8:25     ` Hans de Goede
2018-03-14 20:49       ` Pandiyan, Dhinakaran
2018-03-14 22:09         ` Hans de Goede
2018-03-14 23:35           ` Pandiyan, Dhinakaran
2018-03-16  0:16             ` Rodrigo Vivi
2018-03-18 19:17               ` Hans de Goede
2018-02-13 22:26 ` ✗ Fi.CI.BAT: failure for PSR lag fixes (rev2) Patchwork

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20180212060805.3000-1-dhinakaran.pandiyan@intel.com \
    --to=dhinakaran.pandiyan@intel.com \
    --cc=hdegoede@redhat.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=luto@kernel.org \
    --cc=rodrigo.vivi@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox