Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Karthik Poosa <karthik.poosa@intel.com>
To: igt-dev@lists.freedesktop.org
Cc: anshuman.gupta@intel.com, badal.nilawar@intel.com,
	vinay.belgaumkar@intel.com, riana.tauro@intel.com,
	rodrigo.vivi@intel.com, Karthik Poosa <karthik.poosa@intel.com>
Subject: [PATCH i-g-t v4 2/2] tests/intel/xe_gt_freq: Add a wait after gt reset
Date: Tue, 20 Aug 2024 23:53:24 +0530	[thread overview]
Message-ID: <20240820182324.3206155-3-karthik.poosa@intel.com> (raw)
In-Reply-To: <20240820182324.3206155-1-karthik.poosa@intel.com>

After reset min and max takes sometime to get set.
So add a wait of 100ms after gt reset before reading
min and max frequencies.

Signed-off-by: Karthik Poosa <karthik.poosa@intel.com>
Reviewed-by: Riana Tauro <riana.tauro@intel.com>
---
 tests/intel/xe_gt_freq.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/tests/intel/xe_gt_freq.c b/tests/intel/xe_gt_freq.c
index 56cc10ade..427e12c55 100644
--- a/tests/intel/xe_gt_freq.c
+++ b/tests/intel/xe_gt_freq.c
@@ -342,6 +342,7 @@ static void test_reset(int fd, int gt_id, int cycles)
 			     "Failed after %d good cycles\n", i);
 
 		xe_force_gt_reset_async(fd, gt_id);
+		usleep(SLPC_FREQ_LATENCY_US);
 
 		igt_assert_f(get_freq(fd, gt_id, "min") == rpn,
 			     "Failed after %d good cycles\n", i);
-- 
2.25.1


  parent reply	other threads:[~2024-08-20 18:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-20 18:23 [PATCH i-g-t v4 0/2] tests/intel/xe_gt_freq: Add a wait after gt reset Karthik Poosa
2024-08-20 18:23 ` [PATCH i-g-t v4 1/2] tests/intel/xe_gt_freq: Rename ACT_FREQ_LATENCY_US to SLPC_FREQ_LATENCY_US Karthik Poosa
2024-08-20 18:23 ` Karthik Poosa [this message]
2024-08-20 19:11 ` ✗ Fi.CI.BAT: failure for tests/intel/xe_gt_freq: Add a wait after gt reset (rev4) Patchwork
2024-08-20 19:19 ` ✓ CI.xeBAT: success " Patchwork
2024-08-21  1:09 ` ✗ CI.xeFULL: 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=20240820182324.3206155-3-karthik.poosa@intel.com \
    --to=karthik.poosa@intel.com \
    --cc=anshuman.gupta@intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=riana.tauro@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=vinay.belgaumkar@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