kms_content_protection: Add Content Protection test

Pretty simple test:
- picks the hdcp capable output with suitable pipe and apply modeset.
- checks the connected sink's hdcp capability through debugfs
- apply a FB and wait for the flip completion.
- clears the content protection property
- verifies that it clears
- sets the content protection property to desired
- verifies that it transitions to enabled
- incase of timeout three reattempts are implemented
- clear the content protection property and modeset on the crtc

Above steps are repeated on all HDCP capable connectors for both
legacy and atomic subtests.

v2:
  dynamic subtests are dropped [Daniel]
v3:
  debugfs is used to detect the sink's hdcp capability [Daniel]
  data structure is made as global variable.
v4:
  debugfs file from connector's debugfs dir is used [Daniel]
v5:
  i915_debugfs_connector_dir() usage is modified [Chris]

Signed-off-by: Sean Paul <seanpaul@chromium.org>
Signed-off-by: Ramalingam C <ramalingam.c@intel.com>
Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>

1 files changed, 1 insertions, 0 deletions

diff --git a/lib/igt_kms.h b/lib/igt_kms.h
index cbfcced9..e6aff339 100644
--- a/lib/igt_kms.h
+++ b/lib/igt_kms.h
@@ -120,6 +120,7 @@ enum igt_atomic_connector_properties {
        IGT_CONNECTOR_CRTC_ID,
        IGT_CONNECTOR_DPMS,
        IGT_CONNECTOR_BROADCAST_RGB,
+       IGT_CONNECTOR_CONTENT_PROTECTION,
        IGT_NUM_CONNECTOR_PROPS
 };