From: Jani Nikula <jani.nikula@intel.com>
To: Ramalingam C <ramalingam.c@intel.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v12 0/6] HDCP2.2 Phase II
Date: Mon, 05 Aug 2019 11:09:11 +0300 [thread overview]
Message-ID: <87d0hkkp94.fsf@intel.com> (raw)
In-Reply-To: <20190801114119.28830-1-ramalingam.c@intel.com>
On Thu, 01 Aug 2019, Ramalingam C <ramalingam.c@intel.com> wrote:
> Series adds the content_type support for HDCP2.2. Along with that uevent
> is sent for each HDCP state change triggered within kernel.
Acked-by: Jani Nikula <jani.nikula@intel.com>
For merging the i915 specific parts via drm-misc along the rest of the
patches.
>
> Pekka have completed the Weston DRM-backend review in
> https://gitlab.freedesktop.org/wayland/weston/merge_requests/48
> and the UAPI for HDCP 2.2 looks good.
>
> The userspace is accepted in Weston.
>
> v12:
> DRM_MODE_HDCP_CONTENT_TYPEx definition are moved into drm_hdcp.h
> [pekka]
> Picked Acked-by and R-by from reviewers.
>
> Test-with: <20190703095446.14092-2-ramalingam.c@intel.com>
>
> 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 | 68 ++++++++++++++++++--
> 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 | 9 ++-
> include/drm/drm_mode_config.h | 6 ++
> include/drm/drm_sysfs.h | 5 +-
> 11 files changed, 271 insertions(+), 34 deletions(-)
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2019-08-05 8:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-01 11:41 [PATCH v12 0/6] HDCP2.2 Phase II Ramalingam C
2019-08-01 11:41 ` [PATCH v12 1/6] drm: Add Content protection type property Ramalingam C
2019-08-01 11:41 ` [PATCH v12 2/6] drm/i915: Attach content " Ramalingam C
2019-08-01 11:41 ` [PATCH v12 3/6] drm: uevent for connector status change Ramalingam C
2019-08-01 11:41 ` [PATCH v12 4/6] drm/hdcp: update content protection property with uevent Ramalingam C
2019-08-01 11:41 ` [PATCH v12 5/6] drm/i915: update the hdcp state " Ramalingam C
2019-08-01 11:41 ` [PATCH v12 6/6] drm/hdcp: reference for srm file format Ramalingam C
2019-08-01 18:17 ` ✗ Fi.CI.CHECKPATCH: warning for HDCP2.2 Phase II (rev14) Patchwork
2019-08-01 18:43 ` ✗ Fi.CI.BAT: failure " Patchwork
2019-08-02 7:04 ` Ramalingam C
2019-08-14 12:17 ` Martin Peres
2019-08-05 8:09 ` Jani Nikula [this message]
2019-08-06 10:29 ` [PATCH v12 0/6] HDCP2.2 Phase II Ramalingam C
2019-08-14 14:30 ` ✗ Fi.CI.BAT: failure for HDCP2.2 Phase II (rev15) 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=87d0hkkp94.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@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;
as well as URLs for NNTP newsgroup(s).