From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t] lib/igt_debugfs: Add timeouts to opening pipe CRC fd.
Date: Thu, 5 Apr 2018 12:49:54 +0200 [thread overview]
Message-ID: <20180405104954.6880-1-maarten.lankhorst@linux.intel.com> (raw)
This will fix the PSR tests to fail slightly faster, since they wait
indefinitely for a CRC that never comes during open.
Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
---
lib/igt_debugfs.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lib/igt_debugfs.c b/lib/igt_debugfs.c
index 8adc02e9cc47..094df564b6f4 100644
--- a/lib/igt_debugfs.c
+++ b/lib/igt_debugfs.c
@@ -757,7 +757,10 @@ void igt_pipe_crc_start(igt_pipe_crc_t *pipe_crc)
sprintf(buf, "crtc-%d/crc/data", pipe_crc->pipe);
+ igt_set_timeout(5, "Opening crc fd, which waits for first CRC.");
pipe_crc->crc_fd = openat(pipe_crc->dir, buf, pipe_crc->flags);
+ igt_reset_timeout();
+
igt_assert(pipe_crc->crc_fd != -1);
errno = 0;
}
--
2.16.3
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2018-04-05 10:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 10:49 Maarten Lankhorst [this message]
2018-04-05 11:45 ` [igt-dev] ✗ Fi.CI.BAT: failure for lib/igt_debugfs: Add timeouts to opening pipe CRC fd Patchwork
2018-04-05 21:03 ` [igt-dev] [PATCH i-g-t] " Souza, Jose
2018-04-05 21:15 ` Chris Wilson
2018-04-05 22:10 ` Souza, Jose
2018-04-05 22:39 ` Dhinakaran Pandiyan
2018-04-06 7:33 ` Maarten Lankhorst
2018-04-06 18:27 ` Dhinakaran Pandiyan
2018-04-10 15:28 ` Maarten Lankhorst
2018-05-24 1:05 ` Dhinakaran Pandiyan
2018-05-24 6:59 ` Maarten Lankhorst
2018-04-06 18:17 ` Dhinakaran Pandiyan
2018-04-11 7:46 ` Maarten Lankhorst
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=20180405104954.6880-1-maarten.lankhorst@linux.intel.com \
--to=maarten.lankhorst@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.