public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Dhinakaran Pandiyan <dhinakaran.pandiyan@intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] PSR: Bump wait for active timeout to 2.5s
Date: Tue, 11 Dec 2018 13:27:04 -0800	[thread overview]
Message-ID: <10f881c3d24970952303b1a68e8b20969fedeb63.camel@intel.com> (raw)
In-Reply-To: <20181211161608.7345-1-maarten.lankhorst@linux.intel.com>

On Tue, 2018-12-11 at 17:16 +0100, Maarten Lankhorst wrote:
> 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

We have to find out why it took that long, ~96 frames exceeds the idle
frame limit we set in the driver. I'm concerned we might be covering up
a bug by increasing the limit so high.

-DK

> 
> 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)

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

  parent reply	other threads:[~2018-12-11 21:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-11 16:16 [igt-dev] [PATCH i-g-t] PSR: Bump wait for active timeout to 2.5s Maarten Lankhorst
2018-12-11 16:48 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2018-12-11 17:40 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2018-12-11 21:27 ` Dhinakaran Pandiyan [this message]
2018-12-12 14:37   ` [igt-dev] [PATCH i-g-t] " 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=10f881c3d24970952303b1a68e8b20969fedeb63.camel@intel.com \
    --to=dhinakaran.pandiyan@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=maarten.lankhorst@linux.intel.com \
    /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