From: "Jason-JH Lin (林睿祥)" <Jason-JH.Lin@mediatek.com>
To: "igt-dev@lists.freedesktop.org" <igt-dev@lists.freedesktop.org>,
"santhosh.reddy.guddati@intel.com"
<santhosh.reddy.guddati@intel.com>
Subject: Re: [PATCH i-g-t] tests/kms_content_protection: Skip MST outputs in SST-style tests
Date: Fri, 17 Jul 2026 16:58:35 +0000 [thread overview]
Message-ID: <1de1d9f616efbb16ce26bf2653da27eefb4ff148.camel@mediatek.com> (raw)
In-Reply-To: <96a7b371898c7363f886b2a80186ff5edeca1359.camel@mediatek.com>
On Wed, 2026-07-15 at 23:14 +0800, Jason-JH.Lin wrote:
> On Fri, 2026-07-10 at 11:42 +0530, Reddy Guddati, Santhosh wrote:
> > 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.
> >
>
> Hi Reddy,
>
> Sorry for the late reply. I don't know why I lost your reply mail.😫️
>
> > 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.
>
> I think a single monitor is connected through a MST hub make sense.
> But in MTK platform which supports MST, even if one monitor connected
> to a MST hub, it'll got to the MST flow and make the HDCP auth fail.
>
> But we found a HDCP issue in MST mode recently. We'll confirm if we
> still need this skip patch after we fix the issue and let you know.
>
Hi Reddy,
After we solved the MST HDCP issue, I confirmed that we can pass SST
test case in MST mode without this patch.
So we can drop this patch now.
Thanks
Jason-JH Lin
prev parent reply other threads:[~2026-07-17 16:59 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
2026-07-15 15:14 ` Jason-JH Lin (林睿祥)
2026-07-17 16:58 ` Jason-JH Lin (林睿祥) [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=1de1d9f616efbb16ce26bf2653da27eefb4ff148.camel@mediatek.com \
--to=jason-jh.lin@mediatek.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