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 v8 0/8] HDCP2.2 Tests
Date: Wed, 3 Jul 2019 13:32:17 +0530 [thread overview]
Message-ID: <20190703080225.10915-1-ramalingam.c@intel.com> (raw)
This series adds tests for:
1. content_type which is added for HDCP2.2.
Adds a new test for Type1.
2. Adds another test for Type1 -> Type0.
3. teardown and rebuild of i915-mei interface.
Removes the mei_hdcp and reloads it and test for HDCP2.2.
4. Test for SRM write and kernel validation
5 Link Integrity check is converted as a separate subtest
6. Subtest is added to test the uevent for HDCP state change.
v8:
Failure to receive the uevent is handled as a failure [uma]
captured all r-b received from reviewers.
Thanks Uma and Daniel for the review. With this, if ci is happy, we can
merge the series.
Ramalingam C (8):
kms_content_protection: Tests are defined by flags
kms_content_protection: Link Integrity Check subtest
kms_content_protection: Content type support
kms_content_protection: test teardown and rebuild of I915-mei I/F
kms_content_protection: test content type change
kms_content_protection: uevent for HDCP status change
kms_content_protection: SRM Testing
DO NOT MERGE: CP in fast feedback list
lib/igt_kms.c | 1 +
lib/igt_kms.h | 1 +
tests/intel-ci/fast-feedback.testlist | 3 +
tests/kms_content_protection.c | 365 ++++++++++++++++++++++++--
4 files changed, 348 insertions(+), 22 deletions(-)
--
2.19.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2019-07-03 15:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-03 8:02 Ramalingam C [this message]
2019-07-03 8:02 ` [igt-dev] [PATCH i-g-t v8 1/8] kms_content_protection: Tests are defined by flags Ramalingam C
2019-07-03 8:02 ` [igt-dev] [PATCH i-g-t v8 2/8] kms_content_protection: Link Integrity Check subtest Ramalingam C
2019-07-03 8:02 ` [igt-dev] [PATCH i-g-t v8 3/8] kms_content_protection: Content type support Ramalingam C
2019-07-03 8:02 ` [igt-dev] [PATCH i-g-t v8 4/8] kms_content_protection: test teardown and rebuild of I915-mei I/F Ramalingam C
2019-07-03 8:02 ` [igt-dev] [PATCH i-g-t v8 5/8] kms_content_protection: test content type change Ramalingam C
2019-07-03 8:02 ` [igt-dev] [PATCH i-g-t v8 6/8] kms_content_protection: uevent for HDCP status change Ramalingam C
2019-07-03 8:02 ` [igt-dev] [PATCH i-g-t v8 7/8] kms_content_protection: SRM Testing Ramalingam C
2019-07-03 8:02 ` [igt-dev] [PATCH i-g-t v8 8/8] DO NOT MERGE: CP in fast feedback list Ramalingam C
2019-07-03 15:19 ` [igt-dev] ✗ Fi.CI.BAT: failure for HDCP2.2 Tests (rev8) Patchwork
2019-07-03 15:29 ` [igt-dev] ✗ GitLab.Pipeline: warning " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2019-07-03 9:54 [igt-dev] [PATCH i-g-t v8 0/8] HDCP2.2 Tests Ramalingam C
2019-08-06 11:04 ` 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=20190703080225.10915-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