From: Ramalingam C <ramalingam.c@intel.com>
To: igt-dev@lists.freedesktop.org, daniel.vetter@ffwll.ch
Subject: [igt-dev] [PATCH i-g-t 0/4] Coverage for HDCP2.2 Phase II
Date: Tue, 26 Feb 2019 12:53:21 +0530 [thread overview]
Message-ID: <1551165805-19130-1-git-send-email-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. teardown and rebuild of i915-mei interface.
Removes the mei_hdcp and reloads it and test for HDCP2.2.
3. downstream info gathering and SRM revocation.
Retrieves the receivers ID from downstream_info
fabricates a SRM and test for the revocation of the device.
Ramalingam C (4):
kms_content_protection: Content type support
kms_content_protection: test teardown and rebuild of I915-mei I/F
kms_content_protection: srm and downstream_info test
DO NOT MERGE: CP in fast feedback list
lib/igt_kms.c | 3 +
lib/igt_kms.h | 3 +
tests/intel-ci/fast-feedback.testlist | 3 +
tests/kms_content_protection.c | 292 ++++++++++++++++++++++++++++++++--
4 files changed, 284 insertions(+), 17 deletions(-)
--
2.7.4
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2019-02-26 7:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-26 7:23 Ramalingam C [this message]
2019-02-26 7:23 ` [igt-dev] [PATCH i-g-t 1/4] kms_content_protection: Content type support Ramalingam C
2019-02-26 7:23 ` [igt-dev] [PATCH i-g-t 2/4] kms_content_protection: test teardown and rebuild of I915-mei I/F Ramalingam C
2019-02-27 10:22 ` C, Ramalingam
2019-02-26 7:23 ` [igt-dev] [PATCH i-g-t 3/4] kms_content_protection: srm and downstream_info test Ramalingam C
2019-02-26 7:23 ` [igt-dev] [PATCH i-g-t 4/4] DO NOT MERGE: CP in fast feedback list Ramalingam C
2019-02-26 8:15 ` [igt-dev] ✓ Fi.CI.BAT: success for Coverage for HDCP2.2 Phase II Patchwork
2019-02-26 9:49 ` [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=1551165805-19130-1-git-send-email-ramalingam.c@intel.com \
--to=ramalingam.c@intel.com \
--cc=daniel.vetter@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