From: Ramalingam C <ramalingam.c@intel.com>
To: igt-dev <igt-dev@lists.freedesktop.org>
Cc: Daniel Vetter <daniel@ffwll.ch>
Subject: [igt-dev] [PATCH i-g-t] tests/kms_content_protection: disable hdcp if uevent test fails
Date: Tue, 13 Aug 2019 09:29:06 +0530 [thread overview]
Message-ID: <20190813035906.22064-1-ramalingam.c@intel.com> (raw)
Though uevent test failed we can't assert there itself. we need to
disable the hdcp before exit.
Hence uevent failure is treated as hdcp enable failure and passed
to the caller to set the UNDESIRED to the property before exit..
Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=111390
---
tests/kms_content_protection.c | 7 +++++--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/tests/kms_content_protection.c b/tests/kms_content_protection.c
index e676b60bf719..46473d8893a8 100644
--- a/tests/kms_content_protection.c
+++ b/tests/kms_content_protection.c
@@ -251,9 +251,12 @@ wait_for_prop_value(igt_output_t *output, uint64_t expected,
int i;
if (data.cp_tests & CP_UEVENT && expected != CP_UNDESIRED) {
- igt_assert_f(wait_for_hdcp_event(output->id,
+ if (!wait_for_hdcp_event(output->id,
output->props[IGT_CONNECTOR_CONTENT_PROTECTION],
- timeout_mSec), "uevent is not received");
+ timeout_mSec)) {
+ igt_info("uevent is not received\n");
+ return false;
+ }
val = igt_output_get_prop(output,
IGT_CONNECTOR_CONTENT_PROTECTION);
--
2.20.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2019-08-13 10:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 3:59 Ramalingam C [this message]
2019-08-13 11:22 ` [igt-dev] ✓ Fi.CI.BAT: success for tests/kms_content_protection: disable hdcp if uevent test fails Patchwork
2019-08-13 18:23 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20190813035906.22064-1-ramalingam.c@intel.com \
--to=ramalingam.c@intel.com \
--cc=daniel@ffwll.ch \
--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