From: Daniel Vetter <daniel@ffwll.ch>
To: Ramalingam C <ramalingam.c@intel.com>
Cc: igt-dev@lists.freedesktop.org, daniel.vetter@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t v5 0/6] HDCP2.2 Tests
Date: Mon, 29 Apr 2019 17:24:59 +0200 [thread overview]
Message-ID: <20190429152459.GR3271@phenom.ffwll.local> (raw)
In-Reply-To: <20190418084842.5422-1-ramalingam.c@intel.com>
On Thu, Apr 18, 2019 at 02:18:36PM +0530, Ramalingam C wrote:
> This series adds tests for:
> 1. content_type which is added for HDCP2.2.
> Adds a new test for Type1.
> Adds another test for Type1 -> Type0.
> 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.
>
> Wait for HDCP state change is implemented through the uevent handler.
>
> v5:
> srm is written into /lib/firmware/display_hdcp_srm.bin [Danvet]
>
> Ramalingam C (6):
> 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 and topology_info test
Looks good, made some comments, with those addressed entire series has my
Acked-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> DO NOT MERGE: CP in fast feedback list
>
> lib/igt_kms.c | 2 +
> lib/igt_kms.h | 2 +
> tests/intel-ci/fast-feedback.testlist | 3 +
> tests/kms_content_protection.c | 498 ++++++++++++++++++++++++--
> 4 files changed, 477 insertions(+), 28 deletions(-)
>
> --
> 2.19.1
>
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
prev parent reply other threads:[~2019-04-29 15:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-18 8:48 [igt-dev] [PATCH i-g-t v5 0/6] HDCP2.2 Tests Ramalingam C
2019-04-18 8:48 ` [igt-dev] [PATCH i-g-t v5 1/6] kms_content_protection: Content type support Ramalingam C
2019-04-18 8:48 ` [igt-dev] [PATCH i-g-t v5 2/6] kms_content_protection: test teardown and rebuild of I915-mei I/F Ramalingam C
2019-04-18 8:48 ` [igt-dev] [PATCH i-g-t v5 3/6] kms_content_protection: test content type change Ramalingam C
2019-04-29 14:40 ` Daniel Vetter
2019-04-30 12:41 ` Ramalingam C
2019-04-18 8:48 ` [igt-dev] [PATCH i-g-t v5 4/6] kms_content_protection: uevent for HDCP status change Ramalingam C
2019-04-29 15:17 ` Daniel Vetter
2019-04-18 8:48 ` [igt-dev] [PATCH i-g-t v5 5/6] kms_content_protection: srm and topology_info test Ramalingam C
2019-04-29 15:24 ` Daniel Vetter
2019-04-30 12:33 ` Ramalingam C
2019-04-18 8:48 ` [igt-dev] [PATCH i-g-t v5 6/6] DO NOT MERGE: CP in fast feedback list Ramalingam C
2019-04-18 9:54 ` [igt-dev] ✓ Fi.CI.BAT: success for HDCP2.2 Tests (rev5) Patchwork
2019-04-18 11:38 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-04-29 15:24 ` Daniel Vetter [this message]
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=20190429152459.GR3271@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=daniel.vetter@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=ramalingam.c@intel.com \
/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