From: "Naladala, Ramanaidu" <Ramanaidu.naladala@intel.com>
To: Jeevan B <jeevan.b@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <animesh.manna@intel.com>,
<dibin.moolakadan.subrahmanian@intel.com>,
<mohammed.thasleem@intel.com>
Subject: Re: [PATCH i-g-t v4 7/7] tests/intel/kms_pm_dc: Add dc3co-vpb-framegap subtest
Date: Wed, 13 May 2026 13:36:48 +0530 [thread overview]
Message-ID: <d086c5dd-bd9b-419f-ba97-5ddc857a627f@intel.com> (raw)
In-Reply-To: <20260511171820.461666-8-jeevan.b@intel.com>
Hi Jeevan,
On 5/11/2026 10:48 PM, Jeevan B wrote:
> Add a new subtest to validate DC3CO counter increments across
> frame gaps exceeding the threshold during a video-like workload
> with PSR2 enabled.
>
> Signed-off-by: Jeevan B <jeevan.b@intel.com>
> ---
> tests/intel/kms_pm_dc.c | 69 +++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 69 insertions(+)
>
> diff --git a/tests/intel/kms_pm_dc.c b/tests/intel/kms_pm_dc.c
> index 6d2bd0ee1..b8d903fd5 100644
> --- a/tests/intel/kms_pm_dc.c
> +++ b/tests/intel/kms_pm_dc.c
> @@ -60,6 +60,10 @@
> * exit cycle, ensuring DC3CO is not broken by deeper power state
> * transitions.
> *
> + * SUBTEST: dc3co-vpb-framegap
> + * Description: Validate DC3CO counter increments before and after a delay greater
> + * than 6 frame gaps during video-like load with PSR2 active.
> + *
> * SUBTEST: dc5-dpms
> * Description: Validate display engine entry to DC5 state while all connectors's
> * DPMS property set to OFF
> @@ -433,6 +437,63 @@ static void test_dc3co_framedrop(data_t *data, enum psr_mode mode)
> cleanup_dc3co_fbs(data);
> }
>
> +static void check_dc3co_with_framegap_load(data_t *data)
> +{
> + igt_plane_t *primary;
> + uint32_t dc3co_cnt_before, dc3co_cnt_after_gap;
> + int delay, long_gap_us;
> + time_t secs = 3;
> + time_t start_time;
> +
> + primary = igt_output_get_plane_type(data->output, DRM_PLANE_TYPE_PRIMARY);
> + igt_plane_set_fb(primary, NULL);
> +
> + delay = 1.5 * ((1000 * 1000) / data->mode->vrefresh);
> +
> + dc3co_cnt_before = igt_read_dc_counter(data->debugfs_fd,
> + IGT_INTEL_CHECK_DC3CO);
> + start_time = time(NULL);
> + while (time(NULL) - start_time < secs) {
> + 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);
> + }
Imho, instead of using loops and delay calculations use
igt_wait_for_vblank_count() helper to delay required number of frames.
> +
> + assert_dc_counter(data, IGT_INTEL_CHECK_DC3CO, dc3co_cnt_before);
> +
> + long_gap_us = 7 * ((1000 * 1000) / data->mode->vrefresh);
> + usleep(long_gap_us);
> +
> + dc3co_cnt_after_gap = igt_read_dc_counter(data->debugfs_fd,
> + IGT_INTEL_CHECK_DC3CO);
> + start_time = time(NULL);
> + while (time(NULL) - start_time < secs) {
> + 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);
> + }
> +
> + assert_dc_counter(data, IGT_INTEL_CHECK_DC3CO, dc3co_cnt_after_gap);
> +}
> +
> +static void test_dc3co_vpb_framegap(data_t *data)
> +{
> + igt_require_dc_counter(data->debugfs_fd, IGT_INTEL_CHECK_DC3CO);
> + setup_output(data);
> + setup_dc3co(data, PSR_MODE_2);
> + setup_videoplayback(data);
> + check_dc3co_with_framegap_load(data);
> + cleanup_dc3co_fbs(data);
> +}
> +
> static void test_dc5_retention_flops(data_t *data, int dc_flag)
> {
> uint32_t dc_counter_before_psr;
> @@ -864,6 +925,14 @@ int igt_main()
> }
> }
>
> + igt_describe("Validate DC3CO counter increments before and after a delay "
> + "greater than 6 frame gaps during video-like load with PSR2 active");
> + igt_subtest("dc3co-vpb-framegap") {
> + igt_require(psr_sink_support(data.drm_fd, data.debugfs_fd,
> + PSR_MODE_2, NULL));
> + test_dc3co_vpb_framegap(&data);
> + }
> +
> igt_describe("This test validates display engine entry to DC5 state "
> "while PSR is active");
> igt_subtest("dc5-psr") {
next prev parent reply other threads:[~2026-05-13 8:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 17:18 [PATCH i-g-t v4 0/7] Enable and Add new tests for DC3CO Jeevan B
2026-05-11 17:18 ` [PATCH i-g-t v4 1/7] tests: s/check_dc_counter/assert_dc_counter Jeevan B
2026-05-11 17:18 ` [PATCH i-g-t v4 2/7] tests/intel/kms_pm_dc: Replace require with proper assertion Jeevan B
2026-05-11 17:18 ` [PATCH i-g-t v4 3/7] tests/intel/kms_pm_dc: Enable DC3CO test for PSR2/PR modes Jeevan B
2026-05-12 6:18 ` Naladala, Ramanaidu
2026-05-11 17:18 ` [PATCH i-g-t v4 4/7] tests/kms_vrr: Add new test for DC3CO validation with LOBF Jeevan B
2026-05-13 6:11 ` Naladala, Ramanaidu
2026-05-11 17:18 ` [PATCH i-g-t v4 5/7] tests/intel/kms_pm_dc: Add new test for dc3co framedrop validation Jeevan B
2026-05-11 17:18 ` [PATCH i-g-t v4 6/7] tests/intel/kms_pm_dc: Add new test for DC3CO recovery after DC6 Jeevan B
2026-05-13 8:27 ` Naladala, Ramanaidu
2026-05-11 17:18 ` [PATCH i-g-t v4 7/7] tests/intel/kms_pm_dc: Add dc3co-vpb-framegap subtest Jeevan B
2026-05-13 8:06 ` Naladala, Ramanaidu [this message]
2026-05-15 15:29 ` B, Jeevan
2026-05-12 4:32 ` ✓ i915.CI.BAT: success for Enable and Add new tests for DC3CO (rev5) Patchwork
2026-05-12 5:58 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-12 12:07 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-12 18:14 ` ✗ 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=d086c5dd-bd9b-419f-ba97-5ddc857a627f@intel.com \
--to=ramanaidu.naladala@intel.com \
--cc=animesh.manna@intel.com \
--cc=dibin.moolakadan.subrahmanian@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