[PATCH i-g-t] tests/kms_content_protection: Add LIC Type 1 scenario
Sharma, Swati2
swati2.sharma at intel.com
Wed Jan 17 11:28:30 UTC 2024
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 at intel.com>
> Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal at 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",
More information about the igt-dev
mailing list