Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Badal Nilawar <badal.nilawar@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [PATCH i-g-t 1/2] test/intel/xe_gt_freq: Fix freq_low_max test
Date: Thu, 18 Jan 2024 20:26:35 +0530	[thread overview]
Message-ID: <20240118145636.1775115-2-badal.nilawar@intel.com> (raw)
In-Reply-To: <20240118145636.1775115-1-badal.nilawar@intel.com>

freq_low_max test is intended to validate GuC PC (SLPC) behaviour
when max freq set to less than min freq. As workloads are not being
run validating cur freq is enough.

v2: Validate act freq as well when gt is not in C6 (Vinay)

Fixes: acaaca0bf317 ("tests/xe: Add Xe IGT tests")
Signed-off-by: Badal Nilawar <badal.nilawar@intel.com>
---
 tests/intel/xe_gt_freq.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/tests/intel/xe_gt_freq.c b/tests/intel/xe_gt_freq.c
index 4334a8a41..bf63e4298 100644
--- a/tests/intel/xe_gt_freq.c
+++ b/tests/intel/xe_gt_freq.c
@@ -263,7 +263,9 @@ static void test_freq_low_max(int fd, int gt_id)
 	igt_assert(set_freq(fd, gt_id, "max", rpn) > 0);
 	usleep(ACT_FREQ_LATENCY_US);
 	igt_assert(get_freq(fd, gt_id, "cur") == rpe);
-	igt_assert(get_freq(fd, gt_id, "act") == rpe);
+
+	if (!xe_is_gt_in_c6(fd, gt_id))
+		igt_assert(get_freq(fd, gt_id, "act") == rpe);
 }
 
 /**
-- 
2.25.1


  reply	other threads:[~2024-01-18 14:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-18 14:56 [PATCH i-g-t 0/2] Couple of fixes to guc_pc tests Badal Nilawar
2024-01-18 14:56 ` Badal Nilawar [this message]
2024-01-18 14:56 ` [PATCH i-g-t 2/2] tests/intel/xe_gt_freq: Skip GuC PC tests if SLPC not enabled Badal Nilawar
2024-01-18 16:10   ` Gupta, Anshuman
2024-01-18 17:22     ` Nilawar, Badal
2024-01-18 17:07 ` ✓ Fi.CI.BAT: success for Couple of fixes to guc_pc tests (rev2) Patchwork
2024-01-18 17:50 ` ✓ CI.xeBAT: " Patchwork
2024-01-18 19:31 ` ✗ 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=20240118145636.1775115-2-badal.nilawar@intel.com \
    --to=badal.nilawar@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