From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: Jeevan B <jeevan.b@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <karthik.b.s@intel.com>
Subject: Re: [PATCH i-g-t] tests/kms_rotation_crc: Add vblank wait for multiplane rotation synchronization
Date: Fri, 20 Feb 2026 17:16:57 +0530 [thread overview]
Message-ID: <ca27ff12-cec1-458e-82c6-311185ff40a6@intel.com> (raw)
In-Reply-To: <20260217060825.517098-1-jeevan.b@intel.com>
Hi Jeevan
I see test passing with and w/o your patch
https://intel-gfx-ci.01.org/tree/intel-xe/IGTPW_14562/shards-all.html?testfilter=multiplane-rotation
On 17-02-2026 11:38 am, Jeevan B wrote:
> Add explicit vblank wait after atomic commit in test_multi_plane_rotation()
> to ensure both planes are fully synchronized before CRC capture. This fixes
> sporadic CRC mismatches observed on CI.
>
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/issues/6946
> Signed-off-by: Jeevan B <jeevan.b@intel.com>
> ---
> tests/kms_rotation_crc.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/tests/kms_rotation_crc.c b/tests/kms_rotation_crc.c
> index 8721a8311..93e5c3e91 100644
> --- a/tests/kms_rotation_crc.c
> +++ b/tests/kms_rotation_crc.c
> @@ -1032,6 +1032,7 @@ static void test_multi_plane_rotation(data_t *data, enum pipe pipe)
> continue;
>
> igt_display_commit_atomic(display, DRM_MODE_ATOMIC_ALLOW_MODESET, NULL);
> + igt_wait_for_vblank(crtc);
> fliphw = kmstest_get_vblank(data->gfx_fd,
> crtc->pipe,
> 0) + 1;
next prev parent reply other threads:[~2026-02-20 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-17 6:08 [PATCH i-g-t] tests/kms_rotation_crc: Add vblank wait for multiplane rotation synchronization Jeevan B
2026-02-17 15:04 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-02-17 15:21 ` ✓ i915.CI.BAT: " Patchwork
2026-02-17 18:52 ` ✓ Xe.CI.FULL: " Patchwork
2026-02-20 11:46 ` Sharma, Swati2 [this message]
2026-03-23 3:23 ` [PATCH i-g-t] " B, Jeevan
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=ca27ff12-cec1-458e-82c6-311185ff40a6@intel.com \
--to=swati2.sharma@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jeevan.b@intel.com \
--cc=karthik.b.s@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