From: Sowmiya S <sowmiya.s@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: suraj.kandpal@intel.com, swati2.sharma@intel.com,
Sowmiya S <sowmiya.s@intel.com>
Subject: [PATCH i-g-t v5 3/6] tests/kms_writeback: Add intel check for vendor-specific restriction
Date: Thu, 8 Jan 2026 21:18:14 +0530 [thread overview]
Message-ID: <20260108154817.48665-4-sowmiya.s@intel.com> (raw)
In-Reply-To: <20260108154817.48665-1-sowmiya.s@intel.com>
Add intel checks for vendor specific restriction.
Disallow empty FB as writeback FB only for Intel.
v4: Restore drm_fd added in struct and access it from
igt_display_t struct (Suraj)
v5: Revise commit message and subject with detailed
explanation. (Suraj)
Signed-off-by: Sowmiya S <sowmiya.s@intel.com>
---
tests/kms_writeback.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/tests/kms_writeback.c b/tests/kms_writeback.c
index 691774777..defe43686 100644
--- a/tests/kms_writeback.c
+++ b/tests/kms_writeback.c
@@ -291,7 +291,7 @@ static void writeback_fb_id(igt_output_t *output, igt_fb_t *valid_fb, igt_fb_t *
/* Zero WRITEBACK_FB_ID */
ret = do_writeback_test(output, 0, NULL, false);
- igt_assert_eq(ret, 0);
+ igt_assert_eq(ret, is_intel_device(output->display->drm_fd) ? -EINVAL : 0);
/* Valid output buffer */
ret = do_writeback_test(output, valid_fb->fb_id, NULL, false);
@@ -406,7 +406,8 @@ static void writeback_check_output(igt_output_t *output, igt_plane_t *plane,
/* Two commits, the second with no writeback */
out_fbs[0] = output_fb;
- writeback_sequence(output, plane, input_fb, out_fbs, 2, fourcc_color);
+ if (!is_intel_device(output->display->drm_fd))
+ writeback_sequence(output, plane, input_fb, out_fbs, 2, fourcc_color);
/* Two commits, both with writeback */
out_fbs[1] = output_fb;
--
2.43.0
next prev parent reply other threads:[~2026-01-08 15:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 15:48 [PATCH i-g-t v5 0/6] Add writeback changes for intel-supported formats Sowmiya S
2026-01-08 15:48 ` [PATCH i-g-t v5 1/6] tests/kms_writeback: Add support for intel-specific formats Sowmiya S
2026-01-08 15:48 ` [PATCH i-g-t v5 2/6] lib/igt_fb: Validate supported formats for crc calculation Sowmiya S
2026-01-08 15:48 ` Sowmiya S [this message]
2026-01-09 3:32 ` [PATCH i-g-t v5 3/6] tests/kms_writeback: Add intel check for vendor-specific restriction Kandpal, Suraj
2026-01-08 15:48 ` [PATCH i-g-t v5 4/6] tests/kms_writeback: Refactor format handling in commit_and_dump_fb Sowmiya S
2026-01-09 3:35 ` Kandpal, Suraj
2026-01-08 15:48 ` [PATCH i-g-t v5 5/6] tests/kms_writeback: Refactor writeback-fb-id subtest Sowmiya S
2026-01-08 15:48 ` [PATCH i-g-t v5 6/6] tests/kms_writeback: Refactor writeback-check-output subtest Sowmiya S
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=20260108154817.48665-4-sowmiya.s@intel.com \
--to=sowmiya.s@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=suraj.kandpal@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