From: Karthik B S <karthik.b.s@intel.com>
To: Santhosh Reddy Guddati <santhosh.reddy.guddati@intel.com>,
<igt-dev@lists.freedesktop.org>
Cc: <ankit.k.nautiyal@intel.com>
Subject: Re: [PATCH i-g-t v1] tests/intel/kms_joiner: Fix mixed_output subtest skips
Date: Mon, 11 May 2026 11:33:01 +0530 [thread overview]
Message-ID: <d3d87ae0-f43a-4e6a-ab1e-a78e9aaa4314@intel.com> (raw)
In-Reply-To: <20260508035940.645143-1-santhosh.reddy.guddati@intel.com>
Hi Santhosh,
On 5/8/2026 9:29 AM, Santhosh Reddy Guddati wrote:
> In the mixed output case, mixed_output[1] is a non-big-joiner output,
> but bigjoiner_mode_found() was unconditionally called for both outputs,
> causing the subtest to skip. Only require a big joiner mode for the
> first output (j=0); the second uses its default mode.
>
> cc: Karthik B.S <karthik.b.s@intel.com>
> cc: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> Signed-off-by: Santhosh Reddy Guddati <santhosh.reddy.guddati@intel.com>
> ---
> tests/intel/kms_joiner.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/tests/intel/kms_joiner.c b/tests/intel/kms_joiner.c
> index 86226a3ba..20f39ceef 100644
> --- a/tests/intel/kms_joiner.c
> +++ b/tests/intel/kms_joiner.c
> @@ -386,7 +386,7 @@ static void test_invalid_modeset_two_joiner(data_t *data,
>
> output = outputs[j];
>
> - if (!force_joiner) {
> + if (!force_joiner && (!mixed || j == 0)) {
The patch is correct logically and required, but IMHO it would be good
if we can rename the existing variables to make it more clear from the
variable name itself.
Thanks and Regards,
Karthik.B.S
> igt_require_f(bigjoiner_mode_found(data->drm_fd, output->config.connector, max_dotclock, &mode),
> "No big joiner mode found on output %s\n", output->name);
> igt_output_override_mode(output, &mode);
prev parent reply other threads:[~2026-05-11 6:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 3:59 [PATCH i-g-t v1] tests/intel/kms_joiner: Fix mixed_output subtest skips Santhosh Reddy Guddati
2026-05-08 4:49 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-05-08 5:08 ` ✓ i915.CI.BAT: " Patchwork
2026-05-08 15:38 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-05-09 0:09 ` ✗ i915.CI.Full: " Patchwork
2026-05-11 6:03 ` Karthik B S [this message]
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=d3d87ae0-f43a-4e6a-ab1e-a78e9aaa4314@intel.com \
--to=karthik.b.s@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=santhosh.reddy.guddati@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