Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Gupta, Anshuman" <anshuman.gupta@intel.com>
To: "Bhatt, Jigar" <jigar.bhatt@intel.com>,
	"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "Varide, Nischal" <nischal.varide@intel.com>,
	"Shankar, Uma" <uma.shankar@intel.com>,
	"Sharma, Swati2" <swati2.sharma@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t v2 2/2] tests/i915/i915_pm_dc: Fix DC9 test
Date: Wed, 22 Sep 2021 15:54:48 +0000	[thread overview]
Message-ID: <5069fdcbe7ed49c79334a431c2fd5c6b@intel.com> (raw)
In-Reply-To: <20210922055301.1853271-3-jigar.bhatt@intel.com>



> -----Original Message-----
> From: Bhatt, Jigar <jigar.bhatt@intel.com>
> Sent: Wednesday, September 22, 2021 11:23 AM
> To: igt-dev@lists.freedesktop.org
> Cc: Bhatt, Jigar <jigar.bhatt@intel.com>; Gupta, Anshuman
> <anshuman.gupta@intel.com>; Varide, Nischal <nischal.varide@intel.com>;
> Shankar, Uma <uma.shankar@intel.com>; Sharma, Swati2
> <swati2.sharma@intel.com>
> Subject: [PATCH i-g-t v2 2/2] tests/i915/i915_pm_dc: Fix DC9 test
> 
> V1:
> Currently, check_dc9 is being called with reference
> (previous) counter being read after dpms_off call.
> At this time, already the counter is 0.
> We need to read the counter before dpms_off is called so that it holds the
> previous value which had incremented while testing shallow states (DC5 or DC6).
> 
> V2:
> Bit cleaner code.[Imre]
> dump the i915_pm_runtime_status debugfs file in case of test
> failure.[Anshuman]
> 
> V3:
> Disabling the polling during DC9 test “echo 0 >
> /sys/module/drm_kms_helper/parameters/poll”.[Anshuman]
> 
> V4:
> passing right fd to igt_sysfs_get_boolean() function, moving save and get part of
> polling to setup_dc9_dpms().
> 
> Signed-off-by: Jigar Bhatt <jigar.bhatt@intel.com>
> ---
>  tests/i915/i915_pm_dc.c | 45 ++++++++++++++++++++++++++++-------------
>  1 file changed, 31 insertions(+), 14 deletions(-)
> 
> diff --git a/tests/i915/i915_pm_dc.c b/tests/i915/i915_pm_dc.c index
> 04acf839..4efe3206 100644
> --- a/tests/i915/i915_pm_dc.c
> +++ b/tests/i915/i915_pm_dc.c
> @@ -40,6 +40,7 @@
>  #define CHECK_DC3CO	(1 << 2)
> 
>  #define PWR_DOMAIN_INFO "i915_power_domain_info"
> +#define RPM_STATUS "i915_runtime_pm_status"
> 
>  typedef struct {
>  	double r, g, b;
> @@ -393,42 +394,58 @@ static bool support_dc6(int debugfs_fd)
>  	return strstr(buf, "DC5 -> DC6 count");  }
> 
> -static bool check_dc9(uint32_t debugfs_fd, int prev_dc, bool dc6_supported,
> int seconds)
> +static bool dc9_wait_entry(uint32_t debugfs_fd, int dc_target, int
> +prev_dc, int seconds)
>  {
>  	/*
>  	 * since we do not have DC9 counter,
>  	 * so we rely on dc5/dc6 counter reset to check if display engine was in
> DC9.
>  	 */
> -	return igt_wait(dc6_supported ? read_dc_counter(debugfs_fd,
> CHECK_DC6) <
> -			prev_dc : read_dc_counter(debugfs_fd, CHECK_DC5) <
> +	return igt_wait(read_dc_counter(debugfs_fd, dc_target) >
>  			prev_dc, seconds, 100);
>  }
> 
> -static void setup_dc9_dpms(data_t *data, int prev_dc, bool dc6_supported)
> +static void check_dc9(data_t *data, int dc_target, int prev_dc)
>  {
> +	igt_assert_f(dc9_wait_entry(data->debugfs_fd, dc_target, prev_dc,
> 3000),
> +			"DC9 state is not achieved\n%s:\n%s\n", RPM_STATUS,
> +			data->debugfs_dump = igt_sysfs_get(data-
> >debugfs_fd, RPM_STATUS)); }
> +
> +static bool setup_dc9_dpms(data_t *data, int dc_target, int sysfs_fd,
> +const char *kms_poll) {
> +	int prev_dc;
> +	bool buf = true;
> +
> +	if (sysfs_fd >= 0) {
> +		buf = igt_sysfs_get_boolean(sysfs_fd, kms_poll);
> +		igt_sysfs_set_boolean(sysfs_fd, kms_poll, 0);
> +	}
> +	prev_dc = read_dc_counter(data->debugfs_fd, dc_target);
>  	setup_dc_dpms(data);
>  	dpms_off(data);
> -	igt_skip_on_f(!(igt_wait(dc6_supported ? read_dc_counter(data-
> >debugfs_fd, CHECK_DC6) >
> -				prev_dc : read_dc_counter(data->debugfs_fd,
> CHECK_DC5) >
> +	igt_skip_on_f(!(igt_wait(read_dc_counter(data->debugfs_fd, dc_target)
> +>
>  				prev_dc, 3000, 100)), "Unable to enters shallow
> DC states\n");
>  	dpms_on(data);
>  	cleanup_dc_dpms(data);
> +	return buf;
>  }
> 
>  static void test_dc9_dpms(data_t *data)  {
> -	bool dc6_supported;
> +	int prev_dc, dc_target, sysfs_fd;
> +	bool buf;
> +	const char *kms_poll =
> "/sys/module/drm_kms_helper/parameters/poll";
Better to use macro for path string.
> 
> +	sysfs_fd = open(kms_poll, O_WRONLY);
Error condition need to be check for open.
>  	require_dc_counter(data->debugfs_fd, CHECK_DC5);
> -	dc6_supported = support_dc6(data->debugfs_fd);
> -	setup_dc9_dpms(data, dc6_supported ? read_dc_counter(data-
> >debugfs_fd, CHECK_DC6) :
> -			read_dc_counter(data->debugfs_fd, CHECK_DC5),
> dc6_supported);
> +	dc_target = support_dc6(data->debugfs_fd) ? CHECK_DC6 :
> CHECK_DC5;
> +	buf = setup_dc9_dpms(data, dc_target, sysfs_fd, kms_poll);
> +	prev_dc = read_dc_counter(data->debugfs_fd, dc_target);
>  	dpms_off(data);
> -	igt_assert_f(check_dc9(data->debugfs_fd, dc6_supported ?
> -				read_dc_counter(data->debugfs_fd,
> CHECK_DC6) :
> -				read_dc_counter(data->debugfs_fd,
> CHECK_DC5),
> -				dc6_supported, 3000), "Not in DC9\n");
> +	check_dc9(data, dc_target, prev_dc);
>  	dpms_on(data);
> +	if (sysfs_fd >= 0)
> +		igt_sysfs_set_boolean(sysfs_fd, kms_poll, buf);
This need to restore in an igt exit hander, when test will fail control flow will not reach here and
It will not restore the value.
Check igt_install_exit_handler().
Br,
Anshuman Gupta.

>  }
> 
>  IGT_TEST_DESCRIPTION("These tests validate Display Power DC states");
> --
> 2.25.1


  reply	other threads:[~2021-09-22 15:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22  5:52 [igt-dev] [PATCH i-g-t v2 0/2] tests/i915/i915_pm_dc: Refactoring pwr_dmn_info to debugfs_dump and fix DC9 test Jigar Bhatt
2021-09-22  5:53 ` [igt-dev] [PATCH i-g-t v2 1/2] tests/i915/i915_pm_dc: Refactoring pwr_dmn_info to debugfs_dump Jigar Bhatt
2021-09-22  5:53 ` [igt-dev] [PATCH i-g-t v2 2/2] tests/i915/i915_pm_dc: Fix DC9 test Jigar Bhatt
2021-09-22 15:54   ` Gupta, Anshuman [this message]
2021-09-23  9:06     ` Bhatt, Jigar
2021-09-22  7:17 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/i915/i915_pm_dc: Refactoring pwr_dmn_info to debugfs_dump and fix DC9 test (rev2) Patchwork
2021-09-22  8:17 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2021-09-24 10:03 [igt-dev] [PATCH i-g-t v2 0/2] tests/i915/i915_pm_dc: Refactoring pwr_dmn_info to debugfs_dump and fix DC9-dpms test Jigar Bhatt
2021-09-24 10:03 ` [igt-dev] [PATCH i-g-t v2 2/2] tests/i915/i915_pm_dc: Fix DC9 test Jigar Bhatt
2021-09-24 11:15   ` Gupta, Anshuman

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=5069fdcbe7ed49c79334a431c2fd5c6b@intel.com \
    --to=anshuman.gupta@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=jigar.bhatt@intel.com \
    --cc=nischal.varide@intel.com \
    --cc=swati2.sharma@intel.com \
    --cc=uma.shankar@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