public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Anshuamn Gupta <anshuman.gupta@intel.com>
To: Imre Deak <imre.deak@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/i915_pm_dc: Increase timeout and poll interval
Date: Wed, 13 Nov 2019 16:05:18 +0530	[thread overview]
Message-ID: <20191113103516.GA17487@intel.com> (raw)
In-Reply-To: <20191023191002.8220-1-imre.deak@intel.com>

On 2019-10-23 at 22:10:02 +0300, Imre Deak wrote:
> The eDP panel power cycle delay prevents DC entry after a full modeset,
> which makes the test fail on some panels. Let's increase the timeout to
> take into account that delay (atm in the worst case the power cycle
> delay is 3 seconds) and also increase the polling interval to give more
> time for the device to enter a low power state.
IMHO how about exposing the panel_power_cycle_delay delay too in i915_panel_timings
attribute which can used by the igt to wait for time which is required.
It can save some time for IGT ?
i915_panel_timings has already exposing the other panel timings for debug purpose. 
> 
> Cc: Anshuman Gupta <anshuman.gupta@intel.com>
> Signed-off-by: Imre Deak <imre.deak@intel.com>
> ---
>  tests/i915/i915_pm_dc.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tests/i915/i915_pm_dc.c b/tests/i915/i915_pm_dc.c
> index ce3319b7..ef96a86e 100644
> --- a/tests/i915/i915_pm_dc.c
> +++ b/tests/i915/i915_pm_dc.c
> @@ -153,7 +153,7 @@ static uint32_t read_dc_counter(uint32_t drm_fd, int dc_flag)
>  static bool dc_state_wait_entry(int drm_fd, int dc_flag, int prev_dc_count)
>  {
>  	return igt_wait(read_dc_counter(drm_fd, dc_flag) >
> -			prev_dc_count, 3000, 100);
> +			prev_dc_count, 6000, 1000);
>  }
>  
>  static void check_dc_counter(int drm_fd, int dc_flag, uint32_t prev_dc_count)
> -- 
> 2.17.1
> 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  parent reply	other threads:[~2019-11-13 10:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 19:10 [igt-dev] [PATCH i-g-t] tests/i915_pm_dc: Increase timeout and poll interval Imre Deak
2019-10-23 20:45 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-10-24 15:27 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-11-13 10:35 ` Anshuamn Gupta [this message]
2019-11-13 12:33   ` [igt-dev] [PATCH i-g-t] " Imre Deak

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=20191113103516.GA17487@intel.com \
    --to=anshuman.gupta@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=imre.deak@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