From: Ramalingam C <ramalingam.c@intel.com>
To: Anshuman Gupta <anshuman.gupta@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] kms_content_protection: Set CP prop to UNDESIRED at igt exit
Date: Thu, 26 Sep 2019 10:31:10 +0530 [thread overview]
Message-ID: <20190926050110.GA28487@intel.com> (raw)
In-Reply-To: <20190926043129.11599-1-anshuman.gupta@intel.com>
On 2019-09-26 at 10:01:29 +0530, Anshuman Gupta wrote:
> We require to clear HDCP state to UNDESIRED at igt exit on
> every success/failure in order to avoid any HDCP operations in
> subsequent IGT tests.
>
> v2: commit message change.
Look good to me.
Reviewed-by: Ramalingam C <ramalingam.c@intel.com>
-Ram
>
> Cc: Ramalingam C <ramalingam.c@intel.com>
> Signed-off-by: Anshuman Gupta <anshuman.gupta@intel.com>
> ---
> tests/kms_content_protection.c | 24 +++++++++++++++++++++++-
> 1 file changed, 23 insertions(+), 1 deletion(-)
>
> diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
> index e676b60b..fce4b591 100644
> --- a/tests/kms_content_protection.c
> +++ b/tests/kms_content_protection.c
> @@ -617,6 +617,26 @@ test_content_protection(enum igt_commit_style s, int content_type)
> igt_require_f(valid_tests, "No connector found with HDCP capability\n");
> }
>
> +static void test_content_protection_cleanup(void)
> +{
> + igt_display_t *display = &data.display;
> + igt_output_t *output;
> + uint64_t val;
> +
> + for_each_connected_output(display, output) {
> + if (!output->props[IGT_CONNECTOR_CONTENT_PROTECTION])
> + continue;
> +
> + val = igt_output_get_prop(output,
> + IGT_CONNECTOR_CONTENT_PROTECTION);
> + if (val == CP_UNDESIRED)
> + continue;
> +
> + igt_info("CP Prop being UNDESIRED on %s\n", output->name);
> + test_cp_disable(output, COMMIT_ATOMIC);
> + }
> +}
> +
> igt_main
> {
> igt_fixture {
> @@ -692,6 +712,8 @@ igt_main
> test_content_protection(COMMIT_ATOMIC, HDCP_CONTENT_TYPE_0);
> }
>
> - igt_fixture
> + igt_fixture {
> + test_content_protection_cleanup();
> igt_display_fini(&data.display);
> + }
> }
> --
> 2.21.0
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-09-26 5:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-26 4:31 [igt-dev] [PATCH i-g-t] kms_content_protection: Set CP prop to UNDESIRED at igt exit Anshuman Gupta
2019-09-26 5:01 ` Ramalingam C [this message]
2019-10-09 18:35 ` Ramalingam C
2019-09-26 5:25 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-09-27 1:54 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-10-07 11:10 ` [igt-dev] ✓ Fi.CI.BAT: success for kms_content_protection: Set CP prop to UNDESIRED at igt exit (rev2) Patchwork
2019-10-07 12:25 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-10-09 10:36 ` Anshuman Gupta
2019-10-09 12:25 ` Vudum, Lakshminarayana
-- strict thread matches above, loose matches on Subject: below --
2019-09-23 11:04 [igt-dev] [PATCH i-g-t] kms_content_protection: Set CP prop to UNDESIRED at igt exit Anshuman Gupta
2019-09-23 12:37 ` Ramalingam C
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=20190926050110.GA28487@intel.com \
--to=ramalingam.c@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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;
as well as URLs for NNTP newsgroup(s).