public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Vijay Purushothaman <vijay.a.purushothaman@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>,
	Chris Wilson <chris@chris-wilson.co.uk>,
	intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 06/11] drm/i915: Force PSR exit by inactivating it.
Date: Tue, 03 Jun 2014 16:40:47 +0530	[thread overview]
Message-ID: <538DAD37.1000605@intel.com> (raw)
In-Reply-To: <CABVU7+vERMbRXecS+-j6e+aD9Xb8vaVmuLRPqMQwNcd+BomAag@mail.gmail.com>

On 5/16/2014 10:12 PM, Rodrigo Vivi wrote:
>
>
>
> On Fri, May 16, 2014 at 3:23 AM, Chris Wilson <chris@chris-wilson.co.uk
> <mailto:chris@chris-wilson.co.uk>> wrote:
>
>     On Thu, May 15, 2014 at 08:13:05PM -0400, Rodrigo Vivi wrote:
>      > The perfect solution for psr_exit is the hardware tracking the
>     changes and
>      > doing the psr exit by itself. This scenario works for HSW and BDW
>     with some
>      > environments like Gnome and Wayland.
>      >
>      > However there are many other scenarios that this isn't true.
>     Mainly one right
>      > now is KDE users on HSW and BDW with PSR on. User would miss many
>     screen
>      > updates. For instances any key typed could be seen only when
>     mouse cursor is
>      > moved. So this patch introduces the ability of trigger PSR exit
>     on kernel side
>      > on some common cases that.
>
>     You know that userspace has been waiting for a PSR flag for over a year
>     now so that it can use the more efficient rendering paths when it makes
>     sense.
>
>
> yeah... this item is lingering on my to do list... but reaching a point
> where I won't be able to continue postponing it ;)
>
>> What happened to the front buffer tracking?
>
> What front buffer tracking? hehe
> I'm wondering about this since I started looking to fbc and psr and
> could never find a reliable way.
>
FBC should cover most of the scenarios except cursor planes.. When ever 
cursor planes are enabled you can fall back to s/w controlled exit path.

If you can elaborate on the exact issue that you are facing with FBC and 
PSR may be i can help..

Thanks,
Vijay

>
>     -Chris
>
>     --
>     Chris Wilson, Intel Open Source Technology Centre
>
>
>
>
> --
> Rodrigo Vivi
> Blog: http://blog.vivi.eng.br
>
>
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>

  reply	other threads:[~2014-06-03 11:11 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-16  0:12 [PATCH 00/11] HSW/BDW PSR Rodrigo Vivi
2014-05-16  0:13 ` [PATCH 01/11] drm/i915: move psr_setup_done to psr struct Rodrigo Vivi
2014-05-22 17:50   ` Paulo Zanoni
2014-05-23 20:45     ` [PATCH] " Rodrigo Vivi
2014-05-26  7:44       ` Daniel Vetter
2014-05-16  0:13 ` [PATCH 02/11] drm/i915: Update PSR on resume Rodrigo Vivi
2014-05-23 20:51   ` Paulo Zanoni
2014-05-27 23:50     ` [PATCH] " Rodrigo Vivi
2014-05-28 12:57       ` Daniel Vetter
2014-06-04 19:17         ` Rodrigo Vivi
2014-06-05  9:15           ` Daniel Vetter
2014-06-10 15:11             ` Rodrigo Vivi
2014-06-10 15:24               ` Daniel Vetter
2014-06-10 10:49                 ` [PATCH] drm/i915: Force full PSR setup during crtc enable Rodrigo Vivi
2014-06-11  9:42                   ` Daniel Vetter
2014-08-08 17:19                 ` [PATCH] drm/i915: Update PSR on resume Rodrigo Vivi
2014-08-09  7:40                   ` Daniel Vetter
2014-08-11 16:57                     ` Rodrigo Vivi
2014-08-11 17:31                       ` Daniel Vetter
2014-05-16  0:13 ` [PATCH 03/11] drm/i915: Use HAS_PSR to avoid unecessary interactions Rodrigo Vivi
2014-06-03  9:26   ` Vijay Purushothaman
2014-05-16  0:13 ` [PATCH 04/11] drm/i915: Don't let update_psr function actually enable PSR Rodrigo Vivi
2014-06-03 11:04   ` Vijay Purushothaman
2014-05-16  0:13 ` [PATCH 05/11] drm/i915: Do not try to enable PSR when Panel doesn't suport it Rodrigo Vivi
2014-05-16 10:21   ` Chris Wilson
2014-05-16 16:39     ` Rodrigo Vivi
2014-05-16  0:13 ` [PATCH 06/11] drm/i915: Force PSR exit by inactivating it Rodrigo Vivi
2014-05-16 10:23   ` Chris Wilson
2014-05-16 16:42     ` Rodrigo Vivi
2014-06-03 11:10       ` Vijay Purushothaman [this message]
2014-05-16 10:25   ` Chris Wilson
2014-05-16  0:13 ` [PATCH 07/11] drm/i915: BDW PSR: Add single frame update support Rodrigo Vivi
2014-05-16  0:13 ` [PATCH 08/11] drm/i915: BDW PSR: Remove limitations that aren't valid for BDW Rodrigo Vivi
2014-06-03 11:20   ` Vijay Purushothaman
2014-05-16  0:13 ` [PATCH 09/11] drm/i915: BDW PSR: Remove DDIA limitation for Broadwell Rodrigo Vivi
2014-05-16  0:13 ` [PATCH 10/11] drm/i915: Improve PSR debugfs status Rodrigo Vivi
2014-06-02 18:24   ` Vijay Purushothaman
2014-06-03  7:40     ` Daniel Vetter
2014-06-03 11:22       ` Vijay Purushothaman
2014-05-16  0:13 ` [PATCH 11/11] drm/i915: PSR HSW: update after enabling sprite Rodrigo Vivi
2014-06-03 11:25   ` Vijay Purushothaman
2014-06-12 10:12 ` [PATCH 00/11] HSW/BDW PSR Vijay Purushothaman

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=538DAD37.1000605@intel.com \
    --to=vijay.a.purushothaman@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=rodrigo.vivi@gmail.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