From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Nidhi Gupta <nidhi1.gupta@intel.com>, <igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH i-g-t] tests/kms_plane_cursor: Pipe-D is invalid in big joiner
Date: Mon, 19 Jun 2023 11:30:42 +0530 [thread overview]
Message-ID: <7df7520e-6ddb-b3c7-3007-73faac75b4fe@intel.com> (raw)
In-Reply-To: <20230615052438.15220-1-nidhi1.gupta@intel.com>
Hi Nidhi,
On Thu-15-06-2023 10:54 am, Nidhi Gupta wrote:
> Pipe D is invalid in big joiner and because of that currently
> test throws as skip for all the pipes as it is within the
> dynamic subtest block.
> Fixed in IGT by not executing the subtest if valid combo of pipe
> and output not found for big joiner and go on to check for the
> next pipe.
Please drop Pipe-D from commit subject & message, and write as a generic.
Also, please maintain the rev information.
Example:
V2: - Changes made from Initial version
>
> Signed-off-by: Nidhi Gupta <nidhi1.gupta@intel.com>
> ---
> tests/kms_plane_cursor.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/tests/kms_plane_cursor.c b/tests/kms_plane_cursor.c
> index 59b105c6..b1f3cecc 100644
> --- a/tests/kms_plane_cursor.c
> +++ b/tests/kms_plane_cursor.c
> @@ -86,7 +86,6 @@ static void test_init(data_t *data, enum pipe pipe_id, igt_output_t *output)
> data->cursor = igt_pipe_get_plane_type(data->pipe, DRM_PLANE_TYPE_CURSOR);
>
> igt_output_set_pipe(data->output, data->pipe_id);
> - igt_require(i915_pipe_output_combo_valid(display));
>
> igt_info("Using (pipe %s + %s) to run the subtest.\n",
> kmstest_pipe_name(data->pipe_id), igt_output_name(data->output));
> @@ -268,6 +267,7 @@ igt_main
> static const int cursor_sizes[] = { 64, 128, 256 };
> data_t data = { .max_curw = 64, .max_curh = 64 };
> enum pipe pipe;
> + bool result;
> igt_output_t *output;
> int i, j;
> struct {
> @@ -312,6 +312,13 @@ igt_main
>
> test_init(&data, pipe, output);
Test initialization is not required, if it is an invalid config.
>
> + result = i915_pipe_output_combo_valid(&data.display);
> + if (result == false) {
No need of new variable 'result', instead you can use
if (!i915_pipe_output_combo_valid(&data.display))
continue;
> + igt_info("pipe %s + %s is not a valid combo for big joiner\n",
----------------------------------------^
Use igt_debug() if you really need this print, else please drop it.
- Bhanu
> + kmstest_pipe_name(data.pipe_id), igt_output_name(data.output));
> + continue;
> + }
> +
> for (j = 0; j < ARRAY_SIZE(cursor_sizes); j++) {
> int size = cursor_sizes[j];
>
next prev parent reply other threads:[~2023-06-19 6:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-15 5:24 [igt-dev] [PATCH i-g-t] tests/kms_plane_cursor: Pipe-D is invalid in big joiner Nidhi Gupta
2023-06-15 8:07 ` [igt-dev] ✗ Fi.CI.BAT: failure for tests/kms_plane_cursor: Pipe-D is invalid in big joiner (rev2) Patchwork
2023-06-19 6:00 ` Modem, Bhanuprakash [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-06-14 11:52 [igt-dev] [PATCH i-g-t] tests/kms_plane_cursor: Pipe-D is invalid in big joiner Nidhi Gupta
2023-06-14 14:19 ` Modem, Bhanuprakash
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=7df7520e-6ddb-b3c7-3007-73faac75b4fe@intel.com \
--to=bhanuprakash.modem@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=nidhi1.gupta@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