From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>, igt-dev@lists.freedesktop.org
Subject: Re: [PATCH i-g-t] tests/kms_content_protection: Add LIC Type 1 scenario
Date: Wed, 17 Jan 2024 16:58:30 +0530 [thread overview]
Message-ID: <b204fa15-e193-41ba-8b75-afbfebaeaff4@intel.com> (raw)
In-Reply-To: <20240116112335.353869-1-suraj.kandpal@intel.com>
Hi Suraj,
On 16-Jan-24 4:53 PM, Suraj Kandpal wrote:
> Currently LIC is done only for type0 content this patch
> adds LIC for type1 content too.
>
> --v2
> -Use arg[1] [Swati]
> -Mention Functionality [Swati]
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> ---
> tests/kms_content_protection.c | 19 +++++++++++++++----
> 1 file changed, 15 insertions(+), 4 deletions(-)
>
> diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
> index 6d472ee02..7368cb982 100644
> --- a/tests/kms_content_protection.c
> +++ b/tests/kms_content_protection.c
> @@ -43,8 +43,14 @@
> #include "igt_kmod.h"
>
> /**
> - * SUBTEST: lic
> - * Description: Test for the integrity of link.
> + * SUBTEST: lic-%s
> + * Description: Test for the integrity of link for %arg[1] content.
> + * Functionality: hdcp1.4, hdcp2.2
> + *
> + * arg[1]:
> + *
> + * @type-0: Type 0 with LIC
> + * @type-1: Type 1 with LIC
Since both types support different hdcp versions, we need to revert to
prev version.
lic-type-0
Functionality: hdcp1.4, hdcp2.2
lic-type-1
Functionality: hdcp2.2
> *
> * SUBTEST: content-type-change
> * Description: Test the content type change when the content protection already
> @@ -783,11 +789,16 @@ static const struct {
> .cp_tests = CP_DPMS,
> .content_type = HDCP_CONTENT_TYPE_0
> },
> - { .desc = "Test for the integrity of link.",
> - .name = "lic",
> + { .desc = "Test for the integrity of link with type 0 content.",
> + .name = "lic-type-0",
> .cp_tests = CP_LIC,
> .content_type = HDCP_CONTENT_TYPE_0,
> },
> + { .desc = "Test for the integrity of link with type 1 content",
> + .name = "lic-type-1",
> + .cp_tests = CP_LIC,
> + .content_type = HDCP_CONTENT_TYPE_1,
> + },
> { .desc = "Test content protection with content type 1 "
> "that can be handled only through HDCP2.2.",
> .name = "type1",
next prev parent reply other threads:[~2024-01-17 11:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 10:33 [PATCH i-g-t] tests/kms_content_protection: Add LIC Type 1 scenario Suraj Kandpal
2024-01-12 11:23 ` ✓ Fi.CI.BAT: success for " Patchwork
2024-01-12 11:40 ` ✓ CI.xeBAT: " Patchwork
2024-01-12 14:04 ` ✓ Fi.CI.IGT: " Patchwork
2024-01-16 9:34 ` [PATCH i-g-t] " Nautiyal, Ankit K
2024-01-16 9:34 ` Nautiyal, Ankit K
2024-01-16 9:48 ` Sharma, Swati2
2024-01-16 9:51 ` Kandpal, Suraj
2024-01-16 11:23 ` Suraj Kandpal
2024-01-17 11:28 ` Sharma, Swati2 [this message]
2024-01-18 7:27 ` Suraj Kandpal
2024-01-18 7:33 ` Sharma, Swati2
2024-01-16 11:43 ` ✗ Fi.CI.BUILD: failure for tests/kms_content_protection: Add LIC Type 1 scenario (rev2) Patchwork
2024-01-16 11:48 ` ✗ GitLab.Pipeline: warning " Patchwork
2024-01-18 8:13 ` ✓ CI.xeBAT: success for tests/kms_content_protection: Add LIC Type 1 scenario (rev3) Patchwork
2024-01-18 8:33 ` ✗ Fi.CI.BAT: failure " 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=b204fa15-e193-41ba-8b75-afbfebaeaff4@intel.com \
--to=swati2.sharma@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=suraj.kandpal@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.