From: Dibin Moolakadan Subrahmanian <dibin.moolakadan.subrahmanian@intel.com>
To: Jeevan B <jeevan.b@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <animesh.manna@intel.com>, <mohammed.thasleem@intel.com>
Subject: Re: [PATCH i-g-t v9 0/7] Enable and Add new tests for DC3CO
Date: Thu, 18 Jun 2026 10:10:57 +0530 [thread overview]
Message-ID: <92e5ac33-edad-4dc4-aed3-0a29d1bf9fb4@intel.com> (raw)
In-Reply-To: <20260609034650.2281712-1-jeevan.b@intel.com>
On 6/9/2026 9:16 AM, Jeevan B wrote:
> 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.
>
> Jeevan B (7):
> tests: 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 | 322 +++++++++++++++++++++++++++++++++++++---
> tests/kms_vrr.c | 34 +++++
> 2 files changed, 338 insertions(+), 18 deletions(-)
LGTM.
Acked-by: Dibin Moolakadan Subrahmanian <dibin.moolakadan.subrahmanian@intel.com>
prev parent reply other threads:[~2026-06-18 4:41 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-09 3:46 [PATCH i-g-t v9 0/7] Enable and Add new tests for DC3CO Jeevan B
2026-06-09 3:46 ` [PATCH i-g-t v9 1/7] tests: s/check_dc_counter/assert_dc_counter Jeevan B
2026-06-10 9:25 ` Thasleem, Mohammed
2026-06-09 3:46 ` [PATCH i-g-t v9 2/7] tests/intel/kms_pm_dc: Replace require with proper assertion Jeevan B
2026-06-09 3:46 ` [PATCH i-g-t v9 3/7] tests/intel/kms_pm_dc: Enable DC3CO test for PSR2/PR modes Jeevan B
2026-06-18 4:16 ` Dibin Moolakadan Subrahmanian
2026-06-09 3:46 ` [PATCH i-g-t v9 4/7] tests/kms_vrr: Add new test for DC3CO validation with LOBF Jeevan B
2026-06-09 3:46 ` [PATCH i-g-t v9 5/7] tests/intel/kms_pm_dc: Add dc3co framedrop validation test Jeevan B
2026-06-09 10:54 ` Thasleem, Mohammed
2026-06-09 3:46 ` [PATCH i-g-t v9 6/7] tests/intel/kms_pm_dc: Add new test for DC3CO recovery after DC6 Jeevan B
2026-06-09 3:46 ` [PATCH i-g-t v9 7/7] tests/intel/kms_pm_dc: Add dc3co-vpb-framegap subtest Jeevan B
2026-06-09 7:37 ` ✓ i915.CI.BAT: success for Enable and Add new tests for DC3CO Patchwork
2026-06-09 7:50 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-09 17:14 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-06-09 21:50 ` ✗ i915.CI.Full: " Patchwork
2026-06-18 4:40 ` Dibin Moolakadan Subrahmanian [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=92e5ac33-edad-4dc4-aed3-0a29d1bf9fb4@intel.com \
--to=dibin.moolakadan.subrahmanian@intel.com \
--cc=animesh.manna@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jeevan.b@intel.com \
--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