Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Wed, 14 Jun 2023 19:49:41 +0530	[thread overview]
Message-ID: <e4d0c9fe-8fb1-51fa-2bd1-c295283f8b4f@intel.com> (raw)
In-Reply-To: <20230614115225.8863-1-nidhi1.gupta@intel.com>

Hi Nidhi,

On Wed-14-06-2023 05:22 pm, Nidhi Gupta wrote:
> Pipe D is invalid in big joiner and because of that currently
> test throws as skip for all the pipes and as it is within the
> dynamic subtest block.
> Fixed in IGT to skip the big joiner validity check for pipe-D
> and execute for the rest of the pipes as it is.
> 
> Signed-off-by: Nidhi Gupta <nidhi1.gupta@intel.com>
> ---
>   tests/kms_plane_cursor.c | 5 ++++-
>   1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/tests/kms_plane_cursor.c b/tests/kms_plane_cursor.c
> index 59b105c6..38918bb7 100644
> --- a/tests/kms_plane_cursor.c
> +++ b/tests/kms_plane_cursor.c
> @@ -86,7 +86,10 @@ 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));
> +
> +	/*Pipe D is invalid in big joiner*/
> +	if (data->pipe_id != PIPE_D)
> +		igt_require(i915_pipe_output_combo_valid(display));

Why do we need to call this helper for pipe-A/B/C as we already know 
these pipes can support bigjoiner? If upcoming hardware enables pip-E/F, 
then how this logic can handle?

i915_pipe_output_combo_valid() itself is taken care of last pipe (pipe-D 
in case of adl/dg2). Maybe you need to think about a way to check before 
calling the igt_dynamic().

- Bhanu

>   
>   	igt_info("Using (pipe %s + %s) to run the subtest.\n",
>   		 kmstest_pipe_name(data->pipe_id), igt_output_name(data->output));

  reply	other threads:[~2023-06-14 14:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
2023-06-14 15:24 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2023-06-15  5:24 [igt-dev] [PATCH i-g-t] " Nidhi Gupta
2023-06-19  6:00 ` 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=e4d0c9fe-8fb1-51fa-2bd1-c295283f8b4f@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