Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Sharma, Swati2" <swati2.sharma@intel.com>
To: "Nautiyal, Ankit K" <ankit.k.nautiyal@intel.com>,
	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: Tue, 16 Jan 2024 15:18:37 +0530	[thread overview]
Message-ID: <cee84e7f-e739-4db9-a104-a9a80799a765@intel.com> (raw)
In-Reply-To: <89c29c53-e4b9-403b-826b-a681bad2d9ab@intel.com>

Hi Suraj,

On 16-Jan-24 3:04 PM, Nautiyal, Ankit K wrote:
> LGTM.
> 
> Reviewed-by: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
> 
> On 1/12/2024 4:03 PM, Suraj Kandpal wrote:
>> Currently LIC is done only for type0 content this patch
>> adds LIC for type1 content too.
>>
>> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
>> ---
>>   tests/kms_content_protection.c | 16 ++++++++++++----
>>   1 file changed, 12 insertions(+), 4 deletions(-)
>>
>> diff --git a/tests/kms_content_protection.c 
>> b/tests/kms_content_protection.c
>> index 6d472ee02..38e4143c8 100644
>> --- a/tests/kms_content_protection.c
>> +++ b/tests/kms_content_protection.c
>> @@ -43,8 +43,11 @@
>>   #include "igt_kmod.h"
>>   /**
>> - * SUBTEST: lic
>> - * Description: Test for the integrity of link.
>> + * SUBTEST: lic-type-0
>> + * Description: Test for the integrity of link for type 0 content.
>> + *
>> + * SUBTEST: lic-type-1
>> + * Description: Test for the integrity of link for type 1 content.
>>    *

Instead if writing description like this you can add
lic-%arg[1]

@arg[1]:
@type0:		type-0
@type1:		type-1

Check this 
https://gitlab.freedesktop.org/drm/igt-gpu-tools/-/blob/master/docs/test_documentation.md?ref_type=heads

And functionality for both these tests will be hdcp1.4. Is this correct?
Or do we need to add hdcp2.2 too?
Please update functionality.

>>    * SUBTEST: content-type-change
>>    * Description: Test the content type change when the content 
>> protection already
>> @@ -783,11 +786,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",

  parent reply	other threads:[~2024-01-16  9:48 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 [this message]
2024-01-16  9:51     ` Kandpal, Suraj
2024-01-16 11:23 ` Suraj Kandpal
2024-01-17 11:28   ` Sharma, Swati2
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=cee84e7f-e739-4db9-a104-a9a80799a765@intel.com \
    --to=swati2.sharma@intel.com \
    --cc=ankit.k.nautiyal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox