From: Ramalingam C <ramalingam.c@intel.com>
To: intel-gfx@lists.freedesktop.org, daniel.vetter@ffwll.ch,
maarten.lankhorst@linux.intel.com
Subject: [PATCH v2 0/2] HDCP2.2 Content Type support
Date: Fri, 8 Mar 2019 22:06:05 +0530 [thread overview]
Message-ID: <20190308163607.9277-1-ramalingam.c@intel.com> (raw)
This series adds a property called Content_protection_type
onto HDCP2.2 capable intel connectors.
Using this property userspace app can set the Content Type
of the stream as per HDCP2.2 specification.
v2:
Separated from the other patches for SRM and Downstream_info
Restrictions at atomic_set_property is removed [Maarten]
CP appreviation is expanded [Daniel]
kernel does HDCP restart when type change is requested when CP is on.
Needed to remove the restriction of at atomic_set_property.
Test-with: 20190308163049.9016-2-ramalingam.c@intel.com
Ramalingam C (2):
drm: Add Content protection type property
drm/i915: Attach content type property
drivers/gpu/drm/drm_atomic_uapi.c | 4 ++
drivers/gpu/drm/drm_connector.c | 63 +++++++++++++++++++++++++++++++
drivers/gpu/drm/i915/intel_ddi.c | 21 ++++++++---
drivers/gpu/drm/i915/intel_drv.h | 2 +-
drivers/gpu/drm/i915/intel_hdcp.c | 30 ++++++++++++---
include/drm/drm_connector.h | 15 ++++++++
include/uapi/drm/drm_mode.h | 4 ++
7 files changed, 127 insertions(+), 12 deletions(-)
--
2.19.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2019-03-08 16:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 16:36 Ramalingam C [this message]
2019-03-08 16:36 ` [PATCH v2 1/2] drm: Add Content protection type property Ramalingam C
2019-03-08 16:36 ` [PATCH v2 2/2] drm/i915: Attach content " Ramalingam C
2019-03-08 16:45 ` [PATCH v2 1/8] drm/i915: debugfs: HDCP2.2 capability read Ramalingam C
2019-03-08 16:52 ` ✗ Fi.CI.BAT: failure for HDCP2.2 Content Type support 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=20190308163607.9277-1-ramalingam.c@intel.com \
--to=ramalingam.c@intel.com \
--cc=daniel.vetter@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.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