From: "Naladala, Ramanaidu" <ramanaidu.naladala@intel.com>
To: "Kandpal, Suraj" <suraj.kandpal@intel.com>,
"igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>
Cc: "B, Jeevan" <jeevan.b@intel.com>
Subject: Re: [PATCH i-g-t v4 2/4] tests/intel/kms_pm_dc: Update test duration to 4 seconds
Date: Thu, 22 Aug 2024 15:01:32 +0530 [thread overview]
Message-ID: <d77c9f49-ec62-4bd5-aaed-e7ef4bc21e4c@intel.com> (raw)
In-Reply-To: <MW4PR11MB67614EC56036B26700FCCCF7E3862@MW4PR11MB6761.namprd11.prod.outlook.com>
Hi Suraj,
We need to simulate the scenario of extended vblank. Keeping CI
execution time in mind, we have set the sequence for 4 seconds. For the
first 2-3 seconds, we run at X refresh rate and then change the refresh
rate in between to emulate extended vblank for the remaining 4 seconds.
On 8/13/2024 2:53 PM, Kandpal, Suraj wrote:
> Why is the duration 4 or how did you come to this number explain , if in ms don't we have a define for that use that its
> not good to use magic number.
next prev parent reply other threads:[~2024-08-22 9:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-11 20:03 [PATCH i-g-t v4 0/4] Improvise-the-deep-pkgc Naladala Ramanaidu
2024-08-11 20:03 ` [PATCH i-g-t v4 1/4] tests/intel/kms_pm_dc: Update VRR handling and eDP output check Naladala Ramanaidu
2024-08-13 9:21 ` Kandpal, Suraj
2024-08-11 20:03 ` [PATCH i-g-t v4 2/4] tests/intel/kms_pm_dc: Update test duration to 4 seconds Naladala Ramanaidu
2024-08-13 9:23 ` Kandpal, Suraj
2024-08-22 9:31 ` Naladala, Ramanaidu [this message]
2024-08-11 20:03 ` [PATCH i-g-t v4 3/4] tests/intel/kms_pm_dc: Add polling for deep-pkgc Naladala Ramanaidu
2024-08-13 9:26 ` Kandpal, Suraj
2024-08-11 20:03 ` [PATCH i-g-t v4 4/4] HAX patch do not merge Naladala Ramanaidu
2024-08-11 20:24 ` ✗ CI.xeBAT: failure for Improvise-the-deep-pkgc (rev4) Patchwork
2024-08-11 20:40 ` ✗ Fi.CI.BAT: " Patchwork
2024-08-11 21:22 ` ✗ CI.xeFULL: " Patchwork
2024-08-12 4:03 ` [PATCH i-g-t v4 0/4] Improvise-the-deep-pkgc Kandpal, Suraj
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=d77c9f49-ec62-4bd5-aaed-e7ef4bc21e4c@intel.com \
--to=ramanaidu.naladala@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=jeevan.b@intel.com \
--cc=suraj.kandpal@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