Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jouni Högander" <jouni.hogander@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: ramanaidu.naladala@intel.com,
	"Jouni Högander" <jouni.hogander@intel.com>
Subject: [PATCH i-g-t v2 0/5] PSR testing improvement by checking sink status
Date: Wed, 11 Sep 2024 08:49:53 +0300	[thread overview]
Message-ID: <20240911054958.1023925-1-jouni.hogander@intel.com> (raw)

Currently we are not checking panel status in our PSR testcases. This
might lead to situation where panel is not even aware of PSR being
used. Also possible errors detected by a sink are ignored by our
testcase. This patch set is trying to address this.

v2: split kms_fbt and kms_pm_dc to separate patches

Jouni Högander (5):
  lib/igt_psr: Add mechanism to check sink status as well
  tests/intel/kms_psr*: Add psr_sink_error_check to PSR tests
  tests/intel/kms_fbt: Add psr_sink_error_check to PSR tests
  test/intel/kms_pm_dc: Add psr_sink_error_check to PSR tests
  tests/intel/kms_dirtyfb: Check features after rendering

 lib/igt_psr.c                          | 52 +++++++++++++++++++++++++-
 lib/igt_psr.h                          |  1 +
 tests/intel/kms_dirtyfb.c              | 33 +++++++++++++++-
 tests/intel/kms_frontbuffer_tracking.c |  5 ++-
 tests/intel/kms_pm_dc.c                |  2 +
 tests/intel/kms_psr.c                  |  2 +
 tests/intel/kms_psr2_sf.c              |  2 +
 tests/intel/kms_psr2_su.c              |  2 +
 tests/intel/kms_psr_stress_test.c      |  1 +
 9 files changed, 95 insertions(+), 5 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-09-11  5:50 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-11  5:49 Jouni Högander [this message]
2024-09-11  5:49 ` [PATCH i-g-t v2 1/5] lib/igt_psr: Add mechanism to check sink status as well Jouni Högander
2024-09-11  5:49 ` [PATCH i-g-t v2 2/5] tests/intel/kms_psr*: Add psr_sink_error_check to PSR tests Jouni Högander
2024-09-11 10:53   ` Thasleem, Mohammed
2024-09-11  5:49 ` [PATCH i-g-t v2 3/5] tests/intel/kms_fbt: " Jouni Högander
2024-09-11 11:34   ` Thasleem, Mohammed
2024-09-11  5:49 ` [PATCH i-g-t v2 4/5] test/intel/kms_pm_dc: " Jouni Högander
2024-09-11  9:54   ` Thasleem, Mohammed
2024-09-11  5:49 ` [PATCH i-g-t v2 5/5] tests/intel/kms_dirtyfb: Check features after rendering Jouni Högander
2024-09-12  3:34 ` ✓ CI.xeBAT: success for PSR testing improvement by checking sink status Patchwork
2024-09-12  3:46 ` ✓ Fi.CI.BAT: " Patchwork
2024-09-12  8:12 ` ✓ CI.xeFULL: " Patchwork
2024-09-12 22:50 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-09-17 11:38   ` Hogander, Jouni
2024-09-17 11:59 ` [PATCH i-g-t v2 0/5] " Hogander, Jouni

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=20240911054958.1023925-1-jouni.hogander@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=ramanaidu.naladala@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