From: Ankit Nautiyal <ankit.k.nautiyal@intel.com>
To: igt-dev@lists.freedesktop.org
Subject: [igt-dev] [Patch][i-g-t v2 0/3] Add support to detect HDCP events
Date: Tue, 23 Jun 2020 16:02:51 +0530 [thread overview]
Message-ID: <20200623103254.20921-1-ankit.k.nautiyal@intel.com> (raw)
This patch-series modifies the igt_kms to add support to detect
connector events. This support is then used for detecting
HDCP events in kms_content_protection.
Third patch, renames the APIs to have generic names.
Ankit Nautiyal (3):
lib/igt_kms: Add support for detecting connector events
tests/kms_content_protection: Use library functions for handling
uevents
lib: Use generic names for APIs that handle uevents
lib/igt_kms.c | 89 +++++++++++++-------
lib/igt_kms.h | 8 +-
tests/kms_chamelium.c | 40 ++++-----
tests/kms_content_protection.c | 146 ++-------------------------------
tests/kms_lease.c | 6 +-
5 files changed, 95 insertions(+), 194 deletions(-)
--
2.17.1
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next reply other threads:[~2020-06-23 10:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 10:32 Ankit Nautiyal [this message]
2020-06-23 10:32 ` [igt-dev] [Patch][i-g-t v2 1/3] lib/igt_kms: Add support for detecting connector events Ankit Nautiyal
2020-06-23 11:50 ` Ramalingam C
2020-06-23 13:37 ` Nautiyal, Ankit K
2020-06-23 10:32 ` [igt-dev] [Patch][i-g-t v2 2/3] tests/kms_content_protection: Use library functions for handling uevents Ankit Nautiyal
2020-06-23 11:57 ` Ramalingam C
2020-06-23 10:32 ` [igt-dev] [Patch][i-g-t v2 3/3] lib: Use generic names for APIs that handle uevents Ankit Nautiyal
2020-06-23 11:58 ` Ramalingam C
2020-06-23 11:29 ` [igt-dev] ✗ Fi.CI.BUILD: failure for Add support to detect HDCP events (rev2) 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=20200623103254.20921-1-ankit.k.nautiyal@intel.com \
--to=ankit.k.nautiyal@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