From: Jeevan B <jeevan.b@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: mohammed.thasleem@intel.com, Jeevan B <jeevan.b@intel.com>
Subject: [PATCH i-g-t v2 0/4] Enable and Add new tests for DC3CO
Date: Tue, 14 Apr 2026 15:20:10 +0530 [thread overview]
Message-ID: <20260414095014.55950-1-jeevan.b@intel.com> (raw)
Enable DC3CO tests for PSR/PR for display versions >= 35, add a new
test for DC3CO to validate frame drops, and test DC3CO with LOBF.
Jeevan B (4):
tests/intel/kms_pm_dc: Replace require with proper assertion
tests/intel/kms_pm_dc: Enable DC3CO test for PSR2/PR modes
tests/kms_vrr: Add new test for DC3CO validation with LOBF
tests/intel/kms_pm_dc: Add new test for dc3co framedrop validation
tests/intel/kms_pm_dc.c | 157 +++++++++++++++++++++++++++++++++++++---
tests/kms_vrr.c | 33 +++++++++
2 files changed, 178 insertions(+), 12 deletions(-)
--
2.43.0
next reply other threads:[~2026-04-14 9:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 9:50 Jeevan B [this message]
2026-04-14 9:50 ` [PATCH i-g-t v2 1/4] tests/intel/kms_pm_dc: Replace require with proper assertion Jeevan B
2026-04-14 10:51 ` Jani Nikula
2026-04-14 9:50 ` [PATCH i-g-t v2 2/4] tests/intel/kms_pm_dc: Enable DC3CO test for PSR2/PR modes Jeevan B
2026-04-14 9:50 ` [PATCH i-g-t v2 3/4] tests/kms_vrr: Add new test for DC3CO validation with LOBF Jeevan B
2026-04-14 9:50 ` [PATCH i-g-t v2 4/4] tests/intel/kms_pm_dc: Add new test for dc3co framedrop validation Jeevan B
2026-04-14 10:53 ` Jani Nikula
2026-04-14 10:34 ` ✓ i915.CI.BAT: success for Enable and Add new tests for DC3CO (rev3) Patchwork
2026-04-14 11:26 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-14 13:01 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-14 17:30 ` ✗ i915.CI.Full: " Patchwork
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=20260414095014.55950-1-jeevan.b@intel.com \
--to=jeevan.b@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=mohammed.thasleem@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