From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
<igt-dev@lists.freedesktop.org>
Cc: Arun R Murthy <arun.r.murthy@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t 4/6] tests/kms_async_flips: Run the test only once per pipe
Date: Tue, 31 Jan 2023 17:51:22 +0530 [thread overview]
Message-ID: <61922555-cfbf-e8bb-7b70-e047e98afc25@intel.com> (raw)
In-Reply-To: <20230131120646.27434-5-ville.syrjala@linux.intel.com>
Hi Ville,
On Tue-31-01-2023 05:36 pm, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> No real reason to iterate over all the outputs here. Just
> do the test once per pipe.
>
> Cc: Arun R Murthy <arun.r.murthy@intel.com>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> tests/kms_async_flips.c | 18 +++++-------------
> 1 file changed, 5 insertions(+), 13 deletions(-)
>
> diff --git a/tests/kms_async_flips.c b/tests/kms_async_flips.c
> index f8c97e029c59..54611f66350d 100644
> --- a/tests/kms_async_flips.c
> +++ b/tests/kms_async_flips.c
> @@ -544,20 +544,12 @@ static void test_crc(data_t *data)
>
> static void run_test(data_t *data, void (*test)(data_t *))
> {
> - igt_output_t *output;
> - enum pipe pipe;
> + for_each_pipe_with_valid_output(&data->display, data->pipe, data->output) {
If data->extended is true, it'll iterate over all outputs. Maybe we can
use for_each_pipe_with_single_output() to run test once per pipe.
- Bhanu
> + igt_dynamic_f("pipe-%s", kmstest_pipe_name(data->pipe))
> + test(data);
>
> - for_each_pipe(&data->display, pipe) {
> - for_each_valid_output_on_pipe(&data->display, pipe, output) {
> - igt_dynamic_f("pipe-%s-%s", kmstest_pipe_name(pipe), output->name) {
> - data->output = output;
> - data->pipe = pipe;
> - test(data);
> - }
> -
> - if (!data->extended)
> - break;
> - }
> + if (!data->extended)
> + break;
> }
> }
>
next prev parent reply other threads:[~2023-01-31 12:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-31 12:06 [igt-dev] [PATCH i-g-t 0/6] tests/kms_async_flips: Test format modifiers Ville Syrjala
2023-01-31 12:06 ` [igt-dev] [PATCH i-g-t 1/6] tests/kms_async_flips: Add missing igt_put_cairo_ctx() Ville Syrjala
2023-02-02 11:03 ` Murthy, Arun R
2023-01-31 12:06 ` [igt-dev] [PATCH i-g-t 2/6] tests/kms_async_flips: Render the bars full height Ville Syrjala
2023-02-09 14:11 ` Karthik B S
2023-01-31 12:06 ` [igt-dev] [PATCH i-g-t 3/6] tests/kms_async_flips: Ger rid of i915 specific fb creation Ville Syrjala
2023-02-02 11:24 ` Murthy, Arun R
2023-05-15 9:13 ` Murthy, Arun R
2023-01-31 12:06 ` [igt-dev] [PATCH i-g-t 4/6] tests/kms_async_flips: Run the test only once per pipe Ville Syrjala
2023-01-31 12:21 ` Modem, Bhanuprakash [this message]
2023-02-02 9:27 ` Ville Syrjälä
2023-02-02 11:25 ` Murthy, Arun R
2023-01-31 12:06 ` [igt-dev] [PATCH i-g-t 5/6] tests/kms_async_flips: Split test_init() Ville Syrjala
2023-05-15 9:10 ` Murthy, Arun R
2023-01-31 12:06 ` [igt-dev] [PATCH i-g-t 6/6] tests/kms_async_flips: Test all modifiers Ville Syrjala
2023-02-02 11:23 ` Murthy, Arun R
2023-02-02 12:15 ` Ville Syrjälä
2023-02-02 12:24 ` Murthy, Arun R
2023-02-03 12:32 ` Ville Syrjälä
2023-02-07 5:49 ` Murthy, Arun R
2023-05-15 9:07 ` Murthy, Arun R
2023-02-03 12:29 ` Ville Syrjälä
2023-02-07 5:41 ` Murthy, Arun R
2023-01-31 12:38 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_async_flips: Test format modifiers Patchwork
2023-01-31 16:28 ` [igt-dev] ✓ Fi.CI.IGT: " 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=61922555-cfbf-e8bb-7b70-e047e98afc25@intel.com \
--to=bhanuprakash.modem@intel.com \
--cc=arun.r.murthy@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=ville.syrjala@linux.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