Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "Joshi, Kunal1" <kunal1.joshi@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t 0/2] RFC extend kms_psr2_sf for panel replay
Date: Tue, 20 Jun 2023 11:45:58 +0000	[thread overview]
Message-ID: <e8c988224a17417acb2cb23b70c6123b96b634db.camel@intel.com> (raw)
In-Reply-To: <20230306152151.24200-1-kunal1.joshi@intel.com>

On Mon, 2023-03-06 at 20:51 +0530, Kunal Joshi wrote:
> Extended kms_psr2_sf test to run on sink which supports
> panel replay. All debugfs infois assumed and driver
> may not expose it as currently referred.
> 
> Kunal Joshi (2):
>   RFC lib/igt_psr Added library functions for panel replay
>   RFC tests/kms_psr2_sf Extended test to validate panel replay
> 
>  lib/igt_psr.c            |  62 +++++++++++++++++-
>  lib/igt_psr.h            |   5 ++
>  tests/i915/kms_psr2_sf.c | 137 ++++++++++++++++++++++++++++++-------
> --
>  3 files changed, 171 insertions(+), 33 deletions(-)
> 
Hello Kunal,

How I currently see this will be:

PSR mode: PR enabled
Source PSR ctl: enabled [0xXXXXXXXX]
Source PSR status: DEEP_SLEEP [0xXXXXXXXX]
Busy frontbuffer bits: 0x00000000
Performance counter: 0
Frame:	PSR2 SU blocks:
0	0
1	0
2	0
3	0
4	0
5	0
6	0
7	0
PSR2 selective fetch: enabled

I.e. PR mode w/ and w/o selective update/fetch.

BR,

Jouni Högander


      parent reply	other threads:[~2023-06-20 11:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-06 15:21 [igt-dev] [PATCH i-g-t 0/2] RFC extend kms_psr2_sf for panel replay Kunal Joshi
2023-03-06 15:21 ` [igt-dev] [PATCH i-g-t 1/2] RFC lib/igt_psr Added library functions " Kunal Joshi
2023-03-06 15:21 ` [igt-dev] [PATCH i-g-t 2/2] RFC tests/kms_psr2_sf Extended test to validate " Kunal Joshi
2023-03-06 16:22 ` [igt-dev] ✗ Fi.CI.BAT: failure for RFC extend kms_psr2_sf for " Patchwork
2023-06-20 11:45 ` Hogander, Jouni [this message]

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=e8c988224a17417acb2cb23b70c6123b96b634db.camel@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kunal1.joshi@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