From: "Michał Grzelak" <michal.grzelak@intel.com>
To: Alex Hung <alex.hung@amd.com>
Cc: igt-dev@lists.freedesktop.org, sunpeng.li@amd.com,
Ethan.Cheung@amd.com, swati2.sharma@intel.com
Subject: Re: [PATCH] tests/kms_flip: Fix regression on non-Intel devices in event_loop
Date: Fri, 10 Apr 2026 10:17:25 +0200 (CEST) [thread overview]
Message-ID: <df5f7fb5-77dd-3735-f834-1c2734ea5fcc@intel.com> (raw)
In-Reply-To: <20260409232807.631457-1-alex.hung@amd.com>
[-- Attachment #1: Type: text/plain, Size: 1398 bytes --]
Hi Alex,
On Thu, 9 Apr 2026, Alex Hung wrote:
> Guard the device-id query with is_intel_device() so the "wa" flag is
> only computed on Intel hardware, restoring the pre-regression behavior
> for all other drivers.
>
> This fixes the following regression:
>
> (kms_flip:15463) intel_chipset-CRITICAL: Test assertion failure function intel_get_drm_devid, file ../lib/intel_chipset.c:145:
> (kms_flip:15463) intel_chipset-CRITICAL: Failed assertion: is_intel_device(fd)
>
> Fixes: 2a9f1c1ae ("tests/kms_flip: test suspend at most twice on SNB && BMG")
> Signed-off-by: Alex Hung <alex.hung@amd.com>
Looks good to me.
Reviewed-by: Michał Grzelak <michal.grzelak@intel.com>
BR,
Michał
> ---
> tests/kms_flip.c | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/tests/kms_flip.c b/tests/kms_flip.c
> index 81fa8dd5c..1ef9492ba 100755
> --- a/tests/kms_flip.c
> +++ b/tests/kms_flip.c
> @@ -1327,11 +1327,12 @@ static bool event_loop(struct test_output *o, unsigned duration_ms,
> unsigned long start, end;
> uint32_t devid;
> int count = 0;
> - bool wa;
> + bool wa = false;
>
> - devid = intel_get_drm_devid(drm_fd);
> -
> - wa = IS_SANDYBRIDGE(devid) || IS_BATTLEMAGE(devid);
> + if (is_intel_device(drm_fd)) {
> + devid = intel_get_drm_devid(drm_fd);
> + wa = IS_SANDYBRIDGE(devid) || IS_BATTLEMAGE(devid);
> + }
>
> start = gettime_us();
>
> --
> 2.43.0
>
>
next prev parent reply other threads:[~2026-04-10 8:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 23:28 [PATCH] tests/kms_flip: Fix regression on non-Intel devices in event_loop Alex Hung
2026-04-10 4:52 ` ✓ i915.CI.BAT: success for " Patchwork
2026-04-10 4:57 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-10 8:17 ` Michał Grzelak [this message]
2026-04-10 11:23 ` ✓ Xe.CI.FULL: " Patchwork
2026-04-10 11:44 ` [PATCH] " Kamil Konieczny
2026-04-11 1:23 ` ✗ i915.CI.Full: failure for " 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=df5f7fb5-77dd-3735-f834-1c2734ea5fcc@intel.com \
--to=michal.grzelak@intel.com \
--cc=Ethan.Cheung@amd.com \
--cc=alex.hung@amd.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=sunpeng.li@amd.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