Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: Mohammed Thasleem <mohammed.thasleem@intel.com>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/intel/kms_pm_dc: Fix dc9-dpms test on LNL
Date: Fri, 24 Nov 2023 19:02:55 +0530	[thread overview]
Message-ID: <722a1c33-d384-4f9c-8652-3d09b8dca950@intel.com> (raw)
In-Reply-To: <20231124082712.2384183-1-mohammed.thasleem@intel.com>

Hi Thasleem,

First of all, this patch is not fixing dc9-dpms test.
Rephrase your subject line.

On 24-Nov-23 1:57 PM, Mohammed Thasleem wrote:
> DC5 counter on disp ver >=14 is not expected to get reset in DC9 state.
> Add condition to check runtime_suspended_time value to validate
> DC9 dpms test.

Also, you are not adding any condition, you are just adding platform to 
existing condition.

Please fix both subject and commit message.

> 
> Signed-off-by: Mohammed Thasleem <mohammed.thasleem@intel.com>
> ---
>   lib/intel_chipset.h     | 1 +
>   tests/intel/kms_pm_dc.c | 4 ++--
>   2 files changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/lib/intel_chipset.h b/lib/intel_chipset.h
> index 1edc8e92c..3f2534519 100644
> --- a/lib/intel_chipset.h
> +++ b/lib/intel_chipset.h
> @@ -208,6 +208,7 @@ void intel_check_pch(void);
>   
>   #define IS_GEN(devid, x)	(intel_get_device_info(devid)->graphics_ver == x)
>   #define AT_LEAST_GEN(devid, x)	(intel_get_device_info(devid)->graphics_ver >= x)
> +#define AT_LEAST_DISPLAY(devid, x) (intel_get_device_info(devid)->display_ver >= x)
>   
>   #define IS_GEN2(devid)		IS_GEN(devid, 2)
>   #define IS_GEN3(devid)		IS_GEN(devid, 3)
> diff --git a/tests/intel/kms_pm_dc.c b/tests/intel/kms_pm_dc.c
> index a3c7c4018..6990f91a2 100644
> --- a/tests/intel/kms_pm_dc.c
> +++ b/tests/intel/kms_pm_dc.c
> @@ -107,7 +107,7 @@
>   #define KMS_HELPER "/sys/module/drm_kms_helper/parameters/"
>   #define PACKAGE_CSTATE_PATH  "pmc_core/package_cstate_show"
>   #define KMS_POLL_DISABLE 0
> -#define DC9_RESETS_DC_COUNTERS(devid) (!(IS_DG1(devid) || IS_DG2(devid) || IS_METEORLAKE(devid)))
> +#define DC9_RESETS_DC_COUNTERS(devid) (!(IS_DG1(devid) || IS_DG2(devid) || AT_LEAST_DISPLAY(devid, 14)))
>   
>   IGT_TEST_DESCRIPTION("Tests to validate display power DC states.");
>   
> @@ -524,7 +524,7 @@ static bool dc9_wait_entry(data_t *data, int dc_target, int prev_dc, int prev_rp
>   	 * Runtime suspended residency should increment once DC9 is achieved;
>   	 * this condition is valid for all platforms.
>   	 * However, resetting of dc5/dc6 counter to check if display engine was in DC9;
> -	 * this condition at present can be skipped for dg1, dg2 and MTL platforms.
> +	 * this condition at present can be skipped for dg1, dg2 and MTL+ platforms.
>   	 */
>   	return igt_wait((read_runtime_suspended_time(data->drm_fd) > prev_rpm) &&
>   			(!DC9_RESETS_DC_COUNTERS(data->devid) ||

  reply	other threads:[~2023-11-24 13:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-22  0:22 [igt-dev] [PATCH i-g-t] tests/intel/kms_pm_dc: Fix dc9-dpms test on LNL Mohammed Thasleem
2023-11-23 18:48 ` [igt-dev] ✗ Fi.CI.BUILD: failure for " Patchwork
2023-11-24  8:27 ` [igt-dev] [PATCH i-g-t] " Mohammed Thasleem
2023-11-24 13:32   ` Sharma, Swati2 [this message]
2023-11-29 10:19   ` [igt-dev] [PATCH i-g-t] tests/intel/kms_pm_dc: Add LNL platform for dc9-dpms validation Mohammed Thasleem
2023-11-30 13:37     ` Kamil Konieczny
2023-11-24 10:32 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/intel/kms_pm_dc: Fix dc9-dpms test on LNL (rev2) Patchwork
2023-11-24 11:43 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-11-25 13:52 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-11-29 13:03 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/intel/kms_pm_dc: Fix dc9-dpms test on LNL (rev3) Patchwork
2023-11-29 14:13 ` [igt-dev] ✓ CI.xeBAT: " Patchwork
2023-11-30 13:30 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork

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=722a1c33-d384-4f9c-8652-3d09b8dca950@intel.com \
    --to=swati2.sharma@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=mohammed.thasleem@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