All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramalingam C <ramalingam.c@intel.com>
To: intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel <dri-devel@lists.freedesktop.org>,
	Daniel Vetter <daniel@ffwll.ch>
Subject: [PATCH v9 0/6] HDCP2.2 Phase II
Date: Mon,  8 Jul 2019 16:51:10 +0530	[thread overview]
Message-ID: <20190708112116.1780-1-ramalingam.c@intel.com> (raw)

Adding the uAPI support for the HDCP content type is the main focus
here. Along with that uevent is implemented for the
"Content Protection" state change that got triggered by kernel.

v9:
  KDoc improvements [pekka]

Ramalingam C (6):
  drm: Add Content protection type property
  drm/i915: Attach content type property
  drm: uevent for connector status change
  drm/hdcp: update content protection property with uevent
  drm/i915: update the hdcp state with uevent
  drm/hdcp: reference for srm file format

 drivers/gpu/drm/drm_atomic_uapi.c         |  4 ++
 drivers/gpu/drm/drm_connector.c           | 56 +++++++++++++++--
 drivers/gpu/drm/drm_hdcp.c                | 77 ++++++++++++++++++++++-
 drivers/gpu/drm/drm_sysfs.c               | 35 +++++++++++
 drivers/gpu/drm/i915/display/intel_ddi.c  | 39 ++++++++++--
 drivers/gpu/drm/i915/display/intel_hdcp.c | 53 ++++++++++------
 drivers/gpu/drm/i915/display/intel_hdcp.h |  2 +-
 include/drm/drm_connector.h               |  7 +++
 include/drm/drm_hdcp.h                    |  4 +-
 include/drm/drm_mode_config.h             |  6 ++
 include/drm/drm_sysfs.h                   |  5 +-
 include/uapi/drm/drm_mode.h               |  4 ++
 12 files changed, 258 insertions(+), 34 deletions(-)

-- 
2.19.1

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

             reply	other threads:[~2019-07-08 11:21 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08 11:21 Ramalingam C [this message]
2019-07-08 11:21 ` [PATCH v9 1/6] drm: Add Content protection type property Ramalingam C
2019-07-09 14:31   ` Pekka Paalanen
2019-07-09 12:47     ` Ramalingam C
2019-07-10  8:16       ` Pekka Paalanen
2019-07-11  5:50         ` Ramalingam C
2019-07-12 11:11           ` Pekka Paalanen
2019-07-12  4:43             ` Ramalingam C
2019-07-11 14:18   ` [Intel-gfx] " Sean Paul
2019-07-11 23:38     ` Ramalingam C
2019-07-12 11:39     ` Pekka Paalanen
2019-07-16 20:44       ` Sean Paul
2019-07-08 11:21 ` [PATCH v9 2/6] drm/i915: Attach content " Ramalingam C
2019-07-08 11:21 ` [PATCH v9 3/6] drm: uevent for connector status change Ramalingam C
2019-07-11 15:32   ` [Intel-gfx] " Sean Paul
2019-07-08 11:21 ` [PATCH v9 4/6] drm/hdcp: update content protection property with uevent Ramalingam C
2019-07-09 14:39   ` Pekka Paalanen
2019-07-08 11:21 ` [PATCH v9 5/6] drm/i915: update the hdcp state " Ramalingam C
2019-07-08 11:21 ` [PATCH v9 6/6] drm/hdcp: reference for srm file format Ramalingam C
2019-07-08 18:26 ` ✗ Fi.CI.CHECKPATCH: warning for HDCP2.2 Phase II (rev11) Patchwork
2019-07-08 18:43 ` ✓ Fi.CI.BAT: success " Patchwork
2019-07-09  7:08 ` ✓ 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=20190708112116.1780-1-ramalingam.c@intel.com \
    --to=ramalingam.c@intel.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.