Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Reddy Guddati, Santhosh" <santhosh.reddy.guddati@intel.com>
To: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] tests/kms_content_protection: Skip MST outputs in SST-style tests
Date: Fri, 10 Jul 2026 11:42:42 +0530	[thread overview]
Message-ID: <c67f184b-c93c-47b7-ad5a-a19a2a6078e4@intel.com> (raw)
In-Reply-To: <20260629015411.32130-1-jason-jh.lin@mediatek.com>

Hi Jason,

On 29-06-2026 07:23, Jason-JH Lin wrote:
> MST (Multi-Stream Transport) outputs require topology-wide HDCP
> authentication which is handled by dedicated dp-mst-* subtests.
> Running SST-style tests on MST outputs can cause issues because:
> 
> 1. MST HDCP authentication involves the entire topology (hub + monitors)
> 2. Per-connector HDCP state management differs from SST
> 3. The dp-mst-lic-type-0/1 subtests are specifically designed to test
>     MST HDCP scenarios
> 
> Skip MST outputs in get_hdcp_outputs() when running non-MST subtests
> to ensure proper test isolation.

IMHO, I dont think we should skip all MST outputs in
the SST-style tests - this removes a lot of coverage. NACK for now

You will see a lot of skips after this any mst setup will not run 
individual test on those monitors. We want to test individual displays 
even though they are connected in MST.

The tests (legacy, type1, lic, uevent, srm, mei-interface) will skip 
even if a single monitor is connected through a MST hub thereby a single 
MST display would then get no HDCP coverage at all.

Please let me know your thoughts.

Thanks,
Santhosh

> 
> Signed-off-by: Jason-JH Lin <jason-jh.lin@mediatek.com>
> ---
>   tests/kms_content_protection.c | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
> index d931ce7682be..9d1728ed82a6 100644
> --- a/tests/kms_content_protection.c
> +++ b/tests/kms_content_protection.c
> @@ -751,6 +751,11 @@ static int get_hdcp_outputs(igt_display_t *display, int content_type,
>   			continue;
>   		}
>   
> +		if (igt_get_dp_mst_connector_id(output) >= 0) {
> +			igt_info("Skipping HDCP test on %s, MST output should use dp-mst-* tests\n",
> +				 output->name);
> +			continue;
> +		}
>   

>   		if (count < MAX_HDCP_OUTPUTS)
>   			hdcp_outputs[count++] = output;


  parent reply	other threads:[~2026-07-10  6:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-29  1:53 [PATCH i-g-t] tests/kms_content_protection: Skip MST outputs in SST-style tests Jason-JH Lin
2026-06-29 20:02 ` ✓ Xe.CI.BAT: success for " Patchwork
2026-06-29 20:14 ` ✓ i915.CI.BAT: " Patchwork
2026-06-30  3:34 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-06-30  6:33 ` ✗ i915.CI.Full: " Patchwork
2026-07-08 22:34 ` [PATCH i-g-t] " Manasi Navare
2026-07-10  6:12 ` Reddy Guddati, Santhosh [this message]
2026-07-15 15:14   ` Jason-JH Lin (林睿祥)
2026-07-17 16:58     ` Jason-JH Lin (林睿祥)

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=c67f184b-c93c-47b7-ad5a-a19a2a6078e4@intel.com \
    --to=santhosh.reddy.guddati@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    /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