From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Sean Paul <sean@poorly.run>, <igt-dev@lists.freedesktop.org>
Cc: Sean Paul <seanpaul@chromium.org>
Subject: Re: [igt-dev] [PATCH 0/6] tests/kms_vrr: Modify kms_vrr to allow flicker
Date: Thu, 7 Sep 2023 00:38:25 +0530 [thread overview]
Message-ID: <117968a6-8ccb-1283-ab82-6e6f9ef59dc0@intel.com> (raw)
In-Reply-To: <20230825183934.1271156-1-sean@poorly.run>
Hi Sean Paul,
On Sat-26-08-2023 12:06 am, Sean Paul wrote:
> From: Sean Paul <seanpaul@chromium.org>
>
> Do some cleanup in the kms_vrr test and add some optional command line
> arguments to alter the target refresh rate for the test. This allows us
> to profile VRR flicker on panels at the low end of the refresh range.
Overall, this series makes sense to me. I have dropped few comments & my
R-b too. But with this series, there is a crash in Negative test [1].
Please fix that.
And I can feel it is better to check the health of these kms_vrr tests
by adding them to the BAT [2] & [3] with a HAX patch.
[1]:
https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_9666/shard-mtlp-1/igt@kms_vrr@negative-basic@pipe-a-edp-1.html
[2]: tests/intel-ci/fast-feedback.testlist
[3]: tests/intel-ci/xe-fast-feedback.testlist
- Bhanu
>
> Sean Paul (6):
> tests/kms_vrr: Move fb0 and fb1 to an array
> tests/kms_vrr: Move vtest_ns into data_t
> tests/kms_vrr: Allow test rate to be altered from the command line
> tests/kms_vrr: Allow test duration to be specified from the command
> line
> tests/kms_vrr: Change the pattern displayed in the test
> test/kms_vrr: Add ability to flip static image for flicker profiling
>
> tests/kms_vrr.c | 138 ++++++++++++++++++++++++++++++++----------------
> 1 file changed, 92 insertions(+), 46 deletions(-)
>
prev parent reply other threads:[~2023-09-06 19:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 18:36 [igt-dev] [PATCH 0/6] tests/kms_vrr: Modify kms_vrr to allow flicker Sean Paul
2023-08-25 18:36 ` [igt-dev] [PATCH 1/6] tests/kms_vrr: Move fb0 and fb1 to an array Sean Paul
2023-09-06 19:07 ` Modem, Bhanuprakash
2023-08-25 18:36 ` [igt-dev] [PATCH 2/6] tests/kms_vrr: Move vtest_ns into data_t Sean Paul
2023-09-06 19:07 ` Modem, Bhanuprakash
2023-08-25 18:36 ` [igt-dev] [PATCH 3/6] tests/kms_vrr: Allow test rate to be altered from the command line Sean Paul
2023-09-06 19:07 ` Modem, Bhanuprakash
2023-08-25 18:36 ` [igt-dev] [PATCH 4/6] tests/kms_vrr: Allow test duration to be specified " Sean Paul
2023-09-06 19:08 ` Modem, Bhanuprakash
2023-08-25 18:36 ` [igt-dev] [PATCH 5/6] tests/kms_vrr: Change the pattern displayed in the test Sean Paul
2023-09-06 19:08 ` Modem, Bhanuprakash
2023-08-25 18:36 ` [igt-dev] [PATCH 6/6] test/kms_vrr: Add ability to flip static image for flicker profiling Sean Paul
2023-08-25 19:30 ` [igt-dev] ✗ GitLab.Pipeline: warning for tests/kms_vrr: Modify kms_vrr to allow flicker Patchwork
2023-08-25 19:46 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
2023-08-25 19:55 ` [igt-dev] ✓ Fi.CI.BAT: " Patchwork
2023-08-26 13:51 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-08-31 17:15 ` [igt-dev] [PATCH 0/6] " Sean Paul
2023-09-06 19:08 ` Modem, Bhanuprakash [this message]
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=117968a6-8ccb-1283-ab82-6e6f9ef59dc0@intel.com \
--to=bhanuprakash.modem@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=sean@poorly.run \
--cc=seanpaul@chromium.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