Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Hung <alex.hung@amd.com>
To: <igt-dev@lists.freedesktop.org>
Cc: <rodrigo.siqueira@amd.com>, <harry.wentland@amd.com>,
	<hersenxs.wu@amd.com>, Alex Hung <alex.hung@amd.com>
Subject: [PATCH] tests/kms: Skip amdgpu's writeback connectors on panning tests
Date: Wed, 20 Mar 2024 20:06:46 -0600	[thread overview]
Message-ID: <20240321020646.844372-1-alex.hung@amd.com> (raw)

With commit ff1d9a601 writeback connector will be enabled. The
AMDGPU writeback connector is to be skipped.

Signed-off-by: Alex Hung <alex.hung@amd.com>
---
 tests/kms_plane.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/tests/kms_plane.c b/tests/kms_plane.c
index 406aecc04..d76b3a8f5 100644
--- a/tests/kms_plane.c
+++ b/tests/kms_plane.c
@@ -482,6 +482,12 @@ test_plane_panning(data_t *data, enum pipe pipe)
 		drmModeModeInfo *m = &output->config.connector->modes[j__];
 		uint32_t fb_size = m->hdisplay * m->vdisplay * 4;
 
+		if (output->config.connector->connector_type == DRM_MODE_CONNECTOR_WRITEBACK &&
+		   is_amdgpu_device(data->drm_fd)) {
+			igt_debug("Skipping Writeback connector\n");
+			continue;
+		}
+
 		/* test allocates 2 double-dim fbs, add one more, to be safe */
 		if (mem_size && 3 * 4 * fb_size > mem_size) {
 			igt_debug("Skipping mode %s due to low memory\n", m->name);
-- 
2.34.1


             reply	other threads:[~2024-03-21  2:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-21  2:06 Alex Hung [this message]
2024-03-21  4:05 ` ✓ CI.xeBAT: success for tests/kms: Skip amdgpu's writeback connectors on panning tests Patchwork
2024-03-21  4:21 ` ✓ Fi.CI.BAT: " Patchwork
2024-03-21 14:00 ` [PATCH] " Harry Wentland
2024-03-22  1:18 ` ✗ Fi.CI.IGT: failure for " Patchwork
2024-03-22  6:37 ` ✓ Fi.CI.BAT: success for tests/kms: Skip amdgpu's writeback connectors on panning tests (rev2) Patchwork
2024-03-22  6:41 ` ✓ CI.xeBAT: " Patchwork
2024-03-23  7:20 ` ✗ Fi.CI.IGT: failure " 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=20240321020646.844372-1-alex.hung@amd.com \
    --to=alex.hung@amd.com \
    --cc=harry.wentland@amd.com \
    --cc=hersenxs.wu@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=rodrigo.siqueira@amd.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