All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Siva Chandra <sivachandra@google.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: Question about PSR training and idle frames
Date: Tue, 25 Feb 2014 20:34:06 +0200	[thread overview]
Message-ID: <20140225183406.GB3852@intel.com> (raw)
In-Reply-To: <CAGyQ6gycCp4_yHwYtS3nTfZQ5KReppDu96QxEpQ+8ZtU+UepHA@mail.gmail.com>

On Tue, Feb 25, 2014 at 10:06:19AM -0800, Siva Chandra wrote:
> Hi,
> 
> I would like to know what "training" and "idle frames" mean wrt PSR. I
> apologize if this is the wrong list for such questions.

Training just refers to the DP link training that may be necessary
after exiting PSR.

> 
> I am looking at the i915 driver in 3.10 which sets idle_frames to 1
> (function intel_edp_psr_enable_source in intel_dp.c) when enabling
> PSR. What does this mean, and what should one observe if idle_frames
> is set to a higher number?

IIRC idle frames indicates how many consecutive static frames must be
displayed before the hardware will enter PSR. So the higher you make
it, the longer you burn power scanning out the same picture.

But there might be some tradeoff with the PSR exit latency vs.
interactive content, and maybe there's some power cost to entering/exiting
PSR so if you every time end up exiting PSR immediately after entering
it, it might make sense to not enter PSR in the first place. These
are just gut feeling type of things, I have no numbers to back up anything.

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2014-02-25 18:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-25 18:06 Question about PSR training and idle frames Siva Chandra
2014-02-25 18:34 ` Ville Syrjälä [this message]
2014-02-25 19:36   ` Siva Chandra

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=20140225183406.GB3852@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sivachandra@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.