From: Badal Nilawar <badal.nilawar@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [PATCH i-g-t 1/2] test/intel/xe_guc_pc: Skip freq_*_idle tests on PVC
Date: Fri, 24 Nov 2023 15:59:45 +0530 [thread overview]
Message-ID: <20231124102946.2650848-2-badal.nilawar@intel.com> (raw)
In-Reply-To: <20231124102946.2650848-1-badal.nilawar@intel.com>
PVC does not support RC6 so skip freq_fixed_idle and freq_range_idle
tests.
Signed-off-by: Badal Nilawar <badal.nilawar@intel.com>
---
tests/intel/xe_guc_pc.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/tests/intel/xe_guc_pc.c b/tests/intel/xe_guc_pc.c
index 3376e838f..c23017501 100644
--- a/tests/intel/xe_guc_pc.c
+++ b/tests/intel/xe_guc_pc.c
@@ -295,6 +295,7 @@ igt_main
}
igt_subtest("freq_fixed_idle") {
+ igt_require(!IS_PONTEVECCHIO(xe_dev_id(fd)));
xe_for_each_gt(fd, gt) {
igt_require_f(igt_wait(xe_is_gt_in_c6(fd, gt), 1000, 10),
"GT %d should be in C6\n", gt);
@@ -303,6 +304,7 @@ igt_main
}
igt_subtest("freq_range_idle") {
+ igt_require(!IS_PONTEVECCHIO(xe_dev_id(fd)));
xe_for_each_gt(fd, gt) {
igt_require_f(igt_wait(xe_is_gt_in_c6(fd, gt), 1000, 10),
"GT %d should be in C6\n", gt);
--
2.25.1
next prev parent reply other threads:[~2023-11-24 10:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-24 10:29 [igt-dev] [PATCH i-g-t 0/2] Couple of fixes to guc_pc tests Badal Nilawar
2023-11-24 10:29 ` Badal Nilawar [this message]
2023-11-24 11:21 ` [igt-dev] [PATCH i-g-t 1/2] test/intel/xe_guc_pc: Skip freq_*_idle tests on PVC Ch, Sai Gowtham
2023-11-24 10:29 ` [igt-dev] [PATCH i-g-t 2/2] test/intel/xe_guc_pc: Fix freq_low_max test Badal Nilawar
2023-12-14 17:50 ` Belgaumkar, Vinay
2023-11-24 13:06 ` [igt-dev] ✗ Fi.CI.BAT: failure for Couple of fixes to guc_pc tests Patchwork
2023-11-24 14:46 ` [igt-dev] ✓ CI.xeBAT: success " 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=20231124102946.2650848-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