public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Karthik B S <karthik.b.s@intel.com>
To: Mohammed Thasleem <mohammed.thasleem@intel.com>,
	<igt-dev@lists.freedesktop.org>
Cc: <swati2.sharma@intel.com>
Subject: Re: [PATCH i-g-t] tests/intel/kms_pm_dc: Avoid PIPE_B conflict on dual-eDP systems
Date: Fri, 13 Mar 2026 10:12:36 +0530	[thread overview]
Message-ID: <017e7c52-674c-4a4c-b13b-a319e9d2fe3c@intel.com> (raw)
In-Reply-To: <20260312080305.43449-1-mohammed.thasleem@intel.com>

Hi Thasleem,

On 3/12/2026 1:33 PM, Mohammed Thasleem wrote:
> Select the first available eDP output and assign it to PIPE_B to avoid pipe
> conflicts on dual-eDP systems.
>
> Signed-off-by: Mohammed Thasleem <mohammed.thasleem@intel.com>
> ---
>   tests/intel/kms_pm_dc.c | 3 +++
>   1 file changed, 3 insertions(+)
>
> diff --git a/tests/intel/kms_pm_dc.c b/tests/intel/kms_pm_dc.c
> index d1c4a5019..2e5ffe842 100644
> --- a/tests/intel/kms_pm_dc.c
> +++ b/tests/intel/kms_pm_dc.c
> @@ -149,7 +149,10 @@ static void set_output_on_pipe_b(data_t *data)
>   
>   		data->output = output;
>   		data->mode = igt_output_get_mode(output);
> +
> +		break;
>   	}

Wouldn't we want to run this test on both the eDP's if say both support PSR?

Thanks and Regards,
Karthik.B.S
> +	igt_require_f(data->output, "No valid eDP found for PIPE_B\n");
>   }
>   
>   static void setup_output(data_t *data)

  parent reply	other threads:[~2026-03-13  4:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-12  8:03 [PATCH i-g-t] tests/intel/kms_pm_dc: Avoid PIPE_B conflict on dual-eDP systems Mohammed Thasleem
2026-03-12 12:51 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-03-12 13:08 ` ✗ i915.CI.BAT: failure " Patchwork
2026-03-13  4:42 ` Karthik B S [this message]
2026-03-13 10:03 ` ✗ Xe.CI.FULL: " 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=017e7c52-674c-4a4c-b13b-a319e9d2fe3c@intel.com \
    --to=karthik.b.s@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=mohammed.thasleem@intel.com \
    --cc=swati2.sharma@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