From: Jeevan B <jeevan.b@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Jeevan B <jeevan.b@intel.com>
Subject: [PATCH i-g-t v10 0/7] Enable and Add new tests for DC3CO
Date: Thu, 18 Jun 2026 11:58:57 +0530 [thread overview]
Message-ID: <20260618062904.2789476-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.
v3: Adds a test to verify DC3CO continues to function properly
after a DC6 power cycle and rename function name in first patch.
v4: Add a new test to verify DC3CO continues to funct
v5: Addressed review comments, clarified platform support wording.
Simplified PSR mode handling and fixed output-aware PSR checks.
Cleaned up and aligned new DC3CO test flows and guards.
v6: Addressed review comments.
v7: Fix framedrop test logic and dynamic block.
v8: Update commit message and test description.
v9: Replaced hardcoded values with global constants and updated
logic for framedrop test.
v10: Remove TGL check for PSR2.
Jeevan B (7):
tests/intel/kms_pm_dc: s/check_dc_counter/assert_dc_counter
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 dc3co framedrop validation test
tests/intel/kms_pm_dc: Add new test for DC3CO recovery after DC6
tests/intel/kms_pm_dc: Add dc3co-vpb-framegap subtest
tests/intel/kms_pm_dc.c | 310 +++++++++++++++++++++++++++++++++++++---
tests/kms_vrr.c | 34 +++++
2 files changed, 326 insertions(+), 18 deletions(-)
--
2.43.0
next reply other threads:[~2026-06-18 6:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 6:28 Jeevan B [this message]
2026-06-18 6:28 ` [PATCH i-g-t v10 1/7] tests/intel/kms_pm_dc: s/check_dc_counter/assert_dc_counter Jeevan B
2026-06-18 6:28 ` [PATCH i-g-t v10 2/7] tests/intel/kms_pm_dc: Replace require with proper assertion Jeevan B
2026-06-18 6:29 ` [PATCH i-g-t v10 3/7] tests/intel/kms_pm_dc: Enable DC3CO test for PSR2/PR modes Jeevan B
2026-06-18 6:29 ` [PATCH i-g-t v10 4/7] tests/kms_vrr: Add new test for DC3CO validation with LOBF Jeevan B
2026-06-18 6:29 ` [PATCH i-g-t v10 5/7] tests/intel/kms_pm_dc: Add dc3co framedrop validation test Jeevan B
2026-06-18 6:29 ` [PATCH i-g-t v10 6/7] tests/intel/kms_pm_dc: Add new test for DC3CO recovery after DC6 Jeevan B
2026-06-18 6:29 ` [PATCH i-g-t v10 7/7] tests/intel/kms_pm_dc: Add dc3co-vpb-framegap subtest Jeevan B
2026-06-18 8:20 ` ✓ Xe.CI.BAT: success for Enable and Add new tests for DC3CO Patchwork
2026-06-18 8:33 ` ✓ i915.CI.BAT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2026-06-18 6:27 [PATCH i-g-t v10 0/7] " Jeevan B
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=20260618062904.2789476-1-jeevan.b@intel.com \
--to=jeevan.b@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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