All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Runyan, Arthur J" <arthur.j.runyan@intel.com>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>,
	Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	Matthew Garrett <mjg59@srcf.ucam.orgviacodon.org.uk>,
	"Vivi, Rodrigo" <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 2/5] drm/i915: PSR: Remove Low Power HW tracking mask.
Date: Mon, 22 Jun 2015 22:31:32 +0000	[thread overview]
Message-ID: <C7E999358BBE9E45938BA940F5F51108757B7DDD@fmsmsx116.amr.corp.intel.com> (raw)
In-Reply-To: <CABVU7+sgz=aex1NXio4J1pr97EYUuQ1PQw0Zm37A7wrw3mBz=Q@mail.gmail.com>

-- Daniel
>> I guess I don't really understand your description, but it does sound
>> strange ... runtime pm enabling from my patch is only about D3, power
>> well changes are still done. And as long as we have anything enabled
>> (even with PSR) we'll prevent D3.
>>
>> So the only thing I can think of is that somehow D3 wreaks something
>> in the PSR setup and that's causing issues. Unfortunately I have no
>> idea about our hw details around PSR and D3, so no idea. Maybe Art has
>> some?
>
-- Rodrigo
>I don't know this relation as well. When I found this LPSP maks that
>made PSR working it was totally by forcing all masks and start
>removing one by one up to the point that this Low Power something did
>the trick. At that time Artur had told about power well handling
>enabled, but now after Mathew reported that issue I noticed this Low
>power flag was also related to runtime PM...
>

Let me see if I understand what is happening.  Runtime PM seemed to cause PSR to miss some screen updates when you had LPSP masked, then you stopped masking  LPSP and it fixed the missing updates?
My first guess is that you are not in LPSP at this point, so removing the mask is effectively disabling PSR, which prevents PSR from missing screen updates.   Are you still getting good PSR residency with LPSP masked in this situation?  

The LPSP mask is only there fro debug.  We don't normally want PSR to enter without LPSP because there can be undesirable things like clocks stopping which could break the display audio controller and codec.
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-06-22 22:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 18:43 [PATCH 1/5] drm/i915: Enable runtime pm Rodrigo Vivi
2015-06-18 18:43 ` [PATCH 2/5] drm/i915: PSR: Remove Low Power HW tracking mask Rodrigo Vivi
2015-06-19 20:32   ` Daniel Vetter
2015-06-19 22:05     ` Rodrigo Vivi
2015-06-22 22:31       ` Runyan, Arthur J [this message]
2015-06-22 23:07         ` Rodrigo Vivi
2015-06-23 18:40           ` Runyan, Arthur J
2015-06-23 18:52             ` Rodrigo Vivi
2015-06-18 18:43 ` [PATCH 3/5] drm/i915: Remove unused ring argument from frontbuffer invalidate and busy functions Rodrigo Vivi
2015-06-22 14:00   ` Daniel Vetter
2015-06-18 18:43 ` [PATCH 4/5] drm/i915: Invalidate frontbuffer bits on FBDEV sync Rodrigo Vivi
2015-06-22 13:58   ` Daniel Vetter
2015-06-22 16:53     ` Rodrigo Vivi
2015-06-18 18:43 ` [PATCH 5/5] drm/i915: Enable PSR by default Rodrigo Vivi
2015-06-18 18:54   ` Paulo Zanoni
2015-06-24 21:48     ` Paulo Zanoni
2015-06-24 22:12       ` Vivi, Rodrigo
2015-06-18 18:53 ` [PATCH 1/5] drm/i915: Enable runtime pm Rodrigo Vivi

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=C7E999358BBE9E45938BA940F5F51108757B7DDD@fmsmsx116.amr.corp.intel.com \
    --to=arthur.j.runyan@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=mjg59@srcf.ucam.orgviacodon.org.uk \
    --cc=rodrigo.vivi@gmail.com \
    --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 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.