public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: "Thasleem, Mohammed" <mohammed.thasleem@intel.com>
To: "Michał Grzelak" <michal.grzelak@intel.com>,
	igt-dev@lists.freedesktop.org
Cc: <swati2.sharma@intel.com>
Subject: Re: [PATCH i-g-t v5 2/4] tests/kms_flip: run suspend tests on one pipe per output
Date: Mon, 23 Feb 2026 16:56:14 +0530	[thread overview]
Message-ID: <2d2c0781-b767-4d09-9770-01b4028328ed@intel.com> (raw)
In-Reply-To: <20260213084930.252273-3-michal.grzelak@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]


On 13-02-2026 02:19 pm, Michał Grzelak wrote:
> It is not necessary to test suspend on same output but different pipe.
> In case of suspend tests, limit number of dynamic subtests run per
> output when any pipe has already been tested.
>
> Signed-off-by: Michał Grzelak<michal.grzelak@intel.com>

LGTM.

Reviewed-by: Mohammed Thasleem <mohammed.thasleem@intel.com>


> ---
>   tests/kms_flip.c | 8 ++++++++
>   1 file changed, 8 insertions(+)
>
> diff --git a/tests/kms_flip.c b/tests/kms_flip.c
> index 8bda82627..d09813f02 100755
> --- a/tests/kms_flip.c
> +++ b/tests/kms_flip.c
> @@ -1844,6 +1844,10 @@ static void run_test(int duration, int flags)
>   			    n != 0 && n != (resources->count_crtcs - 1))
>   				continue;
>   
> +			/* Limit the execution to 1 CRTC (first) for suspend tests */
> +			if ((flags & TEST_SUSPEND) && !all_crtcs && n != 0)
> +				continue;
> +
>   			memset(&o, 0, sizeof(o));
>   			o.count = 1;
>   			o._connector[0] = resources->connectors[i];
> @@ -1876,6 +1880,10 @@ static void run_test(int duration, int flags)
>   			    n != 0 && n != (resources->count_crtcs - 1))
>   				continue;
>   
> +			/* Limit the execution to 1 CRTC (first) for suspend tests */
> +			if ((flags & TEST_SUSPEND) && !all_crtcs && n != 0)
> +				continue;
> +
>   			memset(&o, 0, sizeof(o));
>   			o.count = 1;
>   			o._connector[0] = resources->connectors[i];

[-- Attachment #2: Type: text/html, Size: 37328 bytes --]

  reply	other threads:[~2026-02-23 11:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-13  8:49 [PATCH i-g-t v5 0/4] kms_flip: limit number of subtests run Michał Grzelak
2026-02-13  8:49 ` [PATCH i-g-t v5 1/4] tests/kms_flip: test suspend on one pair of pipes Michał Grzelak
2026-02-23 11:16   ` Thasleem, Mohammed
2026-02-13  8:49 ` [PATCH i-g-t v5 2/4] tests/kms_flip: run suspend tests on one pipe per output Michał Grzelak
2026-02-23 11:26   ` Thasleem, Mohammed [this message]
2026-02-13  8:49 ` [PATCH i-g-t v5 3/4] tests/kms_flip: limit output pairs when testing suspend Michał Grzelak
2026-02-23 15:25   ` Thasleem, Mohammed
2026-02-13  8:49 ` [PATCH i-g-t v5 4/4] tests/kms_flip: limit number of outputs wrt suspend Michał Grzelak
2026-02-23 17:24   ` Thasleem, Mohammed
2026-02-13 10:57 ` ✓ Xe.CI.BAT: success for kms_flip: limit number of subtests run (rev4) Patchwork
2026-02-13 11:14 ` ✗ i915.CI.BAT: failure " Patchwork
2026-02-14  7:05 ` ✗ Xe.CI.FULL: " Patchwork
2026-02-16  8:21 ` ✓ Xe.CI.BAT: success for kms_flip: limit number of subtests run (rev5) Patchwork
2026-02-16  8:43 ` ✓ i915.CI.BAT: " Patchwork
2026-02-16  9:20 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-16 10:44   ` Michał Grzelak
2026-02-16 10:29 ` ✗ i915.CI.Full: " Patchwork
2026-02-16 10:56   ` Michał Grzelak

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=2d2c0781-b767-4d09-9770-01b4028328ed@intel.com \
    --to=mohammed.thasleem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --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