From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 6/6] tests/kms_invalid_mode: Allow the test on !i915
Date: Thu, 16 Sep 2021 18:35:15 +0300 [thread overview]
Message-ID: <20210916153515.21369-6-ville.syrjala@linux.intel.com> (raw)
In-Reply-To: <20210916153515.21369-1-ville.syrjala@linux.intel.com>
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
The only i915 specific subtest is the max dotclock check,
so let's add the i915 check there and switch from DRIVER_INTEL
to DRIVER_ANY so that the other subtests can run everywhere.
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
tests/{i915 => }/kms_invalid_mode.c | 6 ++++--
tests/meson.build | 2 +-
2 files changed, 5 insertions(+), 3 deletions(-)
rename tests/{i915 => }/kms_invalid_mode.c (98%)
diff --git a/tests/i915/kms_invalid_mode.c b/tests/kms_invalid_mode.c
similarity index 98%
rename from tests/i915/kms_invalid_mode.c
rename to tests/kms_invalid_mode.c
index 722aa816fca1..8a4e824a4caa 100644
--- a/tests/i915/kms_invalid_mode.c
+++ b/tests/kms_invalid_mode.c
@@ -237,6 +237,9 @@ static int i915_max_dotclock(data_t *data)
char *s;
int max_dotclock = 0;
+ if (!is_i915_device(data->drm_fd))
+ return 0;
+
igt_debugfs_read(data->drm_fd, "i915_frequency_info", buf);
s = strstr(buf, "Max pixel clock frequency:");
igt_assert(s);
@@ -298,8 +301,7 @@ igt_main
igt_fixture {
igt_skip_on_simulation();
- data.drm_fd = drm_open_driver_master(DRIVER_INTEL);
- igt_require_intel(data.drm_fd);
+ data.drm_fd = drm_open_driver_master(DRIVER_ANY);
kmstest_set_vt_graphics_mode();
diff --git a/tests/meson.build b/tests/meson.build
index 3e3090e5d8b4..99557912adc1 100644
--- a/tests/meson.build
+++ b/tests/meson.build
@@ -33,6 +33,7 @@ test_progs = [
'kms_getfb',
'kms_hdmi_inject',
'kms_hdr',
+ 'kms_invalid_mode',
'kms_lease',
'kms_multipipe_modeset',
'kms_panel_fitting',
@@ -228,7 +229,6 @@ i915_progs = [
'kms_flip_scaled_crc',
'kms_flip_tiling',
'kms_frontbuffer_tracking',
- 'kms_invalid_mode',
'kms_legacy_colorkey',
'kms_mmap_write_crc',
'kms_pipe_b_c_ivb',
--
2.32.0
next prev parent reply other threads:[~2021-09-16 15:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-16 15:35 [igt-dev] [PATCH i-g-t 1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode Ville Syrjala
2021-09-16 15:35 ` [igt-dev] [PATCH i-g-t 2/6] tests/kms_invalid_mode: Convert the max dotclock test into a subtest Ville Syrjala
2021-10-05 10:13 ` Karthik B S
2021-10-05 10:33 ` Petri Latvala
2021-10-05 10:38 ` Ville Syrjälä
2021-09-16 15:35 ` [igt-dev] [PATCH i-g-t 3/6] tests/kms_invalid_mode: Move bigjoiner handling into the proper place Ville Syrjala
2021-10-05 10:15 ` Karthik B S
2021-09-16 15:35 ` [igt-dev] [PATCH i-g-t 4/6] tests/kms_invalid_mode: Test various bogus timings Ville Syrjala
2021-10-05 10:22 ` Karthik B S
2021-09-16 15:35 ` [igt-dev] [PATCH i-g-t 5/6] tests/kms_invalid_mode: Test clock==(U)INT_MAX Ville Syrjala
2021-10-05 10:24 ` Karthik B S
2021-09-16 15:35 ` Ville Syrjala [this message]
2021-10-05 10:27 ` [igt-dev] [PATCH i-g-t 6/6] tests/kms_invalid_mode: Allow the test on !i915 Karthik B S
2021-09-16 19:05 ` [igt-dev] ✗ Fi.CI.BAT: failure for series starting with [i-g-t,1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode Patchwork
2021-09-22 17:16 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode (rev2) Patchwork
2021-09-22 19:09 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2021-10-04 12:30 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode (rev3) Patchwork
2021-10-04 14:54 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-10-05 10:09 ` [igt-dev] [PATCH i-g-t 1/6] tests/kms_invalid_dotclock: Rename to kms_invalid_mode Karthik B S
2021-10-05 11:12 ` Ville Syrjälä
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=20210916153515.21369-6-ville.syrjala@linux.intel.com \
--to=ville.syrjala@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.