From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 4/4] tests/kms_invalid_mode: Allow the test on !i915
Date: Fri, 15 Nov 2019 15:15:20 +0200 [thread overview]
Message-ID: <20191115131520.9872-4-ville.syrjala@linux.intel.com> (raw)
In-Reply-To: <20191115131520.9872-1-ville.syrjala@linux.intel.com>
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
The only i915 specific subtests 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/kms_invalid_mode.c | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/tests/kms_invalid_mode.c b/tests/kms_invalid_mode.c
index 9b94b9face4a..6de70a1485ad 100644
--- a/tests/kms_invalid_mode.c
+++ b/tests/kms_invalid_mode.c
@@ -174,6 +174,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);
@@ -223,7 +226,7 @@ igt_main
igt_fixture {
igt_skip_on_simulation();
- data.drm_fd = drm_open_driver_master(DRIVER_INTEL);
+ data.drm_fd = drm_open_driver_master(DRIVER_ANY);
igt_require_intel(data.drm_fd);
kmstest_set_vt_graphics_mode();
--
2.23.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-11-15 13:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-15 13:15 [igt-dev] [PATCH i-g-t 1/4] tests/kms_invalid_dotclock: Rename to kms_invalid_mode Ville Syrjala
2019-11-15 13:15 ` [igt-dev] [PATCH i-g-t 2/4] tests/kms_invalid_mode: Convert the max dotclock test into a subtest Ville Syrjala
2019-11-15 13:15 ` [igt-dev] [PATCH i-g-t 3/4] tests/kms_invalid_mode: Test various bogus timings Ville Syrjala
2019-11-15 13:15 ` Ville Syrjala [this message]
2019-11-15 13:41 ` [igt-dev] ✗ GitLab.Pipeline: failure for series starting with [i-g-t,1/4] tests/kms_invalid_dotclock: Rename to kms_invalid_mode Patchwork
2019-11-15 13:52 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2019-11-16 21:26 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20191115131520.9872-4-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox