Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 3/4] tests/kms_plane_lowres: Only test i915 features on i915
Date: Tue, 13 Nov 2018 10:23:49 -0500	[thread overview]
Message-ID: <20181113152350.23864-3-nicholas.kazlauskas@amd.com> (raw)
In-Reply-To: <20181113152350.23864-1-nicholas.kazlauskas@amd.com>

These subtests fail on non-i915 hardware because of the devid lookups
and tiling format requirements.

This patch guards the devid/gen checks for i915 only. It also skips
tests that are testing the i915 tiling formats for non i915 drivers.

The tests still won't fully run yet because they'll skip during calls to
igt_assert_plane_visible - those require an i915 extension to get the
CRTC for a pipe.

Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
---
 tests/kms_plane_lowres.c | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/tests/kms_plane_lowres.c b/tests/kms_plane_lowres.c
index 0824ef8f..3a89f341 100644
--- a/tests/kms_plane_lowres.c
+++ b/tests/kms_plane_lowres.c
@@ -251,11 +251,14 @@ static void
 test_plane_position(data_t *data, enum pipe pipe, uint64_t modifier)
 {
 	igt_output_t *output;
-	const int gen = intel_gen(intel_get_drm_devid(data->drm_fd));
 
-	if (modifier == LOCAL_I915_FORMAT_MOD_Y_TILED ||
-	    modifier == LOCAL_I915_FORMAT_MOD_Yf_TILED)
-		igt_skip_on(gen < 9);
+	if (is_i915_device(data->drm_fd)) {
+		if (modifier == LOCAL_I915_FORMAT_MOD_Y_TILED ||
+		    modifier == LOCAL_I915_FORMAT_MOD_Yf_TILED)
+			igt_skip_on(intel_gen(intel_get_drm_devid(data->drm_fd)) < 9);
+	} else {
+		igt_skip_on(modifier != LOCAL_DRM_FORMAT_MOD_NONE);
+	}
 
 	for_each_valid_output_on_pipe(&data->display, pipe, output)
 		test_plane_position_with_output(data, pipe, output, modifier);
-- 
2.17.1

_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2018-11-13 15:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-13 15:23 [igt-dev] [PATCH i-g-t 1/4] tests/kms_plane_scaling: Add support for testing AMDGPU Nicholas Kazlauskas
2018-11-13 15:23 ` [igt-dev] [PATCH i-g-t 2/4] tests/kms_plane_multiple: Add tiled-none plane position subtests Nicholas Kazlauskas
2018-11-13 16:58   ` Ville Syrjälä
2018-11-13 17:02     ` Kazlauskas, Nicholas
2018-11-13 17:15       ` Ville Syrjälä
2018-11-27 18:36         ` Kazlauskas, Nicholas
2018-11-27 19:00           ` Ville Syrjälä
2018-11-13 15:23 ` Nicholas Kazlauskas [this message]
2018-11-13 17:00   ` [igt-dev] [PATCH i-g-t 3/4] tests/kms_plane_lowres: Only test i915 features on i915 Ville Syrjälä
2018-11-13 15:23 ` [igt-dev] [PATCH i-g-t 4/4] tests: Enable plane tests for AMDGPU Nicholas Kazlauskas
2018-11-13 16:15 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/4] tests/kms_plane_scaling: Add support for testing AMDGPU Patchwork
2018-11-13 16:57 ` [igt-dev] [PATCH i-g-t 1/4] " Ville Syrjälä
2018-11-13 17:00   ` Kazlauskas, Nicholas
2018-11-13 17:08     ` Ville Syrjälä
2018-11-13 19:51 ` [igt-dev] ✗ Fi.CI.IGT: failure for series starting with [i-g-t,1/4] " 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=20181113152350.23864-3-nicholas.kazlauskas@amd.com \
    --to=nicholas.kazlauskas@amd.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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