From: "Belgaumkar, Vinay" <vinay.belgaumkar@intel.com>
To: Riana Tauro <riana.tauro@intel.com>,
<intel-gfx@lists.freedesktop.org>,
<igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [Intel-gfx] [PATCH i-g-t] tests/i915_pm_freq_api: Ignore zero register value
Date: Mon, 14 Aug 2023 09:48:47 -0700 [thread overview]
Message-ID: <46a09df0-ffb5-a8ea-e90d-dca65f5d92f0@intel.com> (raw)
In-Reply-To: <b5e574a1-7aa4-d233-3b02-f0acbac517bc@intel.com>
On 8/14/2023 12:24 AM, Riana Tauro wrote:
> Hi Vinay
>
> On 8/9/2023 6:20 AM, Vinay Belgaumkar wrote:
>> Register read for requested_freq can return 0 when system is
>> in runtime_pm. Make allowance for this case.
>>
>> Link: https://gitlab.freedesktop.org/drm/intel/issues/8736
>> Link: https://gitlab.freedesktop.org/drm/intel/issues/8989
>>
>> Signed-off-by: Vinay Belgaumkar <vinay.belgaumkar@intel.com>
>> ---
>> tests/i915/i915_pm_freq_api.c | 18 ++++++++++++++----
>> 1 file changed, 14 insertions(+), 4 deletions(-)
>>
>> diff --git a/tests/i915/i915_pm_freq_api.c
>> b/tests/i915/i915_pm_freq_api.c
>> index cf21cc936..9c71411ee 100644
>> --- a/tests/i915/i915_pm_freq_api.c
>> +++ b/tests/i915/i915_pm_freq_api.c
>> @@ -88,6 +88,7 @@ static void test_freq_basic_api(int dirfd, int gt)
>> static void test_reset(int i915, int dirfd, int gt, int count)
>> {
>> uint32_t rpn = get_freq(dirfd, RPS_RPn_FREQ_MHZ);
>> + uint32_t req_freq;
>> int fd;
>> for (int i = 0; i < count; i++) {
>> @@ -95,14 +96,18 @@ static void test_reset(int i915, int dirfd, int
>> gt, int count)
>> igt_assert(set_freq(dirfd, RPS_MIN_FREQ_MHZ, rpn) > 0);
>> igt_assert(set_freq(dirfd, RPS_MAX_FREQ_MHZ, rpn) > 0);
>> usleep(ACT_FREQ_LATENCY_US);
>> - igt_assert_eq(get_freq(dirfd, RPS_CUR_FREQ_MHZ), rpn);
>> + req_freq = get_freq(dirfd, RPS_CUR_FREQ_MHZ);
>> + if (req_freq)
>> + igt_assert_eq(req_freq, rpn);
>
> Is there anything else that can cause req_freq to be zero?
>
> To differentiate can we assert only when runtime_status is active
> (igt_get_runtime_pm_status() == IGT_RUNTIME_PM_STATUS_ACTIVE) ?
Makes sense, re-sending.
Thanks,
Vinay.
>
>
> Thanks
> Riana Tauro
>> /* Manually trigger a GT reset */
>> fd = igt_debugfs_gt_open(i915, gt, "reset", O_WRONLY);
>> igt_require(fd >= 0);
>> igt_ignore_warn(write(fd, "1\n", 2));
>> - igt_assert_eq(get_freq(dirfd, RPS_CUR_FREQ_MHZ), rpn);
>> + req_freq = get_freq(dirfd, RPS_CUR_FREQ_MHZ);
>> + if (req_freq)
>> + igt_assert_eq(req_freq, rpn);
>> }
>> close(fd);
>> }
>> @@ -110,17 +115,22 @@ static void test_reset(int i915, int dirfd, int
>> gt, int count)
>> static void test_suspend(int i915, int dirfd, int gt)
>> {
>> uint32_t rpn = get_freq(dirfd, RPS_RPn_FREQ_MHZ);
>> + uint32_t req_freq;
>> igt_assert(set_freq(dirfd, RPS_MIN_FREQ_MHZ, rpn) > 0);
>> igt_assert(set_freq(dirfd, RPS_MAX_FREQ_MHZ, rpn) > 0);
>> usleep(ACT_FREQ_LATENCY_US);
>> - igt_assert_eq(get_freq(dirfd, RPS_CUR_FREQ_MHZ), rpn);
>> + req_freq = get_freq(dirfd, RPS_CUR_FREQ_MHZ);
>> + if (req_freq)
>> + igt_assert_eq(req_freq, rpn);
>> /* Manually trigger a suspend */
>> igt_system_suspend_autoresume(SUSPEND_STATE_S3,
>> SUSPEND_TEST_NONE);
>> - igt_assert_eq(get_freq(dirfd, RPS_CUR_FREQ_MHZ), rpn);
>> + req_freq = get_freq(dirfd, RPS_CUR_FREQ_MHZ);
>> + if (req_freq)
>> + igt_assert_eq(req_freq, rpn);
>> }
>> int i915 = -1;
next prev parent reply other threads:[~2023-08-14 16:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-09 0:50 [igt-dev] [PATCH i-g-t] tests/i915_pm_freq_api: Ignore zero register value Vinay Belgaumkar
2023-08-09 1:37 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-08-09 3:44 ` [igt-dev] ○ CI.xeBAT: info " Patchwork
2023-08-09 13:06 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-08-16 14:14 ` Kamil Konieczny
2023-08-14 7:24 ` [igt-dev] [Intel-gfx] [PATCH i-g-t] " Riana Tauro
2023-08-14 16:48 ` Belgaumkar, Vinay [this message]
2023-08-16 7:31 ` Riana Tauro
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=46a09df0-ffb5-a8ea-e90d-dca65f5d92f0@intel.com \
--to=vinay.belgaumkar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=riana.tauro@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