From: Mark Yacoub <markyacoub@chromium.org>
To: dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>
Cc: seanpaul@chromium.org, dianders@chromium.org,
dmitry.baryshkov@linaro.org,
Mark Yacoub <markyacoub@chromium.org>,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 1/2] DRM: Create new Content Protection connector property
Date: Fri, 21 Apr 2023 12:12:36 -0400 [thread overview]
Message-ID: <20230421161237.357342-2-markyacoub@google.com> (raw)
In-Reply-To: <20230421161237.357342-1-markyacoub@google.com>
From: Mark Yacoub <markyacoub@chromium.org>
[Why]
To enable Protected Content, some drivers require a key to be injected
from user space to enable HDCP on the connector.
[How]
Create new "Content Protection Property" of type "Blob"
Signed-off-by: Mark Yacoub <markyacoub@chromium.org>
---
drivers/gpu/drm/drm_atomic_uapi.c | 9 +++++++++
include/drm/drm_connector.h | 6 ++++++
include/drm/drm_mode_config.h | 6 ++++++
3 files changed, 21 insertions(+)
diff --git a/drivers/gpu/drm/drm_atomic_uapi.c b/drivers/gpu/drm/drm_atomic_uapi.c
index d867e7f9f2cd5..e20bc57cdb05c 100644
--- a/drivers/gpu/drm/drm_atomic_uapi.c
+++ b/drivers/gpu/drm/drm_atomic_uapi.c
@@ -749,6 +749,11 @@ static int drm_atomic_connector_set_property(struct drm_connector *connector,
state->content_protection = val;
} else if (property == config->hdcp_content_type_property) {
state->hdcp_content_type = val;
+ } else if (property == config->content_protection_key_property) {
+ ret = drm_atomic_replace_property_blob_from_id(
+ dev, &state->content_protection_key, val, -1, -1,
+ &replaced);
+ return ret;
} else if (property == connector->colorspace_property) {
state->colorspace = val;
} else if (property == config->writeback_fb_id_property) {
@@ -843,6 +848,10 @@ drm_atomic_connector_get_property(struct drm_connector *connector,
*val = state->content_protection;
} else if (property == config->hdcp_content_type_property) {
*val = state->hdcp_content_type;
+ } else if (property == config->content_protection_key_property) {
+ *val = state->content_protection_key ?
+ state->content_protection_key->base.id :
+ 0;
} else if (property == config->writeback_fb_id_property) {
/* Writeback framebuffer is one-shot, write and forget */
*val = 0;
diff --git a/include/drm/drm_connector.h b/include/drm/drm_connector.h
index 7b5048516185c..2fbe51272bfeb 100644
--- a/include/drm/drm_connector.h
+++ b/include/drm/drm_connector.h
@@ -896,6 +896,12 @@ struct drm_connector_state {
*/
unsigned int content_protection;
+ /**
+ * @content_protection_key: DRM blob property for holding the Content
+ * Protection Key injected from user space.
+ */
+ struct drm_property_blob *content_protection_key;
+
/**
* @colorspace: State variable for Connector property to request
* colorspace change on Sink. This is most commonly used to switch
diff --git a/include/drm/drm_mode_config.h b/include/drm/drm_mode_config.h
index e5b053001d22e..615d1e5f57562 100644
--- a/include/drm/drm_mode_config.h
+++ b/include/drm/drm_mode_config.h
@@ -887,6 +887,12 @@ struct drm_mode_config {
*/
struct drm_property *hdcp_content_type_property;
+ /**
+ * @content_protection_key_property: DRM blob property that receives the
+ * content protection key from user space to be injected into the kernel.
+ */
+ struct drm_property *content_protection_key_property;
+
/* dumb ioctl parameters */
uint32_t preferred_depth, prefer_shadow;
--
2.40.0.634.g4ca3ef3211-goog
next parent reply other threads:[~2023-04-21 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230421161237.357342-1-markyacoub@google.com>
2023-04-21 16:12 ` Mark Yacoub [this message]
2023-04-21 16:12 ` [PATCH v1 2/2] dp_hdcp: Get the hdcp key from the connector prop Mark Yacoub
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=20230421161237.357342-2-markyacoub@google.com \
--to=markyacoub@chromium.org \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dianders@chromium.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=seanpaul@chromium.org \
--cc=tzimmermann@suse.de \
/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