Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Modem, Bhanuprakash" <bhanuprakash.modem@intel.com>
To: Mohammed Thasleem <mohammed.thasleem@intel.com>,
	<igt-dev@lists.freedesktop.org>
Subject: Re: [igt-dev] [PATCH v4 1/2] tests/kms_display_modes: Fixed mode selection for extended mode tests
Date: Wed, 28 Jun 2023 13:06:21 +0530	[thread overview]
Message-ID: <2776c688-70db-d4ef-fc33-06088760bedc@intel.com> (raw)
In-Reply-To: <20230627185528.2498910-1-mohammed.thasleem@intel.com>

Hi Thasleem,

On Wed-28-06-2023 12:25 am, Mohammed Thasleem wrote:
> Added check on DP-MST and 4k panels when two moniters connected
> through MST.

We are not doing this anymore, please fix the commit message.

> This will find the connector mode combo that fits into the
> bandwidth when more than one monitor is connected.
> 
> Example:
>    When two monitors connected through MST, the second monitor
>    also tries to use the same mode. So two such modes may not
>    fit into the link bandwidth. So, iterate through connected
>    outputs & modes and find a combination of modes those fit
>    into the link BW.
> 
> v2: -Updated commit msg and description. (Bhanu)
>      -Renamed restart with retry. (Bhanu)
>      -Moved igt_pipe_crc_new before retry. (Bhanu)
>      -Removed unrelated changes and new line. (Bhanu)
>      -Minor changes.
> v3: Updated discription and added EINVAL check.
> v4: Removed EINVAL and ENOSPC checks.
>      Added check for DP-MST and 4k panels.
>      Updated discription.
> v5: Defined 4k display modes globally.
> v6: -Removed if loop checks.
>      -Added igt override to avoid dp mst bw failure.
> v7: Resolved conflict.
> v8: Removed igt_display_reset from called function.
> 
> Signed-off-by: Mohammed Thasleem <mohammed.thasleem@intel.com>
> ---
>   tests/kms_display_modes.c | 5 +++--
>   1 file changed, 3 insertions(+), 2 deletions(-)
> 
> diff --git a/tests/kms_display_modes.c b/tests/kms_display_modes.c
> index 93d91ef5..4bebb25e 100644
> --- a/tests/kms_display_modes.c
> +++ b/tests/kms_display_modes.c
> @@ -144,8 +144,6 @@ static void run_extendedmode_basic(data_t *data,
>   	int width, height;
>   	cairo_t *cr;
>   
> -	igt_display_reset(display);
> -
>   	igt_output_set_pipe(output1, pipe1);
>   	igt_output_set_pipe(output2, pipe2);

These are redundant, as we already setting the pipe/output before 
calling the test.

- Bhanu

>   
> @@ -253,6 +251,9 @@ static void run_extendedmode_test(data_t *data) {
>   					igt_output_set_pipe(output1, pipe1);
>   					igt_output_set_pipe(output2, pipe2);
>   
> +					if (!igt_override_all_active_output_modes_to_fit_bw(display))
> +						continue;
> +
>   					if (!i915_pipe_output_combo_valid(display))
>   						continue;
>   

  reply	other threads:[~2023-06-28  7:36 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-07 11:53 [igt-dev] [PATCH i-g-t v2 0/2] Fixed mode selection for MST modeset Mohammed Thasleem
2023-06-07 11:53 ` [igt-dev] [PATCH i-g-t v2 1/2] tests/kms_display_modes: Fixed mode selection for extended mode tests Mohammed Thasleem
2023-06-08 11:26   ` Modem, Bhanuprakash
2023-06-25 18:34   ` [igt-dev] [PATCH v3 " Mohammed Thasleem
2023-06-26 11:01     ` Modem, Bhanuprakash
2023-06-27 18:55     ` [igt-dev] [PATCH v4 " Mohammed Thasleem
2023-06-28  7:36       ` Modem, Bhanuprakash [this message]
2023-07-03  5:38       ` [igt-dev] [PATCH v5 " Thasleem, Mohammed
2023-06-07 11:53 ` [igt-dev] [PATCH i-g-t v2 2/2] tests/i915/kms_cdclk: Fixed mode selection for MST modeset Mohammed Thasleem
2023-06-08 11:17   ` Modem, Bhanuprakash
2023-06-09  7:21     ` Sharma, Swati2
2023-06-27 20:34   ` [igt-dev] [PATCH v3 " Mohammed Thasleem
2023-07-03  6:26     ` [igt-dev] [PATCH v4 " Thasleem, Mohammed
2023-06-07 13:22 ` [igt-dev] ✗ GitLab.Pipeline: warning for Fixed mode selection for MST modeset (rev4) Patchwork
2023-06-07 13:48 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2023-06-08  2:06 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-06-08  6:17 ` [igt-dev] ✓ Fi.CI.BAT: success for Fixed mode selection for MST modeset (rev5) Patchwork
2023-06-08 11:43 ` [igt-dev] ✗ Fi.CI.BUILD: failure for Fixed mode selection for MST modeset (rev6) Patchwork
2023-06-09  4:22 ` [igt-dev] ✗ Fi.CI.IGT: failure for Fixed mode selection for MST modeset (rev5) Patchwork
2023-06-25 19:26 ` [igt-dev] ✓ Fi.CI.BAT: success for Fixed mode selection for MST modeset (rev7) Patchwork
2023-06-25 20:46 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2023-06-27 20:06 ` [igt-dev] ✓ Fi.CI.BAT: success for Fixed mode selection for MST modeset (rev8) Patchwork
2023-06-27 21:47 ` [igt-dev] ✓ Fi.CI.BAT: success for Fixed mode selection for MST modeset (rev9) Patchwork
2023-06-28 12:50 ` [igt-dev] ✗ Fi.CI.IGT: failure for Fixed mode selection for MST modeset (rev8) Patchwork
2023-06-28 15:48 ` [igt-dev] ✗ Fi.CI.IGT: failure for Fixed mode selection for MST modeset (rev9) Patchwork
2023-07-03  6:44 ` [igt-dev] ✗ Fi.CI.BAT: failure for Fixed mode selection for MST modeset (rev10) Patchwork
2023-07-03  7:08 ` [igt-dev] ✓ Fi.CI.BAT: success for Fixed mode selection for MST modeset (rev11) Patchwork
2023-07-03  8:19 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2023-07-05 13:07 ` [igt-dev] ✗ Fi.CI.BAT: failure for Fixed mode selection for MST modeset (rev12) 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=2776c688-70db-d4ef-fc33-06088760bedc@intel.com \
    --to=bhanuprakash.modem@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=mohammed.thasleem@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