[igt-dev] [V5 i-g-t 40/81] tests/kms_content_protection: Document each subtest for testplan

[Karthik B S]

Hi,

On 6/29/2023 8:18 PM, Bhanuprakash Modem wrote:
> Add documentation for all kms tests which is used by IGT testplan
> documentation.
>
> Signed-off-by: Bhanuprakash Modem <bhanuprakash.modem at intel.com>
> ---
>   tests/kms_content_protection.c | 81 ++++++++++++++++++++++++++++++++++
>   1 file changed, 81 insertions(+)
>
> diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
> index 6cdf81a28..50929d8d5 100644
> --- a/tests/kms_content_protection.c
> +++ b/tests/kms_content_protection.c
> @@ -22,6 +22,11 @@
>    *
>    */
>   
> +/**
> + * TEST: kms content protection
> + * Category: Display
> + * Description: Test content protection (HDCP)
> + */
>   #include <poll.h>
>   #include <fcntl.h>
>   #include <sys/epoll.h>
> @@ -485,6 +490,66 @@ test_fini(igt_output_t *output, enum igt_commit_style s)
>   	igt_display_commit2(&data.display, s);
>   }
>   
> +/**
> + * SUBTEST: LIC
> + * Description: Test for the integrity of link.
> + * Driver requirement: any
> + * Functionality: hdcp
> + * Mega feature: HDCP
> + * Run type: FULL
> + * Test category: functionality test
> + *
> + * SUBTEST: content_type_change
> + * Description: Test the content type change when the content protection already
> + *              enabled
> + * Driver requirement: any
> + * Functionality: hdcp, hdcp2.2
> + * Mega feature: HDCP
> + * Run type: FULL
> + * Test category: functionality test
> + *
> + * SUBTEST: mei_interface
> + * Description: Test the teardown and rebuild of the interface between Intel
> + *              and mei hdcp.
> + * Driver requirement: any
> + * Functionality: hdcp, hdcp2.2

Since we're explicitly mentioning HDCP2.2, could/should the other 
component be hdcp1.4 instead of just hdcp?

Thanks,
Karthik.B.S
> + * Mega feature: HDCP
> + * Run type: FULL
> + * Test category: functionality test
> + *
> + * SUBTEST: srm
> + * Description: This test writes the facsimile SRM into the /lib/firmware/ and
> + *              check the kernel parsing of it by invoking the hdcp authentication.
> + * Driver requirement: any
> + * Functionality: hdcp
> + * Mega feature: HDCP
> + * Run type: FULL
> + * Test category: functionality test
> + *
> + * SUBTEST: uevent
> + * Description: Test to detect the HDCP status change when we are reading the
> + *              uevent sent with the corresponding connector id and property id.
> + * Driver requirement: any
> + * Functionality: hdcp
> + * Mega feature: HDCP
> + * Run type: FULL
> + * Test category: functionality test
> + *
> + * SUBTEST: %s
> + * Description: Test content protection with %arg[1]
> + * Driver requirement: any
> + * Functionality: hdcp
> + * Mega feature: HDCP
> + * Run type: FULL
> + * Test category: functionality test
> + *
> + * arg[1]:
> + *
> + * @atomic:         atomic modesetting
> + * @atomic-dpms:    DPMS ON/OFF during atomic modesetting.
> + * @legacy:         legacy style commit
> + * @type1:          content type 1 that can be handled only through HDCP2.2.
> + */
>   static void
>   test_content_protection(enum igt_commit_style s, int content_type)
>   {
> @@ -602,6 +667,22 @@ static void test_cp_lic_on_mst(igt_output_t *mst_outputs[], int valid_outputs, b
>   	}
>   }
>   
> +/**
> + * SUBTEST: dp-mst-%s
> + * Description: Test Content protection %arg[1] over DP MST.
> + * Driver requirement: any
> + * Functionality: hdcp
> + * Mega feature: HDCP
> + * Run type: FULL
> + * Test category: functionality test
> + *
> + * arg[1]:
> + *
> + * @lic-type-0:   Type 0 with LIC
> + * @lic-type-1:   Type 1 with LIC.
> + * @type-0:       Type 0
> + * @type-1:       Type 1
> + */
>   static void
>   test_content_protection_mst(int content_type)
>   {