Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Michał Grzelak" <michal.grzelak@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: karthik.b.s@intel.com, swati2.sharma@intel.com,
	juhapekka.heikkila@gmail.com, michal.grzelak@intel.com,
	"Michał Grzelak" <michal.grzelak@linux.intel.com>
Subject: [PATCH i-g-t v6 2/7] tests/kms_async_flips: limit #crtcs tested during suspend
Date: Thu, 24 Sep 2026 09:50:14 +0200	[thread overview]
Message-ID: <20260924075019.4151374-3-michal.grzelak@linux.intel.com> (raw)
In-Reply-To: <20260924075019.4151374-1-michal.grzelak@linux.intel.com>

Increase tests' performance by testing only 2 CRTCs by default.

Currently first and last CRTC coincide with first and last pipe. In
future this is likely to change due to pipe reordering. It should not
affect the test overall since the aim is to pick two arbitrary CRTCs.

v5->v6
- describe how pipe reordering affects the test (Jani)

v3->v4
- use crtc instead of display->crtcs (Mohammed)
- use proper logic operator (Mohammed)

v2->v3
- add missing S-O-B

Signed-off-by: Michał Grzelak <michal.grzelak@linux.intel.com>
---
 tests/kms_async_flips.c | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/tests/kms_async_flips.c b/tests/kms_async_flips.c
index 8884efd8ba..f373dfcd95 100644
--- a/tests/kms_async_flips.c
+++ b/tests/kms_async_flips.c
@@ -873,6 +873,7 @@ static void run_test(data_t *data, void (*test)(data_t *))
 {
 	igt_crtc_t *crtc;
 	igt_display_t *display = &data->display;
+	int idx;
 
 	if (data->atomic_path)
 		require_atomic_async_cap(data);
@@ -885,6 +886,10 @@ static void run_test(data_t *data, void (*test)(data_t *))
 			data->crtc = crtc;
 			igt_display_reset(display);
 
+			idx = crtc->crtc_index;
+			if (data->suspend_resume && idx != 0 && idx != display->n_crtcs - 1)
+				continue;
+
 			igt_output_set_crtc(data->output,
 					    crtc);
 			if (!intel_pipe_output_combo_valid(display))
-- 
2.45.2


  parent reply	other threads:[~2026-09-24  7:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-24  7:50 [PATCH i-g-t v6 0/7] tests: limiting suspend tests Michał Grzelak
2026-09-24  7:50 ` [PATCH i-g-t v6 1/7] tests/kms_async_flips: split outer test loop into two Michał Grzelak
2026-09-24  7:50 ` Michał Grzelak [this message]
2026-09-24  7:50 ` [PATCH i-g-t v6 3/7] tests/kms_vblank: limit #outputs tested during suspend Michał Grzelak
2026-09-24  7:50 ` [PATCH i-g-t v6 4/7] tests/intel/kms_ccs: split outer test loop into two Michał Grzelak
2026-09-24  7:50 ` [PATCH i-g-t v6 5/7] tests/intel/kms_ccs: limit #outputs tested during suspend Michał Grzelak
2026-09-24  7:50 ` [PATCH i-g-t v6 6/7] tests/intel/kms_ccs: limit #crtcs " Michał Grzelak
2026-09-29  9:16   ` Juha-Pekka Heikkilä
2026-09-24  7:50 ` [PATCH i-g-t v6 7/7] tests/kms_hdr: run on 3 outputs when testing suspend Michał Grzelak
2026-09-24  9:14 ` ✓ i915.CI.BAT: success for tests: limiting suspend tests (rev5) Patchwork
2026-09-24  9:48 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-24 23:05 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-09-25  7:34 ` ✓ i915.CI.Full: success " 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=20260924075019.4151374-3-michal.grzelak@linux.intel.com \
    --to=michal.grzelak@linux.intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=juhapekka.heikkila@gmail.com \
    --cc=karthik.b.s@intel.com \
    --cc=michal.grzelak@intel.com \
    --cc=swati2.sharma@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