From: Jeevan B <jeevan.b@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Jeevan B <jeevan.b@intel.com>,
Mohammed Thasleem <mohammed.thasleem@intel.com>
Subject: [PATCH i-g-t v10 6/7] tests/intel/kms_pm_dc: Add new test for DC3CO recovery after DC6
Date: Thu, 18 Jun 2026 11:59:03 +0530 [thread overview]
Message-ID: <20260618062904.2789476-7-jeevan.b@intel.com> (raw)
In-Reply-To: <20260618062904.2789476-1-jeevan.b@intel.com>
Adds a test to verify DC3CO continues to function properly
after a DC6 power cycle.
v2: Use test_dc_state_dpms for the DPMS/DC6 cycle.
Drop redundant PSR re-enable after DPMS/DC6.
v3: Refactor dynamic block to avoid duplicates.
v3: Remove TGL check for PSR2.
Signed-off-by: Jeevan B <jeevan.b@intel.com>
Reviewed-by: Mohammed Thasleem <mohammed.thasleem@intel.com>
---
tests/intel/kms_pm_dc.c | 47 +++++++++++++++++++++++++++++++++++++++++
1 file changed, 47 insertions(+)
diff --git a/tests/intel/kms_pm_dc.c b/tests/intel/kms_pm_dc.c
index 3602ef92f..d054d3b5c 100644
--- a/tests/intel/kms_pm_dc.c
+++ b/tests/intel/kms_pm_dc.c
@@ -55,6 +55,11 @@
* Description: Verify that DC3CO entry does not cause frame drops and successfully
* enters the power state
*
+ * SUBTEST: dc3co-after-dc6
+ * Description: Verify DC3CO entry is still functional after a DC6 entry and
+ * exit cycle, ensuring DC3CO is not broken by deeper power state
+ * transitions.
+ *
* SUBTEST: dc5-dpms
* Description: Validate display engine entry to DC5 state while all connectors's
* DPMS property set to OFF
@@ -634,6 +639,19 @@ static int has_panels_without_dc_support(igt_display_t *display)
return external_panel;
}
+static void test_dc3co_after_dc6(data_t *data)
+{
+ igt_require_dc_counter(data->debugfs_fd, IGT_INTEL_CHECK_DC3CO);
+ igt_require_dc_counter(data->debugfs_fd, IGT_INTEL_CHECK_DC6);
+
+ setup_output(data);
+ setup_dc3co(data);
+ test_dc_state_dpms(data, IGT_INTEL_CHECK_DC6);
+ setup_videoplayback(data);
+ check_dc3co_with_videoplayback_like_load(data);
+ cleanup_dc3co_fbs(data);
+}
+
static void test_deep_pkgc_state(data_t *data)
{
unsigned int pre_val = 0, cur_val = 0;
@@ -849,6 +867,35 @@ int igt_main()
}
}
+ igt_describe("Verify DC3CO entry is still functional after a DC6 entry "
+ "and exit cycle");
+ igt_subtest_with_dynamic("dc3co-after-dc6") {
+ static const struct dc3co_test_mode dc3co_modes[] = {
+ { PSR_MODE_2, "psr2" },
+ { PR_MODE, "pr" },
+ };
+
+ igt_require_f(igt_pm_pc8_plus_residencies_enabled(data.msr_fd),
+ "PC8+ residencies not supported\n");
+
+ for (int i = 0; i < ARRAY_SIZE(dc3co_modes); i++) {
+ const char *name = dc3co_modes[i].name;
+ data.op_psr_mode = dc3co_modes[i].mode;
+
+ igt_dynamic_f("%s", name) {
+ igt_require(psr_sink_support(data.drm_fd,
+ data.debugfs_fd,
+ data.op_psr_mode, NULL));
+
+ igt_require_f(intel_display_ver(data.devid) >= 35,
+ "Platform does not support DC3CO with %s\n",
+ data.op_psr_mode == PSR_MODE_2 ? "PSR2" : "Panel Replay");
+
+ test_dc3co_after_dc6(&data);
+ }
+ }
+ }
+
igt_describe("This test validates display engine entry to DC5 state "
"while PSR is active");
igt_subtest("dc5-psr") {
--
2.43.0
next prev parent reply other threads:[~2026-06-18 6:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-18 6:28 [PATCH i-g-t v10 0/7] Enable and Add new tests for DC3CO Jeevan B
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 ` Jeevan B [this message]
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
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-7-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.