From: Jani Nikula <jani.nikula@intel.com>
To: Jeevan B <jeevan.b@intel.com>, igt-dev@lists.freedesktop.org
Cc: mohammed.thasleem@intel.com, Jeevan B <jeevan.b@intel.com>
Subject: Re: [PATCH i-g-t v2 4/4] tests/intel/kms_pm_dc: Add new test for dc3co framedrop validation
Date: Tue, 14 Apr 2026 13:53:48 +0300 [thread overview]
Message-ID: <921579195a570e697199b80642d50a4d279c0d2f@intel.com> (raw)
In-Reply-To: <20260414095014.55950-5-jeevan.b@intel.com>
On Tue, 14 Apr 2026, Jeevan B <jeevan.b@intel.com> wrote:
> Add a new subtest to validate that no frame drops occur during
> DC3CO entry, ensuring that no frame drops are detected and DC3CO
> is successfully triggered during the test.
>
> v2: update check_dc3co_framedrop for detecting frame drops via
> drmWaitVBlank vblank sequence numbers, checks DC3CO counter
> to confirm entry and cast variable 'delay'.
>
> Signed-off-by: Jeevan B <jeevan.b@intel.com>
> ---
> tests/intel/kms_pm_dc.c | 109 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 109 insertions(+)
>
> diff --git a/tests/intel/kms_pm_dc.c b/tests/intel/kms_pm_dc.c
> index 910263c9f..ff7bc84ec 100644
> --- a/tests/intel/kms_pm_dc.c
> +++ b/tests/intel/kms_pm_dc.c
> @@ -51,6 +51,10 @@
> * Description: Make sure that system enters DC3CO when PSR2 is active and system
> * is in SLEEP state
> *
> + * SUBTEST: dc3co-framedrop-check
> + * Description: Verify that DC3CO entry does not cause frame drops and successfully
> + * enters the power state
> + *
> * SUBTEST: dc5-dpms
> * Description: Validate display engine entry to DC5 state while all connectors's
> * DPMS property set to OFF
> @@ -338,6 +342,91 @@ static void test_dc3co_vpb_simulation(data_t *data, enum psr_mode mode)
> cleanup_dc3co_fbs(data);
> }
>
> +static void setup_dc3co_for_framedrop(data_t *data, enum psr_mode mode)
> +{
> + data->op_psr_mode = mode;
> + psr_enable(data->drm_fd, data->debugfs_fd, data->op_psr_mode, NULL);
> + igt_require_f(psr_wait_entry(data->debugfs_fd, data->op_psr_mode, NULL),
> + "%s is not enabled\n",
> + mode == PSR_MODE_2 ? "PSR2" : "Panel Replay");
> +}
> +
> +static void check_dc3co_framedrop(data_t *data)
Please don't add functions named "check something". It's one of the most
ambiguous verbs you could use in a function name.
BR,
Jani.
> +{
> + igt_plane_t *primary;
> + uint32_t dc3co_prev_cnt;
> + uint32_t prev_seq = 0, cur_seq = 0, diff = 0;
> + int delay;
> + int frame_count = 0, frame_drops = 0;
> + int max_count = 60;
> + bool dc3co_flag = false;
> + drmVBlank wait;
> + igt_crtc_t *crtc = data->output->pending_crtc;
> + uint32_t vbl_flags;
> +
> + igt_require_f(data->mode->vrefresh != 0, "Invalid vrefresh rate of 0\n");
> +
> + primary = igt_output_get_plane_type(data->output, DRM_PLANE_TYPE_PRIMARY);
> + igt_plane_set_fb(primary, NULL);
> + dc3co_prev_cnt = igt_read_dc_counter(data->debugfs_fd, IGT_INTEL_CHECK_DC3CO);
> +
> + /* Calculate delay to generate idle frame in usec */
> + delay = (int)(1.5 * ((1000 * 1000) / data->mode->vrefresh));
> +
> + vbl_flags = kmstest_get_vbl_flag(crtc->pipe);
> +
> + /* Get initial vblank sequence number */
> + memset(&wait, 0, sizeof(wait));
> + wait.request.type = vbl_flags | DRM_VBLANK_RELATIVE;
> + wait.request.sequence = 1;
> + drmWaitVBlank(data->drm_fd, &wait);
> + prev_seq = wait.reply.sequence;
> +
> + while (frame_count < max_count) {
> + igt_plane_set_fb(primary, &data->fb_rgb);
> + igt_display_commit(&data->display);
> + usleep(delay);
> +
> + igt_plane_set_fb(primary, &data->fb_rgr);
> + igt_display_commit(&data->display);
> + usleep(delay);
> +
> + memset(&wait, 0, sizeof(wait));
> + wait.request.type = vbl_flags | DRM_VBLANK_RELATIVE;
> + wait.request.sequence = 1;
> + drmWaitVBlank(data->drm_fd, &wait);
> + cur_seq = wait.reply.sequence;
> +
> + diff = cur_seq - prev_seq;
> + if (diff > 1)
> + frame_drops += diff - 1;
> + prev_seq = cur_seq;
> +
> + if (!dc3co_flag &&
> + igt_read_dc_counter(data->debugfs_fd,
> + IGT_INTEL_CHECK_DC3CO) > dc3co_prev_cnt)
> + dc3co_flag = true;
> +
> + frame_count++;
> + }
> +
> + igt_assert_f(dc3co_flag, "DC3CO was not entered during the test\n");
> + igt_assert_f(frame_drops == 0,
> + "Frame drops detected: frame_drops=%d, frame_count=%d, max_count=%d, "
> + "last measured vblank diff=%u\n",
> + frame_drops, frame_count, max_count, diff);
> +}
> +
> +static void test_dc3co_framedrop(data_t *data, enum psr_mode mode)
> +{
> + igt_require_dc_counter(data->debugfs_fd, IGT_INTEL_CHECK_DC3CO);
> + setup_output(data);
> + setup_dc3co_for_framedrop(data, mode);
> + setup_videoplayback(data);
> + check_dc3co_framedrop(data);
> + cleanup_dc3co_fbs(data);
> +}
> +
> static void test_dc5_retention_flops(data_t *data, int dc_flag)
> {
> uint32_t dc_counter_before_psr;
> @@ -687,6 +776,26 @@ int igt_main()
> }
> }
>
> + igt_describe("Validate that no frame drops occur during DC3CO entry "
> + "while alternating framebuffers with PSR2 or Panel Replay active");
> + igt_subtest_with_dynamic("dc3co-framedrop-check") {
> + igt_dynamic("psr2-dc3co-framedrop") {
> + igt_require(psr_sink_support(data.drm_fd, data.debugfs_fd,
> + PSR_MODE_2, NULL));
> + igt_require_f(IS_TIGERLAKE(data.devid) ||
> + intel_display_ver(data.devid) >= 35,
> + "Platform does not support DC3CO with PSR2\n");
> + test_dc3co_framedrop(&data, PSR_MODE_2);
> + }
> + igt_dynamic("pr-dc3co-framedrop") {
> + igt_require(psr_sink_support(data.drm_fd, data.debugfs_fd,
> + PR_MODE, NULL));
> + igt_require_f(intel_display_ver(data.devid) >= 35,
> + "Platform does not support DC3CO with Panel Replay\n");
> + test_dc3co_framedrop(&data, PR_MODE);
> + }
> + }
> +
> igt_describe("This test validates display engine entry to DC5 state "
> "while PSR is active");
> igt_subtest("dc5-psr") {
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-04-14 10:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-14 9:50 [PATCH i-g-t v2 0/4] Enable and Add new tests for DC3CO Jeevan B
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 [this message]
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=921579195a570e697199b80642d50a4d279c0d2f@intel.com \
--to=jani.nikula@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