From: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
To: igt-dev@lists.freedesktop.org
Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Subject: [igt-dev] [PATCH i-g-t] PSR: Bump wait for active timeout to 2.5s
Date: Tue, 11 Dec 2018 17:16:08 +0100 [thread overview]
Message-ID: <20181211161608.7345-1-maarten.lankhorst@linux.intel.com> (raw)
Typically PSR enables in around 136 ms, but when enabling 2
screens, 500 ms is not enough on icelake sometimes, so bump
it a bit higher.
On kms_frontbuffer_tracking:
Starting subtest: psr-2p-scndscrn-shrfb-plflip-blt
psr_active(debugfs_fd, true) took 136ms
psr_active(debugfs_fd, true) took 136ms
psr_active(debugfs_fd, true) took 350ms
psr_active(debugfs_fd, true) took 136ms
psr_active(debugfs_fd, true) took 1598ms
Cc: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
Cc: José Roberto de Souza <jose.souza@intel.com>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=108733
---
lib/igt_psr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lib/igt_psr.c b/lib/igt_psr.c
index 0ddfb64f0e72..265521217a2d 100644
--- a/lib/igt_psr.c
+++ b/lib/igt_psr.c
@@ -39,7 +39,7 @@ static bool psr_active(int debugfs_fd, bool check_active)
bool psr_wait_entry(int debugfs_fd)
{
- return igt_wait(psr_active(debugfs_fd, true), 500, 20);
+ return igt_wait(psr_active(debugfs_fd, true), 2500, 20);
}
bool psr_wait_exit(int debugfs_fd)
--
2.19.2
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2018-12-11 16:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-11 16:16 Maarten Lankhorst [this message]
2018-12-11 16:48 ` [igt-dev] ✓ Fi.CI.BAT: success for PSR: Bump wait for active timeout to 2.5s Patchwork
2018-12-11 17:40 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-12-11 21:27 ` [igt-dev] [PATCH i-g-t] " Dhinakaran Pandiyan
2018-12-12 14:37 ` Maarten Lankhorst
2018-12-12 15:11 ` Chris Wilson
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=20181211161608.7345-1-maarten.lankhorst@linux.intel.com \
--to=maarten.lankhorst@linux.intel.com \
--cc=dhinakaran.pandiyan@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