drm/hdcp: Pull HDCP auth/exchange/check into helpers
Subsystems (9)
Sean Paul
reviewerv2 cover drm/hdcp: Pull HDCP auth/exchange/check into helpers
From: Sean Paul <[email protected]>
Hello again,
This is the second version of the HDCP helper patchset. See version 1
here: https://patchwork.freedesktop.org/series/94623/
In this second version, I've fixed up the oopsies exposed by 0-day and yamllint and incorporated early review feedback from the dt/dts reviews.
Please take a look,
Sean
Sean Paul (13):
drm/hdcp: Add drm_hdcp_atomic_check()
drm/hdcp: Avoid changing crtc state in hdcp atomic check drm/hdcp: Update property value on content type and user changes drm/hdcp: Expand HDCP helper library for enable/disable/check drm/i915/hdcp: Consolidate HDCP setup/state cache drm/i915/hdcp: Retain hdcp_capable return codes drm/i915/hdcp: Use HDCP helpers for i915 drm/msm/dpu_kms: Re-order dpu includes
drm/msm/dpu: Remove useless checks in dpu_encoder drm/msm/dpu: Remove encoder->enable() hack drm/msm/dp: Re-order dp_audio_put in deinit_sub_modules
dt-bindings: msm/dp: Add bindings for HDCP registers drm/msm: Implement HDCP 1.x using the new drm HDCP helpers
.../bindings/display/msm/dp-controller.yaml | 7 +- arch/arm64/boot/dts/qcom/sc7180.dtsi | 4 +- drivers/gpu/drm/drm_hdcp.c | 1197 ++++++++++++++++- drivers/gpu/drm/i915/display/intel_atomic.c | 7 +- drivers/gpu/drm/i915/display/intel_ddi.c | 29 +- .../drm/i915/display/intel_display_debugfs.c | 11 +- .../drm/i915/display/intel_display_types.h | 58 +- drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 345 ++--- drivers/gpu/drm/i915/display/intel_dp_mst.c | 17 +- drivers/gpu/drm/i915/display/intel_hdcp.c | 1011 +++----------- drivers/gpu/drm/i915/display/intel_hdcp.h | 35 +- drivers/gpu/drm/i915/display/intel_hdmi.c | 256 ++-- drivers/gpu/drm/msm/Makefile | 1 + drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 17 +- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 30 +- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 2 - drivers/gpu/drm/msm/disp/dpu1/dpu_trace.h | 4 - drivers/gpu/drm/msm/dp/dp_debug.c | 49 +- drivers/gpu/drm/msm/dp/dp_debug.h | 6 +- drivers/gpu/drm/msm/dp/dp_display.c | 47 +- drivers/gpu/drm/msm/dp/dp_display.h | 5 + drivers/gpu/drm/msm/dp/dp_drm.c | 68 +- drivers/gpu/drm/msm/dp/dp_drm.h | 5 + drivers/gpu/drm/msm/dp/dp_hdcp.c | 433 ++++++ drivers/gpu/drm/msm/dp/dp_hdcp.h | 27 + drivers/gpu/drm/msm/dp/dp_parser.c | 22 +- drivers/gpu/drm/msm/dp/dp_parser.h | 4 + drivers/gpu/drm/msm/dp/dp_reg.h | 44 +- drivers/gpu/drm/msm/msm_atomic.c | 15 + include/drm/drm_hdcp.h | 194 +++ 30 files changed, 2561 insertions(+), 1389 deletions(-) create mode 100644 drivers/gpu/drm/msm/dp/dp_hdcp.c create mode 100644 drivers/gpu/drm/msm/dp/dp_hdcp.h
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Sean Paul
reviewerPATCH v2 1/13 drm/hdcp: Add drm_hdcp_atomic_check()
From: Sean Paul <[email protected]>
This patch moves the hdcp atomic check from i915 to drm_hdcp so other drivers can use it. No functional changes, just cleaned up some of the code when moving it over.
Changes in v2:
-None
--- drivers/gpu/drm/drm_hdcp.c | 71 ++++++++++++++++++++- drivers/gpu/drm/i915/display/intel_atomic.c | 4 +- drivers/gpu/drm/i915/display/intel_hdcp.c | 47 -------------- drivers/gpu/drm/i915/display/intel_hdcp.h | 3 - include/drm/drm_hdcp.h | 3 + 5 files changed, 75 insertions(+), 53 deletions(-)
drivers/gpu/drm/drm_hdcp.c +70 -1
@@ -13,13 +13,14 @@#include <linux/slab.h> #include <linux/firmware.h> +#include <drm/drm_atomic.h> +#include <drm/drm_connector.h> #include <drm/drm_hdcp.h> #include <drm/drm_sysfs.h> #include <drm/drm_print.h> #include <drm/drm_device.h> #include <drm/drm_property.h> #include <drm/drm_mode_object.h> -#include <drm/drm_connector.h> #include "drm_internal.h"
@@ -421,3 +422,71 @@ void drm_hdcp_update_content_protection(struct drm_connector *connector, dev->mode_config.content_protection_property); }EXPORT_SYMBOL (drm_hdcp_update_content_protection); + +/** +* drm_hdcp_atomic_check - Helper for drivers to call during connector->atomic_check +* +* @state: pointer to the atomic state being checked +* @connector: drm_connector on which content protection state needs an update +* +* This function can be used by display drivers to perform an atomic check on the +* hdcp state elements. If hdcp state has changed, this function will set +* mode_changed on the crtc driving the connector so it can update its hardware +* to match the hdcp state. +*/ +void drm_hdcp_atomic_check (struct drm_connector *connector, +struct drm_atomic_state *state) +{ +struct drm_connector_state *new_conn_state, *old_conn_state; +struct drm_crtc_state *new_crtc_state; +u64 old_hdcp, new_hdcp; + + old_conn_state =drm_atomic_get_old_connector_state (state, connector); + old_hdcp = old_conn_state->content_protection; + + new_conn_state =drm_atomic_get_new_connector_state (state, connector); + new_hdcp = new_conn_state->content_protection; + +if (!new_conn_state->crtc) { +/* +* If the connector is being disabled with CP enabled, mark it +* desired so it's re-enabled when the connector is brought back +*/ +if (old_hdcp ==DRM_MODE_CONTENT_PROTECTION_ENABLED ) + new_conn_state->content_protection = +DRM_MODE_CONTENT_PROTECTION_DESIRED ; +return ; + } + + new_crtc_state =drm_atomic_get_new_crtc_state (state, + new_conn_state->crtc); +/* +* Fix the HDCP uapi content protection state in case of modeset. +* FIXME: As per HDCP content protection property uapi doc, an uevent() +* need to be sent if there is transition from ENABLED->DESIRED. +*/ +if (drm_atomic_crtc_needs_modeset (new_crtc_state) && + (old_hdcp ==DRM_MODE_CONTENT_PROTECTION_ENABLED && + new_hdcp !=DRM_MODE_CONTENT_PROTECTION_UNDESIRED )) + new_conn_state->content_protection = +DRM_MODE_CONTENT_PROTECTION_DESIRED ; + +/* +* Nothing to do if content type is unchanged and one of: +* - state didn't change +* - HDCP was activated since the last commit +* - attempting to set to desired while already enabled +*/ +if (old_hdcp == new_hdcp || + (old_hdcp ==DRM_MODE_CONTENT_PROTECTION_DESIRED && + new_hdcp ==DRM_MODE_CONTENT_PROTECTION_ENABLED ) || + (old_hdcp ==DRM_MODE_CONTENT_PROTECTION_ENABLED && + new_hdcp ==DRM_MODE_CONTENT_PROTECTION_DESIRED )) { +if (old_conn_state->hdcp_content_type == + new_conn_state->hdcp_content_type) +return ; + } + + new_crtc_state->mode_changed = true; +} +EXPORT_SYMBOL (drm_hdcp_atomic_check);
drivers/gpu/drm/i915/display/intel_atomic.c +2 -2
@@ -32,13 +32,13 @@#include <drm/drm_atomic.h> #include <drm/drm_atomic_helper.h> #include <drm/drm_fourcc.h> +#include <drm/drm_hdcp.h> #include <drm/drm_plane_helper.h> #include "intel_atomic.h" #include "intel_cdclk.h" #include "intel_display_types.h" #include "intel_global_state.h" -#include "intel_hdcp.h" #include "intel_psr.h" #include "skl_universal_plane.h"
@@ -122,7 +122,7 @@ int intel_digital_connector_atomic_check(struct drm_connector *conn,to_intel_digital_connector_state (old_state);struct drm_crtc_state *crtc_state; -intel_hdcp_atomic_check (conn, old_state, new_state); +drm_hdcp_atomic_check (conn, state);if (!new_state->crtc)return 0 ;
drivers/gpu/drm/i915/display/intel_hdcp.c +0 -47
53 lines not on this page · raw message
drivers/gpu/drm/i915/display/intel_hdcp.h +0 -3
@@ -22,9 +22,6 @@ struct intel_digital_port;enum port ;enum transcoder ; -void intel_hdcp_atomic_check (struct drm_connector *connector, -struct drm_connector_state *old_state, -struct drm_connector_state *new_state);int intel_hdcp_init (struct intel_connector *connector,struct intel_digital_port *dig_port,const struct intel_hdcp_shim *hdcp_shim);
include/drm/drm_hdcp.h +3 -0
@@ -291,6 +291,7 @@ struct hdcp_srm_header {u8 srm_gen_no; } __packed; +struct drm_atomic_state ;struct drm_device ;struct drm_connector ;
@@ -300,6 +301,8 @@ int drm_connector_attach_content_protection_property( struct drm_connector *connector, bool hdcp_content_type);void drm_hdcp_update_content_protection (struct drm_connector *connector,u64 val); +void drm_hdcp_atomic_check (struct drm_connector *connector, +struct drm_atomic_state *state);/* Content Type classification for HDCP2.2 vs others */ #define DRM_MODE_HDCP_CONTENT_TYPE0 0
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Sean Paul
reviewerPATCH v2 2/13 drm/hdcp: Avoid changing crtc state in hdcp atomic check
In reply to Sean PaulFrom: Sean Paul <[email protected]>
Instead of forcing a modeset in the hdcp atomic check, simply return true if the content protection value is changing and let the driver decide whether a modeset is required or not.
Changes in v2:
-None
--- drivers/gpu/drm/drm_hdcp.c | 33 +++++++++++++++------ drivers/gpu/drm/i915/display/intel_atomic.c | 5 ++-- include/drm/drm_hdcp.h | 2 +- 3 files changed, 27 insertions(+), 13 deletions(-)
drivers/gpu/drm/drm_hdcp.c +24 -9
@@ -430,11 +430,14 @@ EXPORT_SYMBOL(drm_hdcp_update_content_protection);* @connector: drm_connector on which content protection state needs an update * * This function can be used by display drivers to perform an atomic check on the -* hdcp state elements. If hdcp state has changed, this function will set -* mode_changed on the crtc driving the connector so it can update its hardware -* to match the hdcp state. +* hdcp state elements. If hdcp state has changed in a manner which requires the +* driver to enable or disable content protection, this function will return +* true. +* +* Returns: +* true if the driver must enable/disable hdcp, false otherwise */ -void drm_hdcp_atomic_check (struct drm_connector *connector, +bool drm_hdcp_atomic_check (struct drm_connector *connector,struct drm_atomic_state *state) {struct drm_connector_state *new_conn_state, *old_conn_state;
@@ -452,10 +455,12 @@ void drm_hdcp_atomic_check(struct drm_connector *connector,* If the connector is being disabled with CP enabled, mark it * desired so it's re-enabled when the connector is brought back */ -if (old_hdcp ==DRM_MODE_CONTENT_PROTECTION_ENABLED ) +if (old_hdcp ==DRM_MODE_CONTENT_PROTECTION_ENABLED ) { new_conn_state->content_protection =DRM_MODE_CONTENT_PROTECTION_DESIRED ; -return ; +return true; + } +return false; } new_crtc_state = drm_atomic_get_new_crtc_state(state,
@@ -467,9 +472,19 @@ void drm_hdcp_atomic_check(struct drm_connector *connector,*/ if (drm_atomic_crtc_needs_modeset (new_crtc_state) && (old_hdcp ==DRM_MODE_CONTENT_PROTECTION_ENABLED && - new_hdcp !=DRM_MODE_CONTENT_PROTECTION_UNDESIRED )) + new_hdcp !=DRM_MODE_CONTENT_PROTECTION_UNDESIRED )) { new_conn_state->content_protection =DRM_MODE_CONTENT_PROTECTION_DESIRED ; +return true; + } + +/* +* Coming back from disable or changing CRTC with DESIRED state requires +* that the driver try CP enable. +*/ +if (new_hdcp ==DRM_MODE_CONTENT_PROTECTION_DESIRED && + new_conn_state->crtc != old_conn_state->crtc) +return true;/* * Nothing to do if content type is unchanged and one of:
@@ -484,9 +499,9 @@ void drm_hdcp_atomic_check(struct drm_connector *connector, new_hdcp == DRM_MODE_CONTENT_PROTECTION_DESIRED)) {if (old_conn_state->hdcp_content_type == new_conn_state->hdcp_content_type) -return ; +return false; } - new_crtc_state->mode_changed = true; +return true; }EXPORT_SYMBOL (drm_hdcp_atomic_check);
drivers/gpu/drm/i915/display/intel_atomic.c +2 -3
@@ -122,8 +122,6 @@ int intel_digital_connector_atomic_check(struct drm_connector *conn,to_intel_digital_connector_state (old_state);struct drm_crtc_state *crtc_state; -drm_hdcp_atomic_check (conn, state); -if (!new_state->crtc)return 0 ;
@@ -139,7 +137,8 @@ int intel_digital_connector_atomic_check(struct drm_connector *conn, new_conn_state->base.picture_aspect_ratio != old_conn_state->base.picture_aspect_ratio || new_conn_state->base.content_type != old_conn_state->base.content_type || new_conn_state->base.scaling_mode != old_conn_state->base.scaling_mode || - !drm_connector_atomic_hdr_metadata_equal(old_state, new_state)) + !drm_connector_atomic_hdr_metadata_equal (old_state, new_state) || + drm_hdcp_atomic_check(conn, state)) crtc_state->mode_changed = true;return 0 ;
include/drm/drm_hdcp.h +1 -1
@@ -301,7 +301,7 @@ int drm_connector_attach_content_protection_property( struct drm_connector *connector, bool hdcp_content_type);void drm_hdcp_update_content_protection (struct drm_connector *connector,u64 val); -void drm_hdcp_atomic_check (struct drm_connector *connector, +bool drm_hdcp_atomic_check (struct drm_connector *connector,struct drm_atomic_state *state);/* Content Type classification for HDCP2.2 vs others */
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Sean Paul
reviewerPATCH v2 3/13 drm/hdcp: Update property value on content type and user changes
In reply to Sean PaulFrom: Sean Paul <[email protected]>
This patch updates the connector's property value in 2 cases which were previously missed:
1- Content type changes. The value should revert back to DESIRED from
ENABLED in case the driver must re-authenticate the link due to the new content type.
2- Userspace sets value to DESIRED while ENABLED. In this case, the
value should be reset immediately to ENABLED since the link is actively being encrypted.
To accommodate these changes, I've split up the conditionals to make things a bit more clear (as much as one can with this mess of state).
Changes in v2:
-None
--- drivers/gpu/drm/drm_hdcp.c | 26 +++++++++++++++++--------- 1 file changed, 17 insertions(+), 9 deletions(-)
drivers/gpu/drm/drm_hdcp.c +17 -9
@@ -487,21 +487,29 @@ bool drm_hdcp_atomic_check(struct drm_connector *connector,return true;/* -* Nothing to do if content type is unchanged and one of: -* - state didn't change +* Content type changes require an HDCP disable/enable cycle. +*/ +if (new_conn_state->hdcp_content_type != old_conn_state->hdcp_content_type) { + new_conn_state->content_protection = +DRM_MODE_CONTENT_PROTECTION_DESIRED ; +return true; + } + +/* +* Ignore meaningless state changes: * - HDCP was activated since the last commit -* - attempting to set to desired while already enabled +* - Attempting to set to desired while already enabled */ -if (old_hdcp == new_hdcp || - (old_hdcp ==DRM_MODE_CONTENT_PROTECTION_DESIRED && +if ((old_hdcp ==DRM_MODE_CONTENT_PROTECTION_DESIRED && new_hdcp ==DRM_MODE_CONTENT_PROTECTION_ENABLED ) || (old_hdcp ==DRM_MODE_CONTENT_PROTECTION_ENABLED && new_hdcp ==DRM_MODE_CONTENT_PROTECTION_DESIRED )) { -if (old_conn_state->hdcp_content_type == - new_conn_state->hdcp_content_type) -return false; + new_conn_state->content_protection = +DRM_MODE_CONTENT_PROTECTION_ENABLED ; +return false; } -return true; +/* Finally, if state changes, we need action */ +return old_hdcp != new_hdcp; }EXPORT_SYMBOL (drm_hdcp_atomic_check);
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
kernel test robot
build botRe: [Intel-gfx] [PATCH v2 03/13] drm/hdcp: Update property value on content type and user changes
I love your patch! Perhaps something to improve:
Hi Sean,
I love your patch! Perhaps something to improve:
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-tip/drm-tip robh/for-next linus/master v5.15-rc1 next-20210916] [If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Sean-Paul/drm-hdcp-Pull-HDCP-auth-exchange-check-into-helpers/20210916-044145 base: git://anongit.freedesktop.org/drm-intel for-linux-next config: x86_64-randconfig-m001-20210916 (attached as .config) compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
If you fix the issue, kindly add following tag as appropriate
smatch warnings:drivers/gpu/drm/drm_hdcp.c:509 drm_hdcp_atomic_check() warn: inconsistent indenting
vim +509 drivers/gpu/drm/drm_hdcp.c
a46c52c65fdbf76 Sean Paul 2021-09-15 425
a46c52c65fdbf76 Sean Paul 2021-09-15 426 /**
a46c52c65fdbf76 Sean Paul 2021-09-15 427 * drm_hdcp_atomic_check - Helper for drivers to call during connector->atomic_check
a46c52c65fdbf76 Sean Paul 2021-09-15 428 *
a46c52c65fdbf76 Sean Paul 2021-09-15 429 * @state: pointer to the atomic state being checked
a46c52c65fdbf76 Sean Paul 2021-09-15 430 * @connector: drm_connector on which content protection state needs an update
a46c52c65fdbf76 Sean Paul 2021-09-15 431 *
a46c52c65fdbf76 Sean Paul 2021-09-15 432 * This function can be used by display drivers to perform an atomic check on the
d0cdceca77739a6 Sean Paul 2021-09-15 433 * hdcp state elements. If hdcp state has changed in a manner which requires the
d0cdceca77739a6 Sean Paul 2021-09-15 434 * driver to enable or disable content protection, this function will return
d0cdceca77739a6 Sean Paul 2021-09-15 435 * true.
d0cdceca77739a6 Sean Paul 2021-09-15 436 *
d0cdceca77739a6 Sean Paul 2021-09-15 437 * Returns:
d0cdceca77739a6 Sean Paul 2021-09-15 438 * true if the driver must enable/disable hdcp, false otherwise
a46c52c65fdbf76 Sean Paul 2021-09-15 439 */
d0cdceca77739a6 Sean Paul 2021-09-15 440 bool drm_hdcp_atomic_check(struct drm_connector *connector,
a46c52c65fdbf76 Sean Paul 2021-09-15 441 struct drm_atomic_state *state)
a46c52c65fdbf76 Sean Paul 2021-09-15 442 {
a46c52c65fdbf76 Sean Paul 2021-09-15 443 struct drm_connector_state *new_conn_state, *old_conn_state;
a46c52c65fdbf76 Sean Paul 2021-09-15 444 struct drm_crtc_state *new_crtc_state;
a46c52c65fdbf76 Sean Paul 2021-09-15 445 u64 old_hdcp, new_hdcp;
a46c52c65fdbf76 Sean Paul 2021-09-15 446
a46c52c65fdbf76 Sean Paul 2021-09-15 447 old_conn_state = drm_atomic_get_old_connector_state(state, connector);
a46c52c65fdbf76 Sean Paul 2021-09-15 448 old_hdcp = old_conn_state->content_protection;
a46c52c65fdbf76 Sean Paul 2021-09-15 449
a46c52c65fdbf76 Sean Paul 2021-09-15 450 new_conn_state = drm_atomic_get_new_connector_state(state, connector);
a46c52c65fdbf76 Sean Paul 2021-09-15 451 new_hdcp = new_conn_state->content_protection;
a46c52c65fdbf76 Sean Paul 2021-09-15 452
a46c52c65fdbf76 Sean Paul 2021-09-15 453 if (!new_conn_state->crtc) {
a46c52c65fdbf76 Sean Paul 2021-09-15 454 /*
a46c52c65fdbf76 Sean Paul 2021-09-15 455 * If the connector is being disabled with CP enabled, mark it
a46c52c65fdbf76 Sean Paul 2021-09-15 456 * desired so it's re-enabled when the connector is brought back
a46c52c65fdbf76 Sean Paul 2021-09-15 457 */
d0cdceca77739a6 Sean Paul 2021-09-15 458 if (old_hdcp == DRM_MODE_CONTENT_PROTECTION_ENABLED) {
a46c52c65fdbf76 Sean Paul 2021-09-15 459 new_conn_state->content_protection =
a46c52c65fdbf76 Sean Paul 2021-09-15 460 DRM_MODE_CONTENT_PROTECTION_DESIRED;
d0cdceca77739a6 Sean Paul 2021-09-15 461 return true;
d0cdceca77739a6 Sean Paul 2021-09-15 462 }
d0cdceca77739a6 Sean Paul 2021-09-15 463 return false;
a46c52c65fdbf76 Sean Paul 2021-09-15 464 }
a46c52c65fdbf76 Sean Paul 2021-09-15 465
a46c52c65fdbf76 Sean Paul 2021-09-15 466 new_crtc_state = drm_atomic_get_new_crtc_state(state,
a46c52c65fdbf76 Sean Paul 2021-09-15 467 new_conn_state->crtc);
a46c52c65fdbf76 Sean Paul 2021-09-15 468 /*
a46c52c65fdbf76 Sean Paul 2021-09-15 469 * Fix the HDCP uapi content protection state in case of modeset.
a46c52c65fdbf76 Sean Paul 2021-09-15 470 * FIXME: As per HDCP content protection property uapi doc, an uevent()
a46c52c65fdbf76 Sean Paul 2021-09-15 471 * need to be sent if there is transition from ENABLED->DESIRED.
a46c52c65fdbf76 Sean Paul 2021-09-15 472 */
a46c52c65fdbf76 Sean Paul 2021-09-15 473 if (drm_atomic_crtc_needs_modeset(new_crtc_state) &&
a46c52c65fdbf76 Sean Paul 2021-09-15 474 (old_hdcp == DRM_MODE_CONTENT_PROTECTION_ENABLED &&
d0cdceca77739a6 Sean Paul 2021-09-15 475 new_hdcp != DRM_MODE_CONTENT_PROTECTION_UNDESIRED)) {
a46c52c65fdbf76 Sean Paul 2021-09-15 476 new_conn_state->content_protection =
a46c52c65fdbf76 Sean Paul 2021-09-15 477 DRM_MODE_CONTENT_PROTECTION_DESIRED;
d0cdceca77739a6 Sean Paul 2021-09-15 478 return true;
d0cdceca77739a6 Sean Paul 2021-09-15 479 }
d0cdceca77739a6 Sean Paul 2021-09-15 480
d0cdceca77739a6 Sean Paul 2021-09-15 481 /*
d0cdceca77739a6 Sean Paul 2021-09-15 482 * Coming back from disable or changing CRTC with DESIRED state requires
d0cdceca77739a6 Sean Paul 2021-09-15 483 * that the driver try CP enable.
d0cdceca77739a6 Sean Paul 2021-09-15 484 */
d0cdceca77739a6 Sean Paul 2021-09-15 485 if (new_hdcp == DRM_MODE_CONTENT_PROTECTION_DESIRED &&
d0cdceca77739a6 Sean Paul 2021-09-15 486 new_conn_state->crtc != old_conn_state->crtc)
d0cdceca77739a6 Sean Paul 2021-09-15 487 return true;
a46c52c65fdbf76 Sean Paul 2021-09-15 488
a46c52c65fdbf76 Sean Paul 2021-09-15 489 /*
6c538fd0f0a55b2 Sean Paul 2021-09-15 490 * Content type changes require an HDCP disable/enable cycle.
6c538fd0f0a55b2 Sean Paul 2021-09-15 491 */
6c538fd0f0a55b2 Sean Paul 2021-09-15 492 if (new_conn_state->hdcp_content_type != old_conn_state->hdcp_content_type) {
6c538fd0f0a55b2 Sean Paul 2021-09-15 493 new_conn_state->content_protection =
6c538fd0f0a55b2 Sean Paul 2021-09-15 494 DRM_MODE_CONTENT_PROTECTION_DESIRED;
6c538fd0f0a55b2 Sean Paul 2021-09-15 495 return true;
6c538fd0f0a55b2 Sean Paul 2021-09-15 496 }
6c538fd0f0a55b2 Sean Paul 2021-09-15 497
6c538fd0f0a55b2 Sean Paul 2021-09-15 498 /*
6c538fd0f0a55b2 Sean Paul 2021-09-15 499 * Ignore meaningless state changes:
a46c52c65fdbf76 Sean Paul 2021-09-15 500 * - HDCP was activated since the last commit
6c538fd0f0a55b2 Sean Paul 2021-09-15 501 * - Attempting to set to desired while already enabled
a46c52c65fdbf76 Sean Paul 2021-09-15 502 */
6c538fd0f0a55b2 Sean Paul 2021-09-15 503 if ((old_hdcp == DRM_MODE_CONTENT_PROTECTION_DESIRED &&
a46c52c65fdbf76 Sean Paul 2021-09-15 504 new_hdcp == DRM_MODE_CONTENT_PROTECTION_ENABLED) ||
a46c52c65fdbf76 Sean Paul 2021-09-15 505 (old_hdcp == DRM_MODE_CONTENT_PROTECTION_ENABLED &&
a46c52c65fdbf76 Sean Paul 2021-09-15 506 new_hdcp == DRM_MODE_CONTENT_PROTECTION_DESIRED)) {
6c538fd0f0a55b2 Sean Paul 2021-09-15 507 new_conn_state->content_protection =
6c538fd0f0a55b2 Sean Paul 2021-09-15 508 DRM_MODE_CONTENT_PROTECTION_ENABLED;d0cdceca77739a6 Sean Paul 2021-09-15 @509 return false;
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
Sean Paul
reviewerPATCH v2 4/13 drm/hdcp: Expand HDCP helper library for enable/disable/check
In reply to Sean PaulFrom: Sean Paul <[email protected]>
This patch expands upon the HDCP helper library to manage HDCP enable, disable, and check.
Previous to this patch, the majority of the state management and sink interaction is tucked inside the Intel driver with the understanding that once a new platform supported HDCP we could make good decisions about what should be centralized. With the addition of HDCP support for Qualcomm, it's time to migrate the protocol-specific bits of HDCP authentication, key exchange, and link checks to the HDCP helper.
In terms of functionality, this migration is 1:1 with the Intel driver, however things are laid out a bit differently than with intel_hdcp.c, which is why this is a separate patch from the i915 transition to the helper. On i915, the "shim" vtable is used to account for HDMI vs. DP vs. DP-MST differences whereas the helper library uses a LUT to account for the register offsets and a remote read function to route the messages. On i915, storing the sink information in the source is done inline whereas now we use the new drm_hdcp_helper_funcs vtable to store and fetch information to/from source hw. Finally, instead of calling enable/disable directly from the driver, we'll leave that decision to the helper and by calling drm_hdcp_helper_atomic_commit() from the driver. All told, this will centralize the protocol and state handling in the helper, ensuring we collect all of our bugs^Wlogic in one place.
Changes in v2:
-Fixed set-but-unused variable identified by 0-day
--- drivers/gpu/drm/drm_hdcp.c | 1103 ++++++++++++++++++++++++++++++++++++ include/drm/drm_hdcp.h | 191 +++++++ 2 files changed, 1294 insertions(+)
drivers/gpu/drm/drm_hdcp.c +1103 -0
@@ -6,15 +6,20 @@* Ramalingam C <[email protected]> */ +#include <linux/delay.h> #include <linux/device.h> #include <linux/err.h> #include <linux/gfp.h> +#include <linux/i2c.h> +#include <linux/iopoll.h> #include <linux/export.h> #include <linux/slab.h> #include <linux/firmware.h> +#include <linux/workqueue.h> #include <drm/drm_atomic.h> #include <drm/drm_connector.h> +#include <drm/drm_dp_helper.h> #include <drm/drm_hdcp.h> #include <drm/drm_sysfs.h> #include <drm/drm_print.h>
@@ -513,3 +518,1101 @@ bool drm_hdcp_atomic_check(struct drm_connector *connector,return old_hdcp != new_hdcp; }EXPORT_SYMBOL (drm_hdcp_atomic_check); + +struct drm_hdcp_helper_data { +struct mutex mutex; +struct mutex *driver_mutex; + +struct drm_connector *connector; +const struct drm_hdcp_helper_funcs *funcs; + +u64 value; +unsigned int enabled_type; + +struct delayed_work check_work; +struct work_struct prop_work; + +struct drm_dp_aux *aux; +const struct drm_hdcp_hdcp1_receiver_reg_lut *hdcp1_lut; +}; + +struct drm_hdcp_hdcp1_receiver_reg_lut { +unsigned int bksv; +unsigned int ri; +unsigned int aksv; +unsigned int an; +unsigned int ainfo; +unsigned int v[5 ]; +unsigned int bcaps; +unsigned int bcaps_mask_repeater_present; +unsigned int bstatus; +}; + +static const struct drm_hdcp_hdcp1_receiver_reg_lut drm_hdcp_hdcp1_ddc_lut = { + .bksv =DRM_HDCP_DDC_BKSV , + .ri =DRM_HDCP_DDC_RI_PRIME , + .aksv =DRM_HDCP_DDC_AKSV , + .an =DRM_HDCP_DDC_AN , + .ainfo =DRM_HDCP_DDC_AINFO , + .v = {DRM_HDCP_DDC_V_PRIME (0 ),DRM_HDCP_DDC_V_PRIME (1 ), +DRM_HDCP_DDC_V_PRIME (2 ),DRM_HDCP_DDC_V_PRIME (3 ), +DRM_HDCP_DDC_V_PRIME (4 ) }, + .bcaps =DRM_HDCP_DDC_BCAPS , + .bcaps_mask_repeater_present =DRM_HDCP_DDC_BCAPS_REPEATER_PRESENT , + .bstatus =DRM_HDCP_DDC_BSTATUS , +}; + +static const struct drm_hdcp_hdcp1_receiver_reg_lut drm_hdcp_hdcp1_dpcd_lut = { + .bksv =DP_AUX_HDCP_BKSV , + .ri =DP_AUX_HDCP_RI_PRIME , + .aksv =DP_AUX_HDCP_AKSV , + .an =DP_AUX_HDCP_AN , + .ainfo =DP_AUX_HDCP_AINFO , + .v = {DP_AUX_HDCP_V_PRIME (0 ),DP_AUX_HDCP_V_PRIME (1 ), +DP_AUX_HDCP_V_PRIME (2 ),DP_AUX_HDCP_V_PRIME (3 ), +DP_AUX_HDCP_V_PRIME (4 ) }, + .bcaps =DP_AUX_HDCP_BCAPS , + .bcaps_mask_repeater_present =DP_BCAPS_REPEATER_PRESENT , + +/* +* For some reason the HDMI and DP HDCP specs call this register +* definition by different names. In the HDMI spec, it's called BSTATUS, +* but in DP it's called BINFO. +*/ + .bstatus =DP_AUX_HDCP_BINFO , +}; + +static int drm_hdcp_remote_ddc_read (struct i2c_adapter *i2c, +unsigned int offset,u8 *value,size_t len) +{ +int ret; +u8 start = offset &0xff ; +struct i2c_msg msgs[] = { + { + .addr =DRM_HDCP_DDC_ADDR , + .flags =0 , + .len =1 , + .buf = &start, + }, + { + .addr =DRM_HDCP_DDC_ADDR , + .flags =I2C_M_RD , + .len = len, + .buf = value + } + }; + ret =i2c_transfer (i2c, msgs,ARRAY_SIZE (msgs)); +if (ret ==ARRAY_SIZE (msgs)) +return 0 ; +return ret >=0 ? -EIO : ret; +} + +static int drm_hdcp_remote_dpcd_read (struct drm_dp_aux *aux, +unsigned int offset,u8 *value, +size_t len) +{ +ssize_t ret; + + ret =drm_dp_dpcd_read (aux, offset, value, len); +if (ret != len) { +if (ret >=0 ) +return -EIO ; +return ret; + } + +return 0 ; +} + +static int drm_hdcp_remote_read (struct drm_hdcp_helper_data *data, +unsigned int offset,u8 *value,u8 len) +{ +if (data->aux) +return drm_hdcp_remote_dpcd_read (data->aux, offset, value, len); +else +return drm_hdcp_remote_ddc_read (data->connector->ddc, offset, value, len); +} + +static int drm_hdcp_remote_ddc_write (struct i2c_adapter *i2c, +unsigned int offset,u8 *buffer, +size_t size) +{ +int ret; +u8 *write_buf; +struct i2c_msg msg; + + write_buf =kzalloc (size +1 ,GFP_KERNEL ); +if (!write_buf) +return -ENOMEM ; + + write_buf[0 ] = offset &0xff ; +memcpy (&write_buf[1 ], buffer, size); + + msg.addr =DRM_HDCP_DDC_ADDR ; + msg.flags =0 , + msg.len = size +1 , + msg.buf = write_buf; + + ret =i2c_transfer (i2c, &msg,1 ); +if (ret ==1 ) + ret =0 ; +else if (ret >=0 ) + ret = -EIO ; + +kfree (write_buf); +return ret; +} + +static int drm_hdcp_remote_dpcd_write (struct drm_dp_aux *aux, +unsigned int offset,u8 *value, +size_t len) +{ +ssize_t ret; + + ret =drm_dp_dpcd_write (aux, offset, value, len); +if (ret != len) { +if (ret >=0 ) +return -EIO ; +return ret; + } + +return 0 ; +} + +static int drm_hdcp_remote_write (struct drm_hdcp_helper_data *data, +unsigned int offset,u8 *value,u8 len) +{ +if (data->aux) +return drm_hdcp_remote_dpcd_write (data->aux, offset, value, len); +else +return drm_hdcp_remote_ddc_write (data->connector->ddc, offset, + value, len); +} + +static bool drm_hdcp_is_ksv_valid (struct drm_hdcp_ksv *ksv) +{ +/* Valid Ksv has 20 0's and 20 1's */ +return hweight32 (ksv->words[0 ]) +hweight32 (ksv->words[1 ]) ==20 ; +} + +static int drm_hdcp_read_valid_bksv (struct drm_hdcp_helper_data *data, +struct drm_hdcp_ksv *bksv) +{ +int ret, i, tries =2 ; + +/* HDCP spec states that we must retry the bksv if it is invalid */ +for (i =0 ; i < tries; i++) { + ret =drm_hdcp_remote_read (data, data->hdcp1_lut->bksv, + bksv->bytes,DRM_HDCP_KSV_LEN ); +if (ret) +return ret; + +if (drm_hdcp_is_ksv_valid (bksv)) +break ; + } +if (i == tries) { +drm_dbg_kms (data->connector->dev,"Bksv is invalid %*ph\n" , +DRM_HDCP_KSV_LEN , bksv->bytes); +return -ENODEV ; + } + +return 0 ; +} + +/** +* drm_hdcp_helper_hdcp1_capable - Checks if the sink is capable of HDCP 1.x. +* +* @data: pointer to the HDCP helper data. +* @capable: pointer to a bool which will contain true if the sink is capable. +* +* Returns: +* -errno if the transacation between source and sink fails. +*/ +int drm_hdcp_helper_hdcp1_capable (struct drm_hdcp_helper_data *data, +bool *capable) +{ +/* +* DisplayPort has a dedicated bit for this in DPCD whereas HDMI spec +* states that transmitters should use bksv to determine capability. +*/ +if (data->aux) { +int ret; +u8 bcaps; + + ret =drm_hdcp_remote_read (data, data->hdcp1_lut->bcaps, + &bcaps,1 ); + *capable = !ret && (bcaps &DP_BCAPS_HDCP_CAPABLE ); + }else { +struct drm_hdcp_ksv bksv; + + *capable =drm_hdcp_read_valid_bksv (data, &bksv) ==0 ; + } + +return 0 ; +} +EXPORT_SYMBOL (drm_hdcp_helper_hdcp1_capable); + +static void drm_hdcp_update_value (struct drm_hdcp_helper_data *data, +u64 value,bool update_property) +{ +WARN_ON (!mutex_is_locked (&data->mutex)); + + data->value = value; +if (update_property) { +drm_connector_get (data->connector); +schedule_work (&data->prop_work); + } +} + +static int +drm_hdcp_helper_hdcp1_ksv_fifo_ready (struct drm_hdcp_helper_data *data) +{ +int ret; +u8 val, mask; + +/* KSV FIFO ready bit is stored in different locations on DP v. HDMI */ +if (data->aux) { + ret =drm_hdcp_remote_dpcd_read (data->aux,DP_AUX_HDCP_BSTATUS , + &val,1 ); + mask =DP_BSTATUS_READY ; + }else { + ret =drm_hdcp_remote_ddc_read (data->connector->ddc, +DRM_HDCP_DDC_BCAPS , &val,1 ); + mask =DRM_HDCP_DDC_BCAPS_KSV_FIFO_READY ; + } +if (ret) +return ret; +if (val & mask) +return 0 ; + +return -EAGAIN ; +} + +static int +drm_hdcp_helper_hdcp1_read_ksv_fifo (struct drm_hdcp_helper_data *data,u8 *fifo, +u8 num_downstream) +{ +struct drm_device *dev = data->connector->dev; +int ret, i; + +/* Over HDMI, read the whole thing at once */ +if (data->connector->ddc) { + ret =drm_hdcp_remote_ddc_read (data->connector->ddc, +DRM_HDCP_DDC_KSV_FIFO , fifo, + num_downstream *DRM_HDCP_KSV_LEN ); +if (ret) +drm_err (dev,"DDC ksv fifo read failed (%d)\n" , ret); +return ret; + } + +/* Over DP, read via 15 byte window (3 entries @ 5 bytes each) */ +for (i =0 ; i < num_downstream; i +=3 ) { +size_t len =min (num_downstream - i,3 ) *DRM_HDCP_KSV_LEN ; + ret =drm_hdcp_remote_dpcd_read (data->aux,DP_AUX_HDCP_KSV_FIFO , + fifo + i *DRM_HDCP_KSV_LEN , + len); +if (ret) { +drm_err (dev,"Read ksv[%d] from DP/AUX failed (%d)\n" , + i, ret); +return ret; + } + } + +return 0 ; +} + +static int drm_hdcp_helper_hdcp1_read_v_prime (struct drm_hdcp_helper_data *data, +u32 *v_prime) +{ +struct drm_device *dev = data->connector->dev; +int ret, i; + +for (i =0 ; i <DRM_HDCP_V_PRIME_NUM_PARTS ; i++) { + ret =drm_hdcp_remote_read (data, data->hdcp1_lut->v[i], + (u8 *)&v_prime[i], +DRM_HDCP_V_PRIME_PART_LEN ); +if (ret) { +drm_dbg_kms (dev,"Read v'[%d] from failed (%d)\n" , i, ret); +return ret >=0 ? -EIO : ret; + } + } +return 0 ; +} + +static int +drm_hdcp_helper_hdcp1_authenticate_downstream (struct drm_hdcp_helper_data *data) +{ +struct drm_connector *connector = data->connector; +struct drm_device *dev = connector->dev; +u32 v_prime[DRM_HDCP_V_PRIME_NUM_PARTS ]; +u8 bstatus[DRM_HDCP_BSTATUS_LEN ]; +u8 num_downstream, *ksv_fifo; +int ret, i, tries =3 ; + + ret =read_poll_timeout (drm_hdcp_helper_hdcp1_ksv_fifo_ready, ret, !ret, +10 *1000 ,5 *1000 *1000 , false, data); +if (ret) { +drm_err (dev,"Failed to poll ksv ready, %d\n" , ret); +return ret; + } + + ret =drm_hdcp_remote_read (data, data->hdcp1_lut->bstatus, + bstatus,DRM_HDCP_BSTATUS_LEN ); +if (ret) +return ret; + +/* +* When repeater reports 0 device count, HDCP1.4 spec allows disabling +* the HDCP encryption. That implies that repeater can't have its own +* display. As there is no consumption of encrypted content in the +* repeater with 0 downstream devices, we are failing the +* authentication. +*/ + num_downstream =DRM_HDCP_NUM_DOWNSTREAM (bstatus[0 ]); +if (num_downstream ==0 ) { +drm_err (dev,"Repeater with zero downstream devices, %*ph\n" , +DRM_HDCP_BSTATUS_LEN , bstatus); +return -EINVAL ; + } + + ksv_fifo =kcalloc (DRM_HDCP_KSV_LEN , num_downstream,GFP_KERNEL ); +if (!ksv_fifo) +return -ENOMEM ; + + ret =drm_hdcp_helper_hdcp1_read_ksv_fifo (data, ksv_fifo, + num_downstream); +if (ret) { +drm_err (dev,"Failed to read ksv fifo, %d/%d\n" , num_downstream, + ret); + goto out; + } + +if (drm_hdcp_check_ksvs_revoked (dev, ksv_fifo, num_downstream)) { +drm_err (dev,"Revoked Ksv(s) in ksv_fifo\n" ); + ret = -EPERM ; + goto out; + } + +/* +* When V prime mismatches, DP Spec mandates re-read of +* V prime atleast twice. +*/ +for (i =0 ; i < tries; i++) { + ret =drm_hdcp_helper_hdcp1_read_v_prime (data, v_prime); +if (ret) +continue ; + + ret = data->funcs->hdcp1_store_ksv_fifo (connector, ksv_fifo, + num_downstream, + bstatus, v_prime); +if (!ret) +break ; + } +if (ret) +drm_err (dev,"Could not validate KSV FIFO with V' %d\n" , ret); + +out: +if (!ret) +drm_dbg_kms (dev,"HDCP is enabled (%d downstream devices)\n" , + num_downstream); + +kfree (ksv_fifo); +return ret; +} + +static int drm_hdcp_helper_hdcp1_validate_ri (struct drm_hdcp_helper_data *data) +{ +union { +u32 word; +u8 bytes[DRM_HDCP_RI_LEN ]; + } ri_prime = { .word =0 }; +struct drm_connector *connector = data->connector; +struct drm_device *dev = connector->dev; +int ret; + + ret =drm_hdcp_remote_read (data, data->hdcp1_lut->ri, ri_prime.bytes, +DRM_HDCP_RI_LEN ); +if (ret) { +drm_err (dev,"Failed to read R0' %d\n" , ret); +return ret; + } + +return data->funcs->hdcp1_match_ri (connector, ri_prime.word); +} + +static int drm_hdcp_helper_hdcp1_authenticate (struct drm_hdcp_helper_data *data) +{ +union { +u32 word; +u8 bytes[DRM_HDCP_BSTATUS_LEN ]; + } bstatus; +const struct drm_hdcp_helper_funcs *funcs = data->funcs; +struct drm_connector *connector = data->connector; +struct drm_device *dev = connector->dev; +unsigned long r0_prime_timeout, r0_prime_remaining_us =0 , tmp_jiffies; +struct drm_hdcp_ksv aksv; +struct drm_hdcp_ksv bksv; +struct drm_hdcp_an an; +bool repeater_present; +int ret, i, tries =3 ; +u8 bcaps; + +if (funcs->hdcp1_read_an_aksv) { + ret = funcs->hdcp1_read_an_aksv (connector, an.words, aksv.words); +if (ret) { +drm_err (dev,"Failed to read An/Aksv values, %d\n" , ret); +return ret; + } + + ret =drm_hdcp_remote_write (data, data->hdcp1_lut->an, an.bytes, +DRM_HDCP_AN_LEN ); +if (ret) { +drm_err (dev,"Failed to write An to receiver, %d\n" , ret); +return ret; + } + + ret =drm_hdcp_remote_write (data, data->hdcp1_lut->aksv, aksv.bytes, +DRM_HDCP_KSV_LEN ); +if (ret) { +drm_err (dev,"Failed to write Aksv to receiver, %d\n" , ret); +return ret; + } + }else { + ret = funcs->hdcp1_send_an_aksv (connector); +if (ret) { +drm_err (dev,"Failed to read An/Aksv values, %d\n" , ret); +return ret; + } + } + +/* +* Timeout for R0' to become available. The spec says 100ms from Aksv, +* but some monitors can take longer than this. We'll set the timeout at +* 300ms just to be sure. +*/ + r0_prime_timeout = jiffies +msecs_to_jiffies (300 ); + +memset (&bksv,0 ,sizeof (bksv)); + + ret =drm_hdcp_read_valid_bksv (data, &bksv); +if (ret <0 ) +return ret; + +if (drm_hdcp_check_ksvs_revoked (dev, bksv.bytes,1 )) { +drm_err (dev,"BKSV is revoked\n" ); +return -EPERM ; + } + + ret =drm_hdcp_remote_read (data, data->hdcp1_lut->bcaps, &bcaps,1 ); +if (ret) +return ret; + +memset (&bstatus,0 ,sizeof (bstatus)); + + ret =drm_hdcp_remote_read (data, data->hdcp1_lut->bstatus, + bstatus.bytes,DRM_HDCP_BSTATUS_LEN ); +if (ret) +return ret; + +if (DRM_HDCP_MAX_DEVICE_EXCEEDED (bstatus.bytes[0 ]) || +DRM_HDCP_MAX_CASCADE_EXCEEDED (bstatus.bytes[1 ])) { +drm_err (dev,"Max Topology Limit Exceeded, bstatus=%*ph\n" , +DRM_HDCP_BSTATUS_LEN , bstatus.bytes); +return -EPERM ; + } + + repeater_present = bcaps & data->hdcp1_lut->bcaps_mask_repeater_present; + + ret = funcs->hdcp1_store_receiver_info (connector, bksv.words, + bstatus.word, bcaps, + repeater_present); +if (ret) { +drm_err (dev,"Failed to store bksv, %d\n" , ret); +return ret; + } + + ret = funcs->hdcp1_enable_encryption (connector); +if (ret) +return ret; + + ret = funcs->hdcp1_wait_for_r0 (connector); +if (ret) +return ret; + + tmp_jiffies = jiffies; +if (time_before (tmp_jiffies, r0_prime_timeout)) + r0_prime_remaining_us =jiffies_to_usecs (r0_prime_timeout - tmp_jiffies); + +/* +* Wait for R0' to become available. +* +* On DP, there's an R0_READY bit available but no such bit +* exists on HDMI. So poll the ready bit for DP and just wait the +* remainder of the 300 ms timeout for HDMI. +*/ +if (data->aux) { +u8 val; + ret =read_poll_timeout (drm_hdcp_remote_dpcd_read, ret, + !ret && (val &DP_BSTATUS_R0_PRIME_READY ), +1000 , r0_prime_remaining_us, false, + data->aux,DP_AUX_HDCP_BSTATUS , &val,1 ); +if (ret) { +drm_err (dev,"R0' did not become ready %d\n" , ret); +return ret; + } + }else { +usleep_range (r0_prime_remaining_us, + r0_prime_remaining_us +1000 ); + } + +/* +* DP HDCP Spec mandates the two more reattempt to read R0, incase +* of R0 mismatch. +*/ +for (i =0 ; i < tries; i++) { + ret =drm_hdcp_helper_hdcp1_validate_ri (data); +if (!ret) +break ; + } +if (ret) { +drm_err (dev,"Failed to match R0/R0', aborting HDCP %d\n" , ret); +return ret; + } + +if (repeater_present) +return drm_hdcp_helper_hdcp1_authenticate_downstream (data); + +drm_dbg_kms (dev,"HDCP is enabled (no repeater present)\n" ); +return 0 ; +} + +static int drm_hdcp_helper_hdcp1_enable (struct drm_hdcp_helper_data *data) +{ +struct drm_connector *connector = data->connector; +struct drm_device *dev = connector->dev; +int i, ret, tries =3 ; + +drm_dbg_kms (dev,"[%s:%d] HDCP is being enabled...\n" , connector->name, + connector->base.id); + +/* Incase of authentication failures, HDCP spec expects reauth. */ +for (i =0 ; i < tries; i++) { + ret =drm_hdcp_helper_hdcp1_authenticate (data); +if (!ret) +return 0 ; + +drm_dbg_kms (dev,"HDCP Auth failure (%d)\n" , ret); + +/* Ensuring HDCP encryption and signalling are stopped. */ + data->funcs->hdcp1_disable (data->connector); + } + +drm_err (dev,"HDCP authentication failed (%d tries/%d)\n" , tries, ret); +return ret; +} + +static inline +void drm_hdcp_helper_driver_lock (struct drm_hdcp_helper_data *data) +{ +if (data->driver_mutex) +mutex_lock (data->driver_mutex); +} + +static inline +void drm_hdcp_helper_driver_unlock (struct drm_hdcp_helper_data *data) +{ +if (data->driver_mutex) +mutex_unlock (data->driver_mutex); +} + +static int drm_hdcp_helper_enable_hdcp (struct drm_hdcp_helper_data *data, +struct drm_atomic_state *state, +struct mutex *driver_mutex) +{ +struct drm_connector *connector = data->connector; +struct drm_connector_state *conn_state; +struct drm_device *dev = connector->dev; +unsigned long check_link_interval; +bool capable; +int ret =0 ; + + conn_state =drm_atomic_get_new_connector_state (state, connector); + +mutex_lock (&data->mutex); + +if (data->value ==DRM_MODE_CONTENT_PROTECTION_ENABLED ) { +drm_hdcp_update_value (data,DRM_MODE_CONTENT_PROTECTION_ENABLED , + true); + goto out_data_mutex; + } + +drm_WARN_ON (dev, data->driver_mutex !=NULL ); + data->driver_mutex = driver_mutex; + +drm_hdcp_helper_driver_lock (data); + +if (data->funcs->setup) { + ret = data->funcs->setup (connector, state); +if (ret) { +drm_err (dev,"Failed to setup HDCP %d\n" , ret); + goto out; + } + } + +if (!data->funcs->are_keys_valid || + !data->funcs->are_keys_valid (connector)) { +if (data->funcs->load_keys) { + ret = data->funcs->load_keys (connector); +if (ret) { +drm_err (dev,"Failed to load HDCP keys %d\n" , ret); + goto out; + } + } + } + +/* +* Considering that HDCP2.2 is more secure than HDCP1.4, If the setup +* is capable of HDCP2.2, it is preferred to use HDCP2.2. +*/ + ret = data->funcs->hdcp2_capable (connector, &capable); +if (ret) { +drm_err (dev,"HDCP 2.x capability check failed %d\n" , ret); + goto out; + } +if (capable) { + data->enabled_type =DRM_MODE_HDCP_CONTENT_TYPE1 ; + ret = data->funcs->hdcp2_enable (connector); +if (!ret) { + check_link_interval =DRM_HDCP2_CHECK_PERIOD_MS ; + goto out; + } + } + +/* +* When HDCP2.2 fails and Content Type is not Type1, HDCP1.4 will +* be attempted. +*/ + ret =drm_hdcp_helper_hdcp1_capable (data, &capable); +if (ret) { +drm_err (dev,"HDCP 1.x capability check failed %d\n" , ret); + goto out; + } +if (capable && conn_state->content_type !=DRM_MODE_HDCP_CONTENT_TYPE1 ) { + data->enabled_type =DRM_MODE_HDCP_CONTENT_TYPE0 ; + ret =drm_hdcp_helper_hdcp1_enable (data); +if (!ret) + check_link_interval =DRM_HDCP_CHECK_PERIOD_MS ; + } + +out: +if (!ret) { +schedule_delayed_work (&data->check_work, check_link_interval); +drm_hdcp_update_value (data,DRM_MODE_CONTENT_PROTECTION_ENABLED , + true); + } + +drm_hdcp_helper_driver_unlock (data); +if (ret) + data->driver_mutex =NULL ; + +out_data_mutex: +mutex_unlock (&data->mutex); +return ret; +} + +static int drm_hdcp_helper_disable_hdcp (struct drm_hdcp_helper_data *data) +{ +int ret =0 ; + +mutex_lock (&data->mutex); +drm_hdcp_helper_driver_lock (data); + +if (data->value ==DRM_MODE_CONTENT_PROTECTION_UNDESIRED ) + goto out; + +drm_dbg_kms (data->connector->dev,"[%s:%d] HDCP is being disabled...\n" , + data->connector->name, data->connector->base.id); + +drm_hdcp_update_value (data,DRM_MODE_CONTENT_PROTECTION_UNDESIRED , true); + +if (data->enabled_type ==DRM_MODE_HDCP_CONTENT_TYPE1 ) + ret = data->funcs->hdcp2_disable (data->connector); +else + ret = data->funcs->hdcp1_disable (data->connector); + +drm_dbg_kms (data->connector->dev,"HDCP is disabled\n" ); + +out: +drm_hdcp_helper_driver_unlock (data); + data->driver_mutex =NULL ; +mutex_unlock (&data->mutex); +cancel_delayed_work_sync (&data->check_work); +return ret; +} + +/** +* drm_hdcp_helper_atomic_commit - Helper for drivers to call during commit to +* enable/disable HDCP +* +* @data: pointer to the @drm_hdcp_helper_data for the connector +* @state: pointer to the atomic state being committed +* @driver_mutex: driver-provided lock to be used while interacting with the driver +* +* This function can be used by display drivers to determine when HDCP should be +* enabled or disabled based on the connector state. It should be called during +* steady-state commits as well as connector enable/disable. The function will +* handle the HDCP authentication/encryption logic, calling back into the driver +* when source operations are necessary. +* +* @driver_mutex will be retained and used for the duration of the HDCP session +* since it will be needed for link checks and retries. This mutex is useful if +* the driver has shared resources across connectors which must be serialized. +* For example, driver_mutex can be used for MST connectors sharing a common +* encoder which should not be accessed/changed concurrently. When the +* connector's session is torn down, the mutex will be forgotten by the helper +* for this connector until the next session. +*/ +void drm_hdcp_helper_atomic_commit (struct drm_hdcp_helper_data *data, +struct drm_atomic_state *state, +struct mutex *driver_mutex) +{ +struct drm_connector *connector = data->connector; +struct drm_connector_state *conn_state; +bool type_changed; + + conn_state =drm_atomic_get_new_connector_state (state, connector); + + type_changed = conn_state->hdcp_content_type != data->enabled_type; + +if (conn_state->content_protection ==DRM_MODE_CONTENT_PROTECTION_UNDESIRED ) { +drm_hdcp_helper_disable_hdcp (data); +return ; + } + +if (!conn_state->crtc) { +drm_hdcp_helper_disable_hdcp (data); + +/* Restore property to DESIRED so it's retried later */ +if (conn_state->content_protection ==DRM_MODE_CONTENT_PROTECTION_ENABLED ) { +mutex_lock (&data->mutex); +drm_hdcp_update_value (data,DRM_MODE_CONTENT_PROTECTION_DESIRED , + true); +mutex_unlock (&data->mutex); + } +return ; + } + +/* Already enabled */ +if (conn_state->content_protection ==DRM_MODE_CONTENT_PROTECTION_ENABLED ) +return ; + +/* Disable and re-enable HDCP on content type change */ +if (type_changed) +drm_hdcp_helper_disable_hdcp (data); + +drm_hdcp_helper_enable_hdcp (data, state, driver_mutex); +} +EXPORT_SYMBOL (drm_hdcp_helper_atomic_commit); + +static void drm_hdcp_helper_prop_work (struct work_struct *work) +{ +struct drm_hdcp_helper_data *data =container_of (work, + struct drm_hdcp_helper_data, + prop_work); +struct drm_connector *connector = data->connector; +struct drm_device *dev = connector->dev; + +drm_modeset_lock (&dev->mode_config.connection_mutex,NULL ); +mutex_lock (&data->mutex); + +/* +* This worker is only used to flip between ENABLED/DESIRED. Either of +* those to UNDESIRED is handled by core. If value == UNDESIRED, +* we're running just after hdcp has been disabled, so just exit +*/ +if (data->value !=DRM_MODE_CONTENT_PROTECTION_UNDESIRED ) +drm_hdcp_update_content_protection (connector, data->value); + +mutex_unlock (&data->mutex); +drm_modeset_unlock (&dev->mode_config.connection_mutex); +} + +static int drm_hdcp_hdcp1_check_link (struct drm_hdcp_helper_data *data) +{ +struct drm_connector *connector = data->connector; +struct drm_device *dev = connector->dev; +int ret; + +if (data->funcs->hdcp1_check_link) { + ret = data->funcs->hdcp1_check_link (connector); +if (ret) + goto retry; + } + +/* The link is checked differently for DP and HDMI */ +if (data->aux) { +u8 bstatus; + ret =drm_hdcp_remote_dpcd_read (data->aux,DP_AUX_HDCP_BSTATUS , + &bstatus,1 ); +if (ret) { +drm_err (dev,"Failed to read dpcd bstatus, %d\n" , ret); +return ret; + } +if (bstatus & (DP_BSTATUS_LINK_FAILURE |DP_BSTATUS_REAUTH_REQ )) + ret = -EINVAL ; + }else { + ret =drm_hdcp_helper_hdcp1_validate_ri (data); +if (ret) +drm_err (dev,"Ri' mismatch, check failed (%d)\n" , ret); + } +if (!ret) +return 0 ; + +retry: +drm_err (dev,"[%s:%d] HDCP link failed, retrying authentication\n" , + connector->name, connector->base.id); + + ret = data->funcs->hdcp1_disable (connector); +if (ret) { +drm_err (dev,"Failed to disable hdcp (%d)\n" , ret); +drm_hdcp_update_value (data,DRM_MODE_CONTENT_PROTECTION_DESIRED , + true); +return ret; + } + + ret =drm_hdcp_helper_hdcp1_enable (data); +if (ret) { +drm_err (dev,"Failed to enable hdcp (%d)\n" , ret); +drm_hdcp_update_value (data,DRM_MODE_CONTENT_PROTECTION_DESIRED , + true); +return ret; + } + +return 0 ; +} + +static int drm_hdcp_hdcp2_check_link (struct drm_hdcp_helper_data *data) +{ +struct drm_connector *connector = data->connector; +struct drm_device *dev = connector->dev; +int ret; + + ret = data->funcs->hdcp2_check_link (connector); +if (!ret) +return 0 ; + +drm_err (dev,"[%s:%d] HDCP2 link failed, retrying authentication\n" , + connector->name, connector->base.id); + + ret = data->funcs->hdcp2_disable (connector); +if (ret) { +drm_err (dev,"Failed to disable hdcp2 (%d)\n" , ret); +drm_hdcp_update_value (data,DRM_MODE_CONTENT_PROTECTION_DESIRED , + true); +return ret; + } + + ret = data->funcs->hdcp2_enable (connector); +if (ret) { +drm_err (dev,"Failed to enable hdcp2 (%d)\n" , ret); +drm_hdcp_update_value (data,DRM_MODE_CONTENT_PROTECTION_DESIRED , + true); +return ret; + } + +return 0 ; +} + +static void drm_hdcp_helper_check_work (struct work_struct *work) +{ +struct drm_hdcp_helper_data *data =container_of (to_delayed_work (work), + struct drm_hdcp_helper_data, + check_work); +unsigned long check_link_interval; + +mutex_lock (&data->mutex); +if (data->value !=DRM_MODE_CONTENT_PROTECTION_ENABLED ) + goto out_data_mutex; + +drm_hdcp_helper_driver_lock (data); + +if (data->enabled_type ==DRM_MODE_HDCP_CONTENT_TYPE1 ) { +if (drm_hdcp_hdcp2_check_link (data)) + goto out; + check_link_interval =DRM_HDCP2_CHECK_PERIOD_MS ; + }else { +if (drm_hdcp_hdcp1_check_link (data)) + goto out; + check_link_interval =DRM_HDCP_CHECK_PERIOD_MS ; + } +schedule_delayed_work (&data->check_work, check_link_interval); + +out: +drm_hdcp_helper_driver_unlock (data); +out_data_mutex: +mutex_unlock (&data->mutex); +} + +/** +* drm_hdcp_helper_schedule_hdcp_check - Schedule a check link cycle. +* +* @data: Pointer to the HDCP helper data. +* +* This function will kick off a check link cycle on behalf of the caller. This +* can be used by DP short hpd interrupt handlers, where the driver must poke +* the helper to check the link is still valid. +*/ +void drm_hdcp_helper_schedule_hdcp_check (struct drm_hdcp_helper_data *data) +{ +schedule_delayed_work (&data->check_work,0 ); +} +EXPORT_SYMBOL (drm_hdcp_helper_schedule_hdcp_check); + +static struct drm_hdcp_helper_data * +drm_hdcp_helper_initialize (struct drm_connector *connector, +const struct drm_hdcp_helper_funcs *funcs, +bool attach_content_type_property) +{ +struct drm_hdcp_helper_data *out; +int ret; + + out =kzalloc (sizeof (*out),GFP_KERNEL ); +if (!out) +return ERR_PTR (-ENOMEM ); + + out->connector = connector; + out->funcs = funcs; + +mutex_init (&out->mutex); + out->value =DRM_MODE_CONTENT_PROTECTION_UNDESIRED ; + +INIT_DELAYED_WORK (&out->check_work, drm_hdcp_helper_check_work); +INIT_WORK (&out->prop_work, drm_hdcp_helper_prop_work); + + ret =drm_connector_attach_content_protection_property (connector, + attach_content_type_property); +if (ret) { +drm_hdcp_helper_destroy (out); +return ERR_PTR (ret); + } + +return out; +} + +/** +* drm_hdcp_helper_initialize_dp - Initializes the HDCP helpers for a +* DisplayPort connector +* +* @connector: pointer to the DisplayPort connector. +* @funcs: pointer to the vtable of HDCP helper funcs for this connector. +* @attach_content_type_property: True if the content_type property should be +* attached. +* +* This function intializes the HDCP helper for the given DisplayPort connector. +* This involves creating the Content Protection property as well as the Content +* Type property (if desired). Upon success, it will return a pointer to the +* HDCP helper data. Ownership of the underlaying memory is transfered to the +* caller and should be freed using drm_hdcp_helper_destroy(). +* +* Returns: +* Pointer to newly created HDCP helper data. PTR_ERR on failure. +*/ +struct drm_hdcp_helper_data * +drm_hdcp_helper_initialize_dp (struct drm_connector *connector, +struct drm_dp_aux *aux, +const struct drm_hdcp_helper_funcs *funcs, +bool attach_content_type_property) +{ +struct drm_hdcp_helper_data *out; + + out =drm_hdcp_helper_initialize (connector, funcs, + attach_content_type_property); +if (IS_ERR (out)) +return out; + + out->aux = aux; + out->hdcp1_lut = &drm_hdcp_hdcp1_dpcd_lut; + +return out; +} +EXPORT_SYMBOL (drm_hdcp_helper_initialize_dp); + +/** +* drm_hdcp_helper_initialize_hdmi - Initializes the HDCP helpers for an HDMI +* connector +* +* @connector: pointer to the HDMI connector. +* @funcs: pointer to the vtable of HDCP helper funcs for this connector. +* @attach_content_type_property: True if the content_type property should be +* attached. +* +* This function intializes the HDCP helper for the given HDMI connector. This +* involves creating the Content Protection property as well as the Content Type +* property (if desired). Upon success, it will return a pointer to the HDCP +* helper data. Ownership of the underlaying memory is transfered to the caller +* and should be freed using drm_hdcp_helper_destroy(). +* +* Returns: +* Pointer to newly created HDCP helper data. PTR_ERR on failure. +*/ +struct drm_hdcp_helper_data * +drm_hdcp_helper_initialize_hdmi (struct drm_connector *connector, +const struct drm_hdcp_helper_funcs *funcs, +bool attach_content_type_property) +{ +struct drm_hdcp_helper_data *out; + + out =drm_hdcp_helper_initialize (connector, funcs, + attach_content_type_property); +if (IS_ERR (out)) +return out; + + out->hdcp1_lut = &drm_hdcp_hdcp1_ddc_lut; + +return out; +} +EXPORT_SYMBOL (drm_hdcp_helper_initialize_hdmi); + +/** +* drm_hdcp_helper_destroy - Destroys the given HDCP helper data. +* +* @data: Pointer to the HDCP helper data. +* +* This function cleans up and destroys the HDCP helper data created by +* drm_hdcp_helper_initialize_dp() or drm_hdcp_helper_initialize_hdmi(). +*/ +void drm_hdcp_helper_destroy (struct drm_hdcp_helper_data *data) +{ +struct drm_connector *connector; + +if (!data) +return ; + + connector = data->connector; + +/* +* If the connector is registered, it's possible userspace could kick +* off another HDCP enable, which would re-spawn the workers. +*/ +drm_WARN_ON (connector->dev, + connector->registration_state ==DRM_CONNECTOR_REGISTERED ); + +/* +* Now that the connector is not registered, check_work won't be run, +* but cancel any outstanding instances of it +*/ +cancel_delayed_work_sync (&data->check_work); + +/* +* We don't cancel prop_work in the same way as check_work since it +* requires connection_mutex which could be held while calling this +* function. Instead, we rely on the connector references grabbed before +* scheduling prop_work to ensure the connector is alive when prop_work +* is run. So if we're in the destroy path (which is where this +* function should be called), we're "guaranteed" that prop_work is not +* active (tl;dr This Should Never Happen). +*/ +drm_WARN_ON (connector->dev,work_pending (&data->prop_work)); + +kfree (data); +} +EXPORT_SYMBOL (drm_hdcp_helper_destroy);
include/drm/drm_hdcp.h +191 -0
212 lines not on this page · raw message
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Dan Carpenter
build bot[kbuild] Re: [PATCH v2 04/13] drm/hdcp: Expand HDCP helper library for enable/disable/check
CC: kbuild-all(a)lists.01.org In-Reply-To: <[email protected]> References: <[email protected]> TO: Sean Paul <[email protected]> TO…
CC: kbuild-all(a)lists.01.org
In-Reply-To: <[email protected]>
References: <[email protected]>
TO: Sean Paul <[email protected]>
TO: dri-devel(a)lists.freedesktop.org
TO: intel-gfx(a)lists.freedesktop.org
TO: freedreno(a)lists.freedesktop.org
CC: swboyd(a)chromium.org
CC: Sean Paul <[email protected]>
CC: Maarten Lankhorst <[email protected]>
CC: Maxime Ripard <[email protected]>
CC: Thomas Zimmermann <[email protected]>
CC: David Airlie <[email protected]>
CC: Daniel Vetter <[email protected]>
Hi Sean,
I love your patch! Perhaps something to improve:
[auto build test WARNING on drm-intel/for-linux-next]
[also build test WARNING on drm-tip/drm-tip robh/for-next linus/master v5.15-rc1 next-20210916] [If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Sean-Paul/drm-hdcp-Pull-HDCP-auth-exchange-check-into-helpers/20210916-044145 base: git://anongit.freedesktop.org/drm-intel for-linux-next
:::::: branch date: 29 hours ago
:::::: commit date: 29 hours ago
config: x86_64-randconfig-m001-20210916 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
If you fix the issue, kindly add following tag as appropriate
New smatch warnings:drivers/gpu/drm/drm_hdcp.c:1208 drm_hdcp_helper_enable_hdcp() error: uninitialized symbol 'check_link_interval'.
Old smatch warnings:drivers/gpu/drm/drm_hdcp.c:514 drm_hdcp_atomic_check() warn: inconsistent indenting
vim +/check_link_interval +1208 drivers/gpu/drm/drm_hdcp.c
cbc5065be3a652f Sean Paul 2021-09-15 1126
cbc5065be3a652f Sean Paul 2021-09-15 1127 static int drm_hdcp_helper_enable_hdcp(struct drm_hdcp_helper_data *data,
cbc5065be3a652f Sean Paul 2021-09-15 1128 struct drm_atomic_state *state,
cbc5065be3a652f Sean Paul 2021-09-15 1129 struct mutex *driver_mutex)
cbc5065be3a652f Sean Paul 2021-09-15 1130 {
cbc5065be3a652f Sean Paul 2021-09-15 1131 struct drm_connector *connector = data->connector;
cbc5065be3a652f Sean Paul 2021-09-15 1132 struct drm_connector_state *conn_state;
cbc5065be3a652f Sean Paul 2021-09-15 1133 struct drm_device *dev = connector->dev;
cbc5065be3a652f Sean Paul 2021-09-15 1134 unsigned long check_link_interval;
cbc5065be3a652f Sean Paul 2021-09-15 1135 bool capable;
cbc5065be3a652f Sean Paul 2021-09-15 1136 int ret = 0;
cbc5065be3a652f Sean Paul 2021-09-15 1137
cbc5065be3a652f Sean Paul 2021-09-15 1138 conn_state = drm_atomic_get_new_connector_state(state, connector);
cbc5065be3a652f Sean Paul 2021-09-15 1139
cbc5065be3a652f Sean Paul 2021-09-15 1140 mutex_lock(&data->mutex);
cbc5065be3a652f Sean Paul 2021-09-15 1141
cbc5065be3a652f Sean Paul 2021-09-15 1142 if (data->value == DRM_MODE_CONTENT_PROTECTION_ENABLED) {
cbc5065be3a652f Sean Paul 2021-09-15 1143 drm_hdcp_update_value(data, DRM_MODE_CONTENT_PROTECTION_ENABLED,
cbc5065be3a652f Sean Paul 2021-09-15 1144 true);
cbc5065be3a652f Sean Paul 2021-09-15 1145 goto out_data_mutex;
cbc5065be3a652f Sean Paul 2021-09-15 1146 }
cbc5065be3a652f Sean Paul 2021-09-15 1147
cbc5065be3a652f Sean Paul 2021-09-15 1148 drm_WARN_ON(dev, data->driver_mutex != NULL);
cbc5065be3a652f Sean Paul 2021-09-15 1149 data->driver_mutex = driver_mutex;
cbc5065be3a652f Sean Paul 2021-09-15 1150
cbc5065be3a652f Sean Paul 2021-09-15 1151 drm_hdcp_helper_driver_lock(data);
cbc5065be3a652f Sean Paul 2021-09-15 1152
cbc5065be3a652f Sean Paul 2021-09-15 1153 if (data->funcs->setup) {
cbc5065be3a652f Sean Paul 2021-09-15 1154 ret = data->funcs->setup(connector, state);
cbc5065be3a652f Sean Paul 2021-09-15 1155 if (ret) {
cbc5065be3a652f Sean Paul 2021-09-15 1156 drm_err(dev, "Failed to setup HDCP %d\n", ret);
cbc5065be3a652f Sean Paul 2021-09-15 1157 goto out;
cbc5065be3a652f Sean Paul 2021-09-15 1158 }
cbc5065be3a652f Sean Paul 2021-09-15 1159 }
cbc5065be3a652f Sean Paul 2021-09-15 1160
cbc5065be3a652f Sean Paul 2021-09-15 1161 if (!data->funcs->are_keys_valid ||
cbc5065be3a652f Sean Paul 2021-09-15 1162 !data->funcs->are_keys_valid(connector)) {
cbc5065be3a652f Sean Paul 2021-09-15 1163 if (data->funcs->load_keys) {
cbc5065be3a652f Sean Paul 2021-09-15 1164 ret = data->funcs->load_keys(connector);
cbc5065be3a652f Sean Paul 2021-09-15 1165 if (ret) {
cbc5065be3a652f Sean Paul 2021-09-15 1166 drm_err(dev, "Failed to load HDCP keys %d\n", ret);
cbc5065be3a652f Sean Paul 2021-09-15 1167 goto out;
cbc5065be3a652f Sean Paul 2021-09-15 1168 }
cbc5065be3a652f Sean Paul 2021-09-15 1169 }
cbc5065be3a652f Sean Paul 2021-09-15 1170 }
cbc5065be3a652f Sean Paul 2021-09-15 1171
cbc5065be3a652f Sean Paul 2021-09-15 1172 /*
cbc5065be3a652f Sean Paul 2021-09-15 1173 * Considering that HDCP2.2 is more secure than HDCP1.4, If the setup
cbc5065be3a652f Sean Paul 2021-09-15 1174 * is capable of HDCP2.2, it is preferred to use HDCP2.2.
cbc5065be3a652f Sean Paul 2021-09-15 1175 */
cbc5065be3a652f Sean Paul 2021-09-15 1176 ret = data->funcs->hdcp2_capable(connector, &capable);
cbc5065be3a652f Sean Paul 2021-09-15 1177 if (ret) {
cbc5065be3a652f Sean Paul 2021-09-15 1178 drm_err(dev, "HDCP 2.x capability check failed %d\n", ret);
cbc5065be3a652f Sean Paul 2021-09-15 1179 goto out;
cbc5065be3a652f Sean Paul 2021-09-15 1180 }
cbc5065be3a652f Sean Paul 2021-09-15 1181 if (capable) {
cbc5065be3a652f Sean Paul 2021-09-15 1182 data->enabled_type = DRM_MODE_HDCP_CONTENT_TYPE1;
cbc5065be3a652f Sean Paul 2021-09-15 1183 ret = data->funcs->hdcp2_enable(connector);
cbc5065be3a652f Sean Paul 2021-09-15 1184 if (!ret) {
cbc5065be3a652f Sean Paul 2021-09-15 1185 check_link_interval = DRM_HDCP2_CHECK_PERIOD_MS;
cbc5065be3a652f Sean Paul 2021-09-15 1186 goto out;
cbc5065be3a652f Sean Paul 2021-09-15 1187 }
cbc5065be3a652f Sean Paul 2021-09-15 1188 }
cbc5065be3a652f Sean Paul 2021-09-15 1189
cbc5065be3a652f Sean Paul 2021-09-15 1190 /*
cbc5065be3a652f Sean Paul 2021-09-15 1191 * When HDCP2.2 fails and Content Type is not Type1, HDCP1.4 will
cbc5065be3a652f Sean Paul 2021-09-15 1192 * be attempted.
cbc5065be3a652f Sean Paul 2021-09-15 1193 */
cbc5065be3a652f Sean Paul 2021-09-15 1194 ret = drm_hdcp_helper_hdcp1_capable(data, &capable);
cbc5065be3a652f Sean Paul 2021-09-15 1195 if (ret) {
cbc5065be3a652f Sean Paul 2021-09-15 1196 drm_err(dev, "HDCP 1.x capability check failed %d\n", ret);
cbc5065be3a652f Sean Paul 2021-09-15 1197 goto out;
cbc5065be3a652f Sean Paul 2021-09-15 1198 }
cbc5065be3a652f Sean Paul 2021-09-15 1199 if (capable && conn_state->content_type != DRM_MODE_HDCP_CONTENT_TYPE1) {
cbc5065be3a652f Sean Paul 2021-09-15 1200 data->enabled_type = DRM_MODE_HDCP_CONTENT_TYPE0;
cbc5065be3a652f Sean Paul 2021-09-15 1201 ret = drm_hdcp_helper_hdcp1_enable(data);
cbc5065be3a652f Sean Paul 2021-09-15 1202 if (!ret)
cbc5065be3a652f Sean Paul 2021-09-15 1203 check_link_interval = DRM_HDCP_CHECK_PERIOD_MS;
cbc5065be3a652f Sean Paul 2021-09-15 1204 }
cbc5065be3a652f Sean Paul 2021-09-15 1205
cbc5065be3a652f Sean Paul 2021-09-15 1206 out:
cbc5065be3a652f Sean Paul 2021-09-15 1207 if (!ret) {
cbc5065be3a652f Sean Paul 2021-09-15 @1208 schedule_delayed_work(&data->check_work, check_link_interval);
cbc5065be3a652f Sean Paul 2021-09-15 1209 drm_hdcp_update_value(data, DRM_MODE_CONTENT_PROTECTION_ENABLED,
cbc5065be3a652f Sean Paul 2021-09-15 1210 true);
cbc5065be3a652f Sean Paul 2021-09-15 1211 }
cbc5065be3a652f Sean Paul 2021-09-15 1212
cbc5065be3a652f Sean Paul 2021-09-15 1213 drm_hdcp_helper_driver_unlock(data);
cbc5065be3a652f Sean Paul 2021-09-15 1214 if (ret)
cbc5065be3a652f Sean Paul 2021-09-15 1215 data->driver_mutex = NULL;
cbc5065be3a652f Sean Paul 2021-09-15 1216
cbc5065be3a652f Sean Paul 2021-09-15 1217 out_data_mutex:
cbc5065be3a652f Sean Paul 2021-09-15 1218 mutex_unlock(&data->mutex);
cbc5065be3a652f Sean Paul 2021-09-15 1219 return ret;
cbc5065be3a652f Sean Paul 2021-09-15 1220 }
cbc5065be3a652f Sean Paul 2021-09-15 1221 ---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
Re: [Freedreno] [PATCH v2 04/13] drm/hdcp: Expand HDCP helper library for enable/disable/check
In reply to Sean PaulQuoted 1,022 lines · Sean Paul
From: Sean Paul <[email protected]>
This patch expands upon the HDCP helper library to manage HDCP enable, disable, and check.
Previous to this patch, the majority of the state management and sink interaction is tucked inside the Intel driver with the understanding that once a new platform supported HDCP we could make good decisions about what should be centralized. With the addition of HDCP support for Qualcomm, it's time to migrate the protocol-specific bits of HDCP authentication, key exchange, and link checks to the HDCP helper.
In terms of functionality, this migration is 1:1 with the Intel driver, however things are laid out a bit differently than with
intel_hdcp.c, which is why this is a separate patch from the i915 transition to the helper. On i915, the "shim" vtable is used to account for HDMI vs. DP vs. DP-MST differences whereas the helper library uses a LUT to account for the register offsets and a remote read function to route the messages. On i915, storing the sink information in the source is done inline whereas now we use the newdrm_hdcp_helper_funcsvtable to store and fetch information to/from source hw. Finally, instead of calling enable/disable directly from the driver, we'll leave that decision to the helper and by callingdrm_hdcp_helper_atomic_commit()from the driver. All told, this will centralize the protocol and state handling in the helper, ensuring we collect all of our bugs^Wlogic in one place.Signed-off-by Sean Paul <[email protected]>Link:
https://patchwork.freedesktop.org/patch/msgid/[email protected]
#v1Changes in v2:
(quoted diff) +0
-2-Fixed set-but-unused variable identified by 0-day --- drivers/gpu/drm/drm_hdcp.c | 1103 ++++++++++++++++++++++++++++++++++++ include/drm/drm_hdcp.h | 191 +++++++ 2 files changed, 1294 insertions(+)drivers/gpu/drm/drm_hdcp.c +36
-0@@ -6,15 +6,20 @@* Ramalingam C <[email protected]> */ +#include <linux/delay.h> #include <linux/device.h> #include <linux/err.h> #include <linux/gfp.h> +#include <linux/i2c.h> +#include <linux/iopoll.h> #include <linux/export.h> #include <linux/slab.h> #include <linux/firmware.h> +#include <linux/workqueue.h> #include <drm/drm_atomic.h> #include <drm/drm_connector.h> +#include <drm/drm_dp_helper.h> #include <drm/drm_hdcp.h> #include <drm/drm_sysfs.h> #include <drm/drm_print.h> @@ -513,3 +518,1101 @@ bool drm_hdcp_atomic_check(struct drm_connector *connector, return old_hdcp != new_hdcp; }EXPORT_SYMBOL (drm_hdcp_atomic_check); + +struct drm_hdcp_helper_data { +struct mutex mutex; +struct mutex *driver_mutex; + +struct drm_connector *connector; +const struct drm_hdcp_helper_funcs *funcs; + +u64 value; +unsigned int enabled_type; + +struct delayed_work check_work; +struct work_struct prop_work; + +struct drm_dp_aux *aux; +const struct drm_hdcp_hdcp1_receiver_reg_lut *hdcp1_lut; +}; + +struct drm_hdcp_hdcp1_receiver_reg_lut { +unsigned int bksv; +unsigned int ri; +unsigned int aksv; +unsigned int an; +unsigned int ainfo; +unsigned int v[5 ]; +unsigned int bcaps; +unsigned int bcaps_mask_repeater_present; +unsigned int bstatus; +}; + +static const struct drm_hdcp_hdcp1_receiver_reg_lut
drm_hdcp_hdcp1_ddc_lut= {drivers/gpu/drm/drm_hdcp.c +14
-0+ .bksv = DRM_HDCP_DDC_BKSV, + .ri = DRM_HDCP_DDC_RI_PRIME, + .aksv = DRM_HDCP_DDC_AKSV, + .an = DRM_HDCP_DDC_AN, + .ainfo = DRM_HDCP_DDC_AINFO, + .v = { DRM_HDCP_DDC_V_PRIME(0), DRM_HDCP_DDC_V_PRIME(1), +DRM_HDCP_DDC_V_PRIME (2 ),DRM_HDCP_DDC_V_PRIME (3 ), + DRM_HDCP_DDC_V_PRIME(4) }, + .bcaps = DRM_HDCP_DDC_BCAPS, + .bcaps_mask_repeater_present = DRM_HDCP_DDC_BCAPS_REPEATER_PRESENT, + .bstatus = DRM_HDCP_DDC_BSTATUS, +}; + +static const struct drm_hdcp_hdcp1_receiver_reg_lut
drm_hdcp_hdcp1_dpcd_lut= {drivers/gpu/drm/drm_hdcp.c +14
-0+ .bksv = DP_AUX_HDCP_BKSV, + .ri = DP_AUX_HDCP_RI_PRIME, + .aksv = DP_AUX_HDCP_AKSV, + .an = DP_AUX_HDCP_AN, + .ainfo = DP_AUX_HDCP_AINFO, + .v = { DP_AUX_HDCP_V_PRIME(0), DP_AUX_HDCP_V_PRIME(1), +DP_AUX_HDCP_V_PRIME (2 ),DP_AUX_HDCP_V_PRIME (3 ), + DP_AUX_HDCP_V_PRIME(4) }, + .bcaps = DP_AUX_HDCP_BCAPS, + .bcaps_mask_repeater_present = DP_BCAPS_REPEATER_PRESENT, + +/* +* For some reason the HDMI and DP HDCP specs call this register +* definition by different names. In the HDMI spec, it's called BSTATUS,
drivers/gpu/drm/drm_hdcp.c +53
-0+* but in DP it's called BINFO. +*/ + .bstatus = DP_AUX_HDCP_BINFO, +}; + +static int drm_hdcp_remote_ddc_read (struct i2c_adapter *i2c, +unsigned int offset,u8 *value,size_t len) +{ +int ret; +u8 start = offset &0xff ; +struct i2c_msg msgs[] = { + { + .addr =DRM_HDCP_DDC_ADDR , + .flags =0 , + .len =1 , + .buf = &start, + }, + { + .addr =DRM_HDCP_DDC_ADDR , + .flags =I2C_M_RD , + .len = len, + .buf = value + } + }; + ret =i2c_transfer (i2c, msgs,ARRAY_SIZE (msgs)); +if (ret ==ARRAY_SIZE (msgs)) +return 0 ; +return ret >=0 ? -EIO : ret; +} + +static int drm_hdcp_remote_dpcd_read (struct drm_dp_aux *aux, +unsigned int offset,u8 *value, +size_t len) +{ +ssize_t ret; + + ret =drm_dp_dpcd_read (aux, offset, value, len); +if (ret != len) { +if (ret >=0 ) +return -EIO ; +return ret; + } + +return 0 ; +} + +static int drm_hdcp_remote_read (struct drm_hdcp_helper_data *data, +unsigned int offset,u8 *value,u8 len) +{ +if (data->aux) +return drm_hdcp_remote_dpcd_read (data->aux, offset, value, len); +else + return drm_hdcp_remote_ddc_read(data->connector->ddc, offset, value,len);
drivers/gpu/drm/drm_hdcp.c +90
-0+} + +static int drm_hdcp_remote_ddc_write (struct i2c_adapter *i2c, +unsigned int offset,u8 *buffer, +size_t size) +{ +int ret; +u8 *write_buf; +struct i2c_msg msg; + + write_buf =kzalloc (size +1 ,GFP_KERNEL ); +if (!write_buf) +return -ENOMEM ; + + write_buf[0 ] = offset &0xff ; +memcpy (&write_buf[1 ], buffer, size); + + msg.addr =DRM_HDCP_DDC_ADDR ; + msg.flags =0 , + msg.len = size +1 , + msg.buf = write_buf; + + ret =i2c_transfer (i2c, &msg,1 ); +if (ret ==1 ) + ret =0 ; +else if (ret >=0 ) + ret = -EIO ; + +kfree (write_buf); +return ret; +} + +static int drm_hdcp_remote_dpcd_write (struct drm_dp_aux *aux, +unsigned int offset,u8 *value, +size_t len) +{ +ssize_t ret; + + ret =drm_dp_dpcd_write (aux, offset, value, len); +if (ret != len) { +if (ret >=0 ) +return -EIO ; +return ret; + } + +return 0 ; +} + +static int drm_hdcp_remote_write (struct drm_hdcp_helper_data *data, +unsigned int offset,u8 *value,u8 len) +{ +if (data->aux) +return drm_hdcp_remote_dpcd_write (data->aux, offset, value, len); +else +return drm_hdcp_remote_ddc_write (data->connector->ddc, offset, + value, len); +} + +static bool drm_hdcp_is_ksv_valid (struct drm_hdcp_ksv *ksv) +{ +/* Valid Ksv has 20 0's and 20 1's */ +return hweight32 (ksv->words[0 ]) +hweight32 (ksv->words[1 ]) ==20 ; +} + +static int drm_hdcp_read_valid_bksv (struct drm_hdcp_helper_data *data, +struct drm_hdcp_ksv *bksv) +{ +int ret, i, tries =2 ; + +/* HDCP spec states that we must retry the bksv if it is invalid */ +for (i =0 ; i < tries; i++) { + ret =drm_hdcp_remote_read (data, data->hdcp1_lut->bksv, + bksv->bytes,DRM_HDCP_KSV_LEN ); +if (ret) +return ret; + +if (drm_hdcp_is_ksv_valid (bksv)) +break ; + } +if (i == tries) { +drm_dbg_kms (data->connector->dev,"Bksv is invalid %*ph\n" , +DRM_HDCP_KSV_LEN , bksv->bytes); +return -ENODEV ; + } + +return 0 ; +} + +/** +* drm_hdcp_helper_hdcp1_capable - Checks if the sink is capable of HDCP 1.x.
+ *
+ * @data: pointer to the HDCP helper data.
+ * @capable: pointer to a bool which will contain true if the sink is capable.
+ *
+ * Returns:
+ * -errno if the transacation between source and sink fails.
+ */drivers/gpu/drm/drm_hdcp.c +38
-0+int drm_hdcp_helper_hdcp1_capable (struct drm_hdcp_helper_data *data, +bool *capable) +{ +/* +* DisplayPort has a dedicated bit for this in DPCD whereas HDMI spec +* states that transmitters should use bksv to determine capability. +*/ +if (data->aux) { +int ret; +u8 bcaps; + + ret =drm_hdcp_remote_read (data, data->hdcp1_lut->bcaps, + &bcaps,1 ); + *capable = !ret && (bcaps &DP_BCAPS_HDCP_CAPABLE ); + }else { +struct drm_hdcp_ksv bksv; + + *capable =drm_hdcp_read_valid_bksv (data, &bksv) ==0 ; + } + +return 0 ; +} +EXPORT_SYMBOL (drm_hdcp_helper_hdcp1_capable); + +static void drm_hdcp_update_value (struct drm_hdcp_helper_data *data, +u64 value,bool update_property) +{ +WARN_ON (!mutex_is_locked (&data->mutex)); + + data->value = value; +if (update_property) { +drm_connector_get (data->connector); +schedule_work (&data->prop_work); + } +} + +static int +drm_hdcp_helper_hdcp1_ksv_fifo_ready(struct drm_hdcp_helper_data*data)
drivers/gpu/drm/drm_hdcp.c +5
-0+{ +int ret; +u8 val, mask; + +/* KSV FIFO ready bit is stored in different locations on DP v. HDMI */
drivers/gpu/drm/drm_hdcp.c +19
-0+if (data->aux) { + ret =drm_hdcp_remote_dpcd_read (data->aux,DP_AUX_HDCP_BSTATUS , + &val,1 ); + mask =DP_BSTATUS_READY ; + }else { + ret =drm_hdcp_remote_ddc_read (data->connector->ddc, +DRM_HDCP_DDC_BCAPS , &val,1 ); + mask =DRM_HDCP_DDC_BCAPS_KSV_FIFO_READY ; + } +if (ret) +return ret; +if (val & mask) +return 0 ; + +return -EAGAIN ; +} + +static int +drm_hdcp_helper_hdcp1_read_ksv_fifo(struct drm_hdcp_helper_data*data, u8 *fifo,
drivers/gpu/drm/drm_hdcp.c +32
-0+ u8 num_downstream) +{ +struct drm_device *dev = data->connector->dev; +int ret, i; + +/* Over HDMI, read the whole thing at once */ +if (data->connector->ddc) { + ret =drm_hdcp_remote_ddc_read (data->connector->ddc, +DRM_HDCP_DDC_KSV_FIFO , fifo, + num_downstream *DRM_HDCP_KSV_LEN ); +if (ret) +drm_err (dev,"DDC ksv fifo read failed (%d)\n" , ret); +return ret; + } + +/* Over DP, read via 15 byte window (3 entries @ 5 bytes each) */ +for (i =0 ; i < num_downstream; i +=3 ) { +size_t len =min (num_downstream - i,3 ) *DRM_HDCP_KSV_LEN ; + ret =drm_hdcp_remote_dpcd_read (data->aux,DP_AUX_HDCP_KSV_FIFO , + fifo + i *DRM_HDCP_KSV_LEN , + len); +if (ret) { +drm_err (dev,"Read ksv[%d] from DP/AUX failed (%d)\n" , + i, ret); +return ret; + } + } + +return 0 ; +} + +static int drm_hdcp_helper_hdcp1_read_v_prime(struct
drm_hdcp_helper_data*data,drivers/gpu/drm/drm_hdcp.c +19
-0+ u32 *v_prime) +{ +struct drm_device *dev = data->connector->dev; +int ret, i; + +for (i =0 ; i <DRM_HDCP_V_PRIME_NUM_PARTS ; i++) { + ret =drm_hdcp_remote_read (data, data->hdcp1_lut->v[i], + (u8 *)&v_prime[i], +DRM_HDCP_V_PRIME_PART_LEN ); +if (ret) { +drm_dbg_kms (dev,"Read v'[%d] from failed (%d)\n" , i, ret); +return ret >=0 ? -EIO : ret; + } + } +return 0 ; +} + +static int +drm_hdcp_helper_hdcp1_authenticate_downstream(struct
drm_hdcp_helper_data*data)drivers/gpu/drm/drm_hdcp.c +9
-0+{ +struct drm_connector *connector = data->connector; +struct drm_device *dev = connector->dev; +u32 v_prime[DRM_HDCP_V_PRIME_NUM_PARTS ]; +u8 bstatus[DRM_HDCP_BSTATUS_LEN ]; +u8 num_downstream, *ksv_fifo; +int ret, i, tries =3 ; + + ret = read_poll_timeout(drm_hdcp_helper_hdcp1_ksv_fifo_ready, ret,!ret,
drivers/gpu/drm/drm_hdcp.c +13
-0+ 10 * 1000, 5 * 1000 * 1000, false, data); +if (ret) { +drm_err (dev,"Failed to poll ksv ready, %d\n" , ret); +return ret; + } + + ret =drm_hdcp_remote_read (data, data->hdcp1_lut->bstatus, + bstatus,DRM_HDCP_BSTATUS_LEN ); +if (ret) +return ret; + +/* +* When repeater reports 0 device count, HDCP1.4 spec allows disabling
drivers/gpu/drm/drm_hdcp.c +58
-0+* the HDCP encryption. That implies that repeater can't have its own +* display. As there is no consumption of encrypted content in the +* repeater with 0 downstream devices, we are failing the +* authentication. +*/ + num_downstream =DRM_HDCP_NUM_DOWNSTREAM (bstatus[0 ]); +if (num_downstream ==0 ) { +drm_err (dev,"Repeater with zero downstream devices, %*ph\n" , +DRM_HDCP_BSTATUS_LEN , bstatus); +return -EINVAL ; + } + + ksv_fifo =kcalloc (DRM_HDCP_KSV_LEN , num_downstream,GFP_KERNEL ); +if (!ksv_fifo) +return -ENOMEM ; + + ret =drm_hdcp_helper_hdcp1_read_ksv_fifo (data, ksv_fifo, + num_downstream); +if (ret) { +drm_err (dev,"Failed to read ksv fifo, %d/%d\n" , num_downstream, + ret); + goto out; + } + +if (drm_hdcp_check_ksvs_revoked (dev, ksv_fifo, num_downstream)) { +drm_err (dev,"Revoked Ksv(s) in ksv_fifo\n" ); + ret = -EPERM ; + goto out; + } + +/* +* When V prime mismatches, DP Spec mandates re-read of +* V prime atleast twice. +*/ +for (i =0 ; i < tries; i++) { + ret =drm_hdcp_helper_hdcp1_read_v_prime (data, v_prime); +if (ret) +continue ; + + ret = data->funcs->hdcp1_store_ksv_fifo (connector, ksv_fifo, + num_downstream, + bstatus, v_prime); +if (!ret) +break ; + } +if (ret) +drm_err (dev,"Could not validate KSV FIFO with V' %d\n" , ret); + +out: +if (!ret) +drm_dbg_kms (dev,"HDCP is enabled (%d downstream devices)\n" , + num_downstream); + +kfree (ksv_fifo); +return ret; +} + +static int drm_hdcp_helper_hdcp1_validate_ri(struct
drm_hdcp_helper_data*data)drivers/gpu/drm/drm_hdcp.c +20
-0+{ +union { +u32 word; +u8 bytes[DRM_HDCP_RI_LEN ]; + } ri_prime = { .word =0 }; +struct drm_connector *connector = data->connector; +struct drm_device *dev = connector->dev; +int ret; + + ret =drm_hdcp_remote_read (data, data->hdcp1_lut->ri, ri_prime.bytes, +DRM_HDCP_RI_LEN ); +if (ret) { +drm_err (dev,"Failed to read R0' %d\n" , ret); +return ret; + } + +return data->funcs->hdcp1_match_ri (connector, ri_prime.word); +} + +static int drm_hdcp_helper_hdcp1_authenticate(struct
drm_hdcp_helper_data*data)drivers/gpu/drm/drm_hdcp.c +9
-0+{ +union { +u32 word; +u8 bytes[DRM_HDCP_BSTATUS_LEN ]; + } bstatus; +const struct drm_hdcp_helper_funcs *funcs = data->funcs; +struct drm_connector *connector = data->connector; +struct drm_device *dev = connector->dev; + unsigned long r0_prime_timeout, r0_prime_remaining_us = 0,
tmp_jiffies;drivers/gpu/drm/drm_hdcp.c +37
-0+struct drm_hdcp_ksv aksv; +struct drm_hdcp_ksv bksv; +struct drm_hdcp_an an; +bool repeater_present; +int ret, i, tries =3 ; +u8 bcaps; + +if (funcs->hdcp1_read_an_aksv) { + ret = funcs->hdcp1_read_an_aksv (connector, an.words, aksv.words); +if (ret) { +drm_err (dev,"Failed to read An/Aksv values, %d\n" , ret); +return ret; + } + + ret =drm_hdcp_remote_write (data, data->hdcp1_lut->an, an.bytes, +DRM_HDCP_AN_LEN ); +if (ret) { +drm_err (dev,"Failed to write An to receiver, %d\n" , ret); +return ret; + } + + ret =drm_hdcp_remote_write (data, data->hdcp1_lut->aksv, aksv.bytes, +DRM_HDCP_KSV_LEN ); +if (ret) { +drm_err (dev,"Failed to write Aksv to receiver, %d\n" , ret); +return ret; + } + }else { + ret = funcs->hdcp1_send_an_aksv (connector); +if (ret) { +drm_err (dev,"Failed to read An/Aksv values, %d\n" , ret); +return ret; + } + } + +/* +* Timeout for R0' to become available. The spec says 100ms from Aksv,
drivers/gpu/drm/drm_hdcp.c +1
-0+* but some monitors can take longer than this. We'll set the timeout at
drivers/gpu/drm/drm_hdcp.c +34
-0+* 300ms just to be sure. +*/ + r0_prime_timeout = jiffies +msecs_to_jiffies (300 ); + +memset (&bksv,0 ,sizeof (bksv)); + + ret =drm_hdcp_read_valid_bksv (data, &bksv); +if (ret <0 ) +return ret; + +if (drm_hdcp_check_ksvs_revoked (dev, bksv.bytes,1 )) { +drm_err (dev,"BKSV is revoked\n" ); +return -EPERM ; + } + + ret =drm_hdcp_remote_read (data, data->hdcp1_lut->bcaps, &bcaps,1 ); +if (ret) +return ret; + +memset (&bstatus,0 ,sizeof (bstatus)); + + ret =drm_hdcp_remote_read (data, data->hdcp1_lut->bstatus, + bstatus.bytes,DRM_HDCP_BSTATUS_LEN ); +if (ret) +return ret; + +if (DRM_HDCP_MAX_DEVICE_EXCEEDED (bstatus.bytes[0 ]) || +DRM_HDCP_MAX_CASCADE_EXCEEDED (bstatus.bytes[1 ])) { +drm_err (dev,"Max Topology Limit Exceeded, bstatus=%*ph\n" , +DRM_HDCP_BSTATUS_LEN , bstatus.bytes); +return -EPERM ; + } + + repeater_present = bcaps &
data->hdcp1_lut->bcaps_mask_repeater_present;drivers/gpu/drm/drm_hdcp.c +20
-0+ + ret = funcs->hdcp1_store_receiver_info (connector, bksv.words, + bstatus.word, bcaps, + repeater_present); +if (ret) { +drm_err (dev,"Failed to store bksv, %d\n" , ret); +return ret; + } + + ret = funcs->hdcp1_enable_encryption (connector); +if (ret) +return ret; + + ret = funcs->hdcp1_wait_for_r0 (connector); +if (ret) +return ret; + + tmp_jiffies = jiffies; +if (time_before (tmp_jiffies, r0_prime_timeout)) + r0_prime_remaining_us = jiffies_to_usecs(r0_prime_timeout -
tmp_jiffies);drivers/gpu/drm/drm_hdcp.c +45
-0+ +/* +* Wait for R0' to become available. +* +* On DP, there's an R0_READY bit available but no such bit +* exists on HDMI. So poll the ready bit for DP and just wait the +* remainder of the 300 ms timeout for HDMI. +*/ +if (data->aux) { +u8 val; + ret =read_poll_timeout (drm_hdcp_remote_dpcd_read, ret, + !ret && (val &DP_BSTATUS_R0_PRIME_READY ), +1000 , r0_prime_remaining_us, false, + data->aux,DP_AUX_HDCP_BSTATUS , &val,1 ); +if (ret) { +drm_err (dev,"R0' did not become ready %d\n" , ret); +return ret; + } + }else { +usleep_range (r0_prime_remaining_us, + r0_prime_remaining_us +1000 ); + } + +/* +* DP HDCP Spec mandates the two more reattempt to read R0, incase +* of R0 mismatch. +*/ +for (i =0 ; i < tries; i++) { + ret =drm_hdcp_helper_hdcp1_validate_ri (data); +if (!ret) +break ; + } +if (ret) { +drm_err (dev,"Failed to match R0/R0', aborting HDCP %d\n" , ret); +return ret; + } + +if (repeater_present) +return drm_hdcp_helper_hdcp1_authenticate_downstream (data); + +drm_dbg_kms (dev,"HDCP is enabled (no repeater present)\n" ); +return 0 ; +} + +static int drm_hdcp_helper_hdcp1_enable(struct drm_hdcp_helper_data*data)
drivers/gpu/drm/drm_hdcp.c +6
-0+{ +struct drm_connector *connector = data->connector; +struct drm_device *dev = connector->dev; +int i, ret, tries =3 ; + + drm_dbg_kms(dev, "[%s:%d] HDCP is being enabled...\n",
connector->name,drivers/gpu/drm/drm_hdcp.c +15
-0+ connector->base.id); + +/* Incase of authentication failures, HDCP spec expects reauth. */ +for (i =0 ; i < tries; i++) { + ret =drm_hdcp_helper_hdcp1_authenticate (data); +if (!ret) +return 0 ; + +drm_dbg_kms (dev,"HDCP Auth failure (%d)\n" , ret); + +/* Ensuring HDCP encryption and signalling are stopped. */ + data->funcs->hdcp1_disable (data->connector); + } + + drm_err(dev, "HDCP authentication failed (%d tries/%d)\n", tries,ret);
drivers/gpu/drm/drm_hdcp.c +18
-0+return ret; +} + +static inline +void drm_hdcp_helper_driver_lock (struct drm_hdcp_helper_data *data) +{ +if (data->driver_mutex) +mutex_lock (data->driver_mutex); +} + +static inline +void drm_hdcp_helper_driver_unlock (struct drm_hdcp_helper_data *data) +{ +if (data->driver_mutex) +mutex_unlock (data->driver_mutex); +} + +static int drm_hdcp_helper_enable_hdcp(struct drm_hdcp_helper_data*data,
drivers/gpu/drm/drm_hdcp.c +72
-0+struct drm_atomic_state *state, + struct mutex *driver_mutex) +{ + struct drm_connector *connector = data->connector; +struct drm_connector_state *conn_state; +struct drm_device *dev = connector->dev; +unsigned long check_link_interval; +bool capable; +int ret =0 ; + + conn_state =drm_atomic_get_new_connector_state (state, connector); + +mutex_lock (&data->mutex); + +if (data->value ==DRM_MODE_CONTENT_PROTECTION_ENABLED ) { +drm_hdcp_update_value (data,DRM_MODE_CONTENT_PROTECTION_ENABLED , + true); + goto out_data_mutex; + } + +drm_WARN_ON (dev, data->driver_mutex !=NULL ); + data->driver_mutex = driver_mutex; + +drm_hdcp_helper_driver_lock (data); + +if (data->funcs->setup) { + ret = data->funcs->setup (connector, state); +if (ret) { +drm_err (dev,"Failed to setup HDCP %d\n" , ret); + goto out; + } + } + +if (!data->funcs->are_keys_valid || + !data->funcs->are_keys_valid (connector)) { +if (data->funcs->load_keys) { + ret = data->funcs->load_keys (connector); +if (ret) { +drm_err (dev,"Failed to load HDCP keys %d\n" , ret); + goto out; + } + } + } + +/* +* Considering that HDCP2.2 is more secure than HDCP1.4, If the setup +* is capable of HDCP2.2, it is preferred to use HDCP2.2. +*/ + ret = data->funcs->hdcp2_capable (connector, &capable); +if (ret) { +drm_err (dev,"HDCP 2.x capability check failed %d\n" , ret); + goto out; + } +if (capable) { + data->enabled_type =DRM_MODE_HDCP_CONTENT_TYPE1 ; + ret = data->funcs->hdcp2_enable (connector); +if (!ret) { + check_link_interval =DRM_HDCP2_CHECK_PERIOD_MS ; + goto out; + } + } + +/* +* When HDCP2.2 fails and Content Type is not Type1, HDCP1.4 will +* be attempted. +*/ + ret =drm_hdcp_helper_hdcp1_capable (data, &capable); +if (ret) { +drm_err (dev,"HDCP 1.x capability check failed %d\n" , ret); + goto out; + } + if (capable && conn_state->content_type !=
DRM_MODE_HDCP_CONTENT_TYPE1) {drivers/gpu/drm/drm_hdcp.c +23
-0+ data->enabled_type =DRM_MODE_HDCP_CONTENT_TYPE0 ; + ret =drm_hdcp_helper_hdcp1_enable (data); +if (!ret) + check_link_interval =DRM_HDCP_CHECK_PERIOD_MS ; + } + +out: +if (!ret) { +schedule_delayed_work (&data->check_work, check_link_interval); +drm_hdcp_update_value (data,DRM_MODE_CONTENT_PROTECTION_ENABLED , + true); + } + +drm_hdcp_helper_driver_unlock (data); +if (ret) + data->driver_mutex =NULL ; + +out_data_mutex: +mutex_unlock (&data->mutex); +return ret; +} + +static int drm_hdcp_helper_disable_hdcp(struct drm_hdcp_helper_data*data)
drivers/gpu/drm/drm_hdcp.c +10
-0+{ +int ret =0 ; + +mutex_lock (&data->mutex); +drm_hdcp_helper_driver_lock (data); + +if (data->value ==DRM_MODE_CONTENT_PROTECTION_UNDESIRED ) + goto out; + + drm_dbg_kms(data->connector->dev, "[%s:%d] HDCP is beingdisabled...\n",
drivers/gpu/drm/drm_hdcp.c +3
-0+ data->connector->name, data->connector->base.id); + + drm_hdcp_update_value(data, DRM_MODE_CONTENT_PROTECTION_UNDESIRED,true);
drivers/gpu/drm/drm_hdcp.c +18
-0+ +if (data->enabled_type ==DRM_MODE_HDCP_CONTENT_TYPE1 ) + ret = data->funcs->hdcp2_disable (data->connector); +else + ret = data->funcs->hdcp1_disable (data->connector); + +drm_dbg_kms (data->connector->dev,"HDCP is disabled\n" ); + +out: +drm_hdcp_helper_driver_unlock (data); + data->driver_mutex =NULL ; +mutex_unlock (&data->mutex); +cancel_delayed_work_sync (&data->check_work); +return ret; +} + +/** +* drm_hdcp_helper_atomic_commit - Helper for drivers to call during commit to
+ * enable/disable HDCP
+ *
+ * @data: pointer to the @drm_hdcp_helper_data for the connector
+ * @state: pointer to the atomic state being committed
+ * @driver_mutex: driver-provided lock to be used while interacting with the driver
+ *
+ * This function can be used by display drivers to determine when HDCP should be
+ * enabled or disabled based on the connector state. It should be called during
+ * steady-state commits as well as connector enable/disable. The function will
+ * handle the HDCP authentication/encryption logic, calling back into the driver
+ * when source operations are necessary.
+ *
+ * @driver_mutex will be retained and used for the duration of the HDCP session
+ * since it will be needed for link checks and retries. This mutex is useful if
+ * the driver has shared resources across connectors which must be serialized.
+ * For example,driver_mutexcan be used for MST connectors sharing a common
+ * encoder which should not be accessed/changed concurrently. When the
+ * connector's session is torn down, the mutex will be forgotten by the helper
+ * for this connector until the next session.
+ */drivers/gpu/drm/drm_hdcp.c +13
-0+void drm_hdcp_helper_atomic_commit (struct drm_hdcp_helper_data *data, +struct drm_atomic_state *state, +struct mutex *driver_mutex) +{ +struct drm_connector *connector = data->connector; +struct drm_connector_state *conn_state; +bool type_changed; + + conn_state =drm_atomic_get_new_connector_state (state, connector); + + type_changed = conn_state->hdcp_content_type != data->enabled_type; + + if (conn_state->content_protection ==
DRM_MODE_CONTENT_PROTECTION_UNDESIRED) {drivers/gpu/drm/drm_hdcp.c +9
-0+drm_hdcp_helper_disable_hdcp (data); +return ; + } + +if (!conn_state->crtc) { +drm_hdcp_helper_disable_hdcp (data); + +/* Restore property to DESIRED so it's retried later */ + if (conn_state->content_protection ==
DRM_MODE_CONTENT_PROTECTION_ENABLED) {drivers/gpu/drm/drm_hdcp.c +10
-0+mutex_lock (&data->mutex); +drm_hdcp_update_value (data,DRM_MODE_CONTENT_PROTECTION_DESIRED , + true); +mutex_unlock (&data->mutex); + } +return ; + } + +/* Already enabled */ + if (conn_state->content_protection ==
DRM_MODE_CONTENT_PROTECTION_ENABLED)drivers/gpu/drm/drm_hdcp.c +23
-0+return ; + +/* Disable and re-enable HDCP on content type change */ +if (type_changed) +drm_hdcp_helper_disable_hdcp (data); + +drm_hdcp_helper_enable_hdcp (data, state, driver_mutex); +} +EXPORT_SYMBOL (drm_hdcp_helper_atomic_commit); + +static void drm_hdcp_helper_prop_work (struct work_struct *work) +{ +struct drm_hdcp_helper_data *data =container_of (work, + struct drm_hdcp_helper_data, + prop_work); +struct drm_connector *connector = data->connector; +struct drm_device *dev = connector->dev; + +drm_modeset_lock (&dev->mode_config.connection_mutex,NULL ); +mutex_lock (&data->mutex); + +/* +* This worker is only used to flip between ENABLED/DESIRED. Either of
drivers/gpu/drm/drm_hdcp.c +11
-0+* those to UNDESIRED is handled by core. If value == UNDESIRED, +* we're running just after hdcp has been disabled, so just exit +*/ +if (data->value !=DRM_MODE_CONTENT_PROTECTION_UNDESIRED ) +drm_hdcp_update_content_protection (connector, data->value); + +mutex_unlock (&data->mutex); +drm_modeset_unlock (&dev->mode_config.connection_mutex); +} + +static int drm_hdcp_hdcp1_check_link(struct drm_hdcp_helper_data*data)
drivers/gpu/drm/drm_hdcp.c +54
-0+{ +struct drm_connector *connector = data->connector; +struct drm_device *dev = connector->dev; +int ret; + +if (data->funcs->hdcp1_check_link) { + ret = data->funcs->hdcp1_check_link (connector); +if (ret) + goto retry; + } + +/* The link is checked differently for DP and HDMI */ +if (data->aux) { +u8 bstatus; + ret =drm_hdcp_remote_dpcd_read (data->aux,DP_AUX_HDCP_BSTATUS , + &bstatus,1 ); +if (ret) { +drm_err (dev,"Failed to read dpcd bstatus, %d\n" , ret); +return ret; + } +if (bstatus & (DP_BSTATUS_LINK_FAILURE |DP_BSTATUS_REAUTH_REQ )) + ret = -EINVAL ; + }else { + ret =drm_hdcp_helper_hdcp1_validate_ri (data); +if (ret) +drm_err (dev,"Ri' mismatch, check failed (%d)\n" , ret); + } +if (!ret) +return 0 ; + +retry: +drm_err (dev,"[%s:%d] HDCP link failed, retrying authentication\n" , + connector->name, connector->base.id); + + ret = data->funcs->hdcp1_disable (connector); +if (ret) { +drm_err (dev,"Failed to disable hdcp (%d)\n" , ret); +drm_hdcp_update_value (data,DRM_MODE_CONTENT_PROTECTION_DESIRED , + true); +return ret; + } + + ret =drm_hdcp_helper_hdcp1_enable (data); +if (ret) { +drm_err (dev,"Failed to enable hdcp (%d)\n" , ret); +drm_hdcp_update_value (data,DRM_MODE_CONTENT_PROTECTION_DESIRED , + true); +return ret; + } + +return 0 ; +} + +static int drm_hdcp_hdcp2_check_link(struct drm_hdcp_helper_data*data)
drivers/gpu/drm/drm_hdcp.c +34
-0+{ +struct drm_connector *connector = data->connector; +struct drm_device *dev = connector->dev; +int ret; + + ret = data->funcs->hdcp2_check_link (connector); +if (!ret) +return 0 ; + +drm_err (dev,"[%s:%d] HDCP2 link failed, retrying authentication\n" , + connector->name, connector->base.id); + + ret = data->funcs->hdcp2_disable (connector); +if (ret) { +drm_err (dev,"Failed to disable hdcp2 (%d)\n" , ret); +drm_hdcp_update_value (data,DRM_MODE_CONTENT_PROTECTION_DESIRED , + true); +return ret; + } + + ret = data->funcs->hdcp2_enable (connector); +if (ret) { +drm_err (dev,"Failed to enable hdcp2 (%d)\n" , ret); +drm_hdcp_update_value (data,DRM_MODE_CONTENT_PROTECTION_DESIRED , + true); +return ret; + } + +return 0 ; +} + +static void drm_hdcp_helper_check_work (struct work_struct *work) +{ + struct drm_hdcp_helper_data *data =container_of(to_delayed_work(work),
drivers/gpu/drm/drm_hdcp.c bool drm_hdcp_atomic_check(struct drm_connector *connector, · line 1431
Quoted 4 lines
drivers/gpu/drm/drm_hdcp.c +4
-0+ struct drm_hdcp_helper_data, + check_work); +unsigned long check_link_interval; +
Does this SW polling for Ri' mismatch need to be done even if the HW is capable of doing it on its own?
MSM HDCP 1x HW can periodically check Ri' mismatches and issue an interrupt if there is a mismatch. In that case this SW polling is not needed. So maybe check if the HW supports polling and if so skip this SW polling?
Quoted 441 lines
drivers/gpu/drm/drm_hdcp.c +29
-0+mutex_lock (&data->mutex); +if (data->value !=DRM_MODE_CONTENT_PROTECTION_ENABLED ) + goto out_data_mutex; + +drm_hdcp_helper_driver_lock (data); + +if (data->enabled_type ==DRM_MODE_HDCP_CONTENT_TYPE1 ) { +if (drm_hdcp_hdcp2_check_link (data)) + goto out; + check_link_interval =DRM_HDCP2_CHECK_PERIOD_MS ; + }else { +if (drm_hdcp_hdcp1_check_link (data)) + goto out; + check_link_interval =DRM_HDCP_CHECK_PERIOD_MS ; + } +schedule_delayed_work (&data->check_work, check_link_interval); + +out: +drm_hdcp_helper_driver_unlock (data); +out_data_mutex: +mutex_unlock (&data->mutex); +} + +/** +* drm_hdcp_helper_schedule_hdcp_check - Schedule a check link cycle. +* +* @data: Pointer to the HDCP helper data. +* +* This function will kick off a check link cycle on behalf of the caller. This
+ * can be used by DP short hpd interrupt handlers, where the driver must poke
+ * the helper to check the link is still valid.
+ */
+voiddrm_hdcp_helper_schedule_hdcp_check(struct drm_hdcp_helper_data *data)drivers/gpu/drm/drm_hdcp.c +42
-0+{ +schedule_delayed_work (&data->check_work,0 ); +} +EXPORT_SYMBOL (drm_hdcp_helper_schedule_hdcp_check); + +static struct drm_hdcp_helper_data * +drm_hdcp_helper_initialize (struct drm_connector *connector, +const struct drm_hdcp_helper_funcs *funcs, +bool attach_content_type_property) +{ +struct drm_hdcp_helper_data *out; +int ret; + + out =kzalloc (sizeof (*out),GFP_KERNEL ); +if (!out) +return ERR_PTR (-ENOMEM ); + + out->connector = connector; + out->funcs = funcs; + +mutex_init (&out->mutex); + out->value =DRM_MODE_CONTENT_PROTECTION_UNDESIRED ; + +INIT_DELAYED_WORK (&out->check_work, drm_hdcp_helper_check_work); +INIT_WORK (&out->prop_work, drm_hdcp_helper_prop_work); + + ret =drm_connector_attach_content_protection_property (connector, + attach_content_type_property); +if (ret) { +drm_hdcp_helper_destroy (out); +return ERR_PTR (ret); + } + +return out; +} + +/** +* drm_hdcp_helper_initialize_dp - Initializes the HDCP helpers for a +* DisplayPort connector +* +* @connector: pointer to the DisplayPort connector. +* @funcs: pointer to the vtable of HDCP helper funcs for this connector.
+ * @attach_content_type_property: True if thecontent_typeproperty should be
+ * attached.
+ *
+ * This function intializes the HDCP helper for the given DisplayPort connector.
+ * This involves creating the Content Protection property as well as the Content
+ * Type property (if desired). Upon success, it will return a pointer to the
+ * HDCP helper data. Ownership of the underlaying memory is transfered to the
+ * caller and should be freed usingdrm_hdcp_helper_destroy().
+ *
+ * Returns:
+ * Pointer to newly created HDCP helper data.PTR_ERRon failure.
+ */drivers/gpu/drm/drm_hdcp.c +22
-0+struct drm_hdcp_helper_data * +drm_hdcp_helper_initialize_dp (struct drm_connector *connector, +struct drm_dp_aux *aux, +const struct drm_hdcp_helper_funcs *funcs, +bool attach_content_type_property) +{ +struct drm_hdcp_helper_data *out; + + out =drm_hdcp_helper_initialize (connector, funcs, + attach_content_type_property); +if (IS_ERR (out)) +return out; + + out->aux = aux; + out->hdcp1_lut = &drm_hdcp_hdcp1_dpcd_lut; + +return out; +} +EXPORT_SYMBOL (drm_hdcp_helper_initialize_dp); + +/** +* drm_hdcp_helper_initialize_hdmi - Initializes the HDCP helpers for an HDMI
+ * connector
+ *
+ * @connector: pointer to the HDMI connector.
+ * @funcs: pointer to the vtable of HDCP helper funcs for this connector.
+ * @attach_content_type_property: True if thecontent_typeproperty should be
+ * attached.
+ *
+ * This function intializes the HDCP helper for the given HDMI connector. This
+ * involves creating the Content Protection property as well as the Content Type
+ * property (if desired). Upon success, it will return a pointer to the HDCP
+ * helper data. Ownership of the underlaying memory is transfered to the caller
+ * and should be freed usingdrm_hdcp_helper_destroy().
+ *
+ * Returns:
+ * Pointer to newly created HDCP helper data.PTR_ERRon failure.
+ */drivers/gpu/drm/drm_hdcp.c +24
-0+struct drm_hdcp_helper_data * +drm_hdcp_helper_initialize_hdmi (struct drm_connector *connector, +const struct drm_hdcp_helper_funcs *funcs, +bool attach_content_type_property) +{ +struct drm_hdcp_helper_data *out; + + out =drm_hdcp_helper_initialize (connector, funcs, + attach_content_type_property); +if (IS_ERR (out)) +return out; + + out->hdcp1_lut = &drm_hdcp_hdcp1_ddc_lut; + +return out; +} +EXPORT_SYMBOL (drm_hdcp_helper_initialize_hdmi); + +/** +* drm_hdcp_helper_destroy - Destroys the given HDCP helper data. +* +* @data: Pointer to the HDCP helper data. +* +* This function cleans up and destroys the HDCP helper data created by
+ *drm_hdcp_helper_initialize_dp()ordrm_hdcp_helper_initialize_hdmi().
+ */drivers/gpu/drm/drm_hdcp.c +26
-0+void drm_hdcp_helper_destroy (struct drm_hdcp_helper_data *data) +{ +struct drm_connector *connector; + +if (!data) +return ; + + connector = data->connector; + +/* +* If the connector is registered, it's possible userspace could kick +* off another HDCP enable, which would re-spawn the workers. +*/ +drm_WARN_ON (connector->dev, + connector->registration_state ==DRM_CONNECTOR_REGISTERED ); + +/* +* Now that the connector is not registered, check_work won't be run, +* but cancel any outstanding instances of it +*/ +cancel_delayed_work_sync (&data->check_work); + +/* +* We don't cancel prop_work in the same way as check_work since it +* requires connection_mutex which could be held while calling this +* function. Instead, we rely on the connector references grabbed before
drivers/gpu/drm/drm_hdcp.c +1
-0+* scheduling prop_work to ensure the connector is alive when
prop_workdrivers/gpu/drm/drm_hdcp.c +2
-0+* is run. So if we're in the destroy path (which is where this +* function should be called), we're "guaranteed" that prop_work is not
drivers/gpu/drm/drm_hdcp.c +7
-0+* active (tl;dr This Should Never Happen). +*/ +drm_WARN_ON (connector->dev,work_pending (&data->prop_work)); + +kfree (data); +} +EXPORT_SYMBOL (drm_hdcp_helper_destroy);include/drm/drm_hdcp.h +18
-0@@ -36,6 +36,7 @@#define DRM_HDCP_DDC_BKSV 0x00#define DRM_HDCP_DDC_RI_PRIME 0x08#define DRM_HDCP_DDC_AKSV 0x10 +#define DRM_HDCP_DDC_AINFO 0x15#define DRM_HDCP_DDC_AN 0x18#define DRM_HDCP_DDC_V_PRIME (h) (0x20 + h * 4)#define DRM_HDCP_DDC_BCAPS 0x40@@ -295,6 +296,19 @@ struct drm_atomic_state;struct drm_device ;struct drm_connector ; +struct drm_hdcp_ksv { +union { +u32 words[2 ]; +u8 bytes[DRM_HDCP_KSV_LEN ]; + }; +}; +struct drm_hdcp_an { +union { +u32 words[2 ]; +u8 bytes[DRM_HDCP_AN_LEN ]; + }; +}; +int drm_hdcp_check_ksvs_revoked (struct drm_device *dev,u8 *ksvs,u32 ksv_count); int drm_connector_attach_content_protection_property(@@ -303,9 +317,186 @@ void drm_hdcp_update_content_protection(structdrm_connector *connector, u64 val);bool drm_hdcp_atomic_check (struct drm_connector *connector,struct drm_atomic_state *state); +void drm_hdcp_atomic_commit (struct drm_atomic_state *state, +struct drm_connector *connector);/* Content Type classification for HDCP2.2 vs others */ #define DRM_MODE_HDCP_CONTENT_TYPE0 0#define DRM_MODE_HDCP_CONTENT_TYPE1 1 +/** +* struct drm_hdcp_helper_funcs - A vtable of function hooks for the hdcp helper
+ *
+ * These hooks are used by the hdcp helper to call into the driver/connector
+ * code to read/write to hw.
+ */include/drm/drm_hdcp.h +18
-0+struct drm_hdcp_helper_funcs { +/** +* @setup - Performs driver-specific setup before hdcp is enabled +* +* Returns: 0 on success, -errno on failure +*/ +int (*setup)(struct drm_connector *connector, +struct drm_atomic_state *state); + +/** +* @are_keys_valid - Checks if the HDCP transmitter keys are valid +* +* Returns: true if the display controller has valid keys loaded +*/ +bool (*are_keys_valid)(struct drm_connector *connector); + +/** +* @load_keys - Instructs the driver to load its HDCP transmitter keys
include/drm/drm_hdcp.h +25
-0+* +* Returns: 0 on success, -errno on failure +*/ +int (*load_keys)(struct drm_connector *connector); + +/** +* @hdcp2_capable - Checks if both source and sink support HDCP 2.x +* +* Returns: 0 on success, -errno on failure +*/ +int (*hdcp2_capable)(struct drm_connector *connector,bool *capable); + +/** +* @hdcp2_enable - Enables HDCP 2.x on the specified connector +* +* Since we don't have multiple examples of HDCP 2.x enablement, we +* provide the bare minimum support for HDCP 2.x help. Once we have +* more examples, perhaps we can be more helpful. +* +* Returns: 0 on success, -errno on failure +*/ +int (*hdcp2_enable)(struct drm_connector *connector); + +/** +* @hdcp2_check_link - Checks the HDCP 2.x link on a specified connector
include/drm/drm_hdcp.h +16
-0+* +* Returns: 0 on success, -errno on failure +*/ +int (*hdcp2_check_link)(struct drm_connector *connector); + +/** +* @hdcp2_disable - Disables HDCP 2.x on the specified connector +* +* Returns: 0 on success, -errno on failure +*/ +int (*hdcp2_disable)(struct drm_connector *connector); + +/** +* @hdcp1_read_an_aksv - Reads transmitter's An & Aksv from hardware +* +* Use this function if hardware allows reading the transmitter's An and
include/drm/drm_hdcp.h +11
-0+* Aksv values from the kernel. If your hardware will not allow this, +* use hdcp1_send_an_aksv() and implement the transmission in the +* driver. +* +* Returns: 0 on success, -errno on failure +*/ +int (*hdcp1_read_an_aksv)(struct drm_connector *connector,u32 *an, +u32 *aksv); + +/** +* @hdcp1_send_an_aksv - Sends transmitter's An & Aksv to the receiver
include/drm/drm_hdcp.h +2
-0+* +* Only implement this on hardware where An or Aksv are not accessible
include/drm/drm_hdcp.h +9
-0+* from the kernel. If these values can be read, use +* hdcp1_read_an_aksv() instead. +* +* Returns: 0 on success, -errno on failure +*/ +int (*hdcp1_send_an_aksv)(struct drm_connector *connector); + +/** +* @hdcp1_store_receiver_info - Stores the receiver's info in the transmitter
include/drm/drm_hdcp.h +9
-0+* +* Returns: 0 on success, -errno on failure +*/ +int (*hdcp1_store_receiver_info)(struct drm_connector *connector, +u32 *ksv,u32 status,u8 caps, +bool repeater_present); + +/** +* @hdcp1_enable_encryption - Enables encryption of the outgoing signal
include/drm/drm_hdcp.h +14
-0+* +* Returns: 0 on success, -errno on failure +*/ +int (*hdcp1_enable_encryption)(struct drm_connector *connector); + +/** +* @hdcp1_wait_for_r0 - Wait for transmitter to calculate R0 +* +* Returns: 0 on success, -errno on failure +*/ +int (*hdcp1_wait_for_r0)(struct drm_connector *connector); + +/** +* @hdcp1_match_ri - Matches the given Ri from the receiver with Ri in
include/drm/drm_hdcp.h +8
-0+* the transmitter +* +* Returns: 0 on success, -errno on failure +*/ +int (*hdcp1_match_ri)(struct drm_connector *connector,u32 ri_prime); + +/** +* @hdcp1_post_encryption - Allows the driver to confirm encryption and
include/drm/drm_hdcp.h +8
-0+* perform any post-processing +* +* Returns: 0 on success, -errno on failure +*/ +int (*hdcp1_post_encryption)(struct drm_connector *connector); + +/** +* @hdcp1_store_ksv_fifo - Write the receiver's KSV list to transmitter
include/drm/drm_hdcp.h +48
-0+* +* Returns: 0 on success, -errno on failure +*/ +int (*hdcp1_store_ksv_fifo)(struct drm_connector *connector, +u8 *ksv_fifo,u8 num_downstream, +u8 *bstatus,u32 *vprime); + +/** +* @hdcp1_check_link - Allows the driver to check the HDCP 1.x status +* on a specified connector +* +* Returns: 0 on success, -errno on failure +*/ +int (*hdcp1_check_link)(struct drm_connector *connector); + +/** +* @hdcp1_disable - Disables HDCP 1.x on the specified connector +* +* Returns: 0 on success, -errno on failure +*/ +int (*hdcp1_disable)(struct drm_connector *connector); +}; + +struct drm_hdcp_helper_data ; +struct drm_dp_aux ; +struct i2c_adapter ; +struct mutex ; + +struct drm_hdcp_helper_data * +drm_hdcp_helper_initialize_dp (struct drm_connector *connector, +struct drm_dp_aux *aux, +const struct drm_hdcp_helper_funcs *funcs, +bool attach_content_type_property); + +struct drm_hdcp_helper_data * +drm_hdcp_helper_initialize_hdmi (struct drm_connector *connector, +const struct drm_hdcp_helper_funcs *funcs, +bool attach_content_type_property); + +void drm_hdcp_helper_destroy (struct drm_hdcp_helper_data *data); + +int drm_hdcp_helper_hdcp1_capable (struct drm_hdcp_helper_data *data, +bool *capable); +void drm_hdcp_helper_atomic_commit (struct drm_hdcp_helper_data *data, +struct drm_atomic_state *state, +struct mutex *driver_mutex); + +void drm_hdcp_helper_schedule_hdcp_check(struct drm_hdcp_helper_data*data);
+
#endif
Sean Paul
reviewerRe: [Freedreno] [PATCH v2 04/13] drm/hdcp: Expand HDCP helper library for enable/disable/check
Quoted 40 lines · On Tue, Sep 21, 2021 at 04:34:59PM -0700, [email protected] wrote:
Quoted 39 lines · Sean Paul
From: Sean Paul <[email protected]>
This patch expands upon the HDCP helper library to manage HDCP enable, disable, and check.
Previous to this patch, the majority of the state management and sink interaction is tucked inside the Intel driver with the understanding that once a new platform supported HDCP we could make good decisions about what should be centralized. With the addition of HDCP support for Qualcomm, it's time to migrate the protocol-specific bits of HDCP authentication, key exchange, and link checks to the HDCP helper.
In terms of functionality, this migration is 1:1 with the Intel driver, however things are laid out a bit differently than with
intel_hdcp.c, which is why this is a separate patch from the i915 transition to the helper. On i915, the "shim" vtable is used to account for HDMI vs. DP vs. DP-MST differences whereas the helper library uses a LUT to account for the register offsets and a remote read function to route the messages. On i915, storing the sink information in the source is done inline whereas now we use the newdrm_hdcp_helper_funcsvtable to store and fetch information to/from source hw. Finally, instead of calling enable/disable directly from the driver, we'll leave that decision to the helper and by callingdrm_hdcp_helper_atomic_commit()from the driver. All told, this will centralize the protocol and state handling in the helper, ensuring we collect all of our bugs^Wlogic in one place.Signed-off-by Sean Paul <[email protected]>Link:
https://patchwork.freedesktop.org/patch/msgid/[email protected]
#v1Changes in v2:
-Fixed set-but-unused variable identified by 0-day--- drivers/gpu/drm/drm_hdcp.c | 1103 ++++++++++++++++++++++++++++++++++++ include/drm/drm_hdcp.h | 191 +++++++ 2 files changed, 1294 insertions(+)
Quoted 4 lines
drivers/gpu/drm/drm_hdcp.c
Quoted 4 lines
drivers/gpu/drm/drm_hdcp.c +0
-0
/snip
Quoted 9 lines
drivers/gpu/drm/drm_hdcp.c bool drm_hdcp_atomic_check(struct drm_connector *connector, · line 1431
Quoted 8 lines
drivers/gpu/drm/drm_hdcp.c +3
-0+static void drm_hdcp_helper_check_work (struct work_struct *work) +{ + struct drm_hdcp_helper_data *data =container_of(to_delayed_work(work),
drivers/gpu/drm/drm_hdcp.c +4
-0+ struct drm_hdcp_helper_data, + check_work); +unsigned long check_link_interval; +
Quoted 9 lines
Does this SW polling for Ri' mismatch need to be done even if the HW is capable of doing it
on its own?
MSM HDCP 1x HW can periodically check Ri' mismatches and issue an interrupt if there is a mismatch.
In that case this SW polling is not needed. So maybe check if the HW supports polling and if so
skip this SW polling?
One could certainly change this to be HW driven. There is also an interrupt on Intel for DP links which [re]schedules link check in the interrupt handler, something similar could be done for msm. Note that even on these Intel links which support the CP interrupt, the worker still runs on the normal cadence. I haven't considered relying solely on the interrupt since I want to be sure we didn't miss anything.
Sean
Quoted 14 lines
Quoted 14 lines
drivers/gpu/drm/drm_hdcp.c +14
-0+mutex_lock (&data->mutex); +if (data->value !=DRM_MODE_CONTENT_PROTECTION_ENABLED ) + goto out_data_mutex; + +drm_hdcp_helper_driver_lock (data); + +if (data->enabled_type ==DRM_MODE_HDCP_CONTENT_TYPE1 ) { +if (drm_hdcp_hdcp2_check_link (data)) + goto out; + check_link_interval =DRM_HDCP2_CHECK_PERIOD_MS ; + }else { +if (drm_hdcp_hdcp1_check_link (data)) + goto out; + check_link_interval =DRM_HDCP_CHECK_PERIOD_MS ;
Quoted 8 lines
drivers/gpu/drm/drm_hdcp.c bool drm_hdcp_atomic_check(struct drm_connector *connector, · line 1453
Quoted 8 lines
drivers/gpu/drm/drm_hdcp.c +8
-0+ } +schedule_delayed_work (&data->check_work, check_link_interval); + +out: +drm_hdcp_helper_driver_unlock (data); +out_data_mutex: +mutex_unlock (&data->mutex); +}
/snip
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Re: [Freedreno] [PATCH v2 04/13] drm/hdcp: Expand HDCP helper library for enable/disable/check
Hi Sean
Quoted 67 lines · Sean Paul
Quoted 40 lines · On Tue, Sep 21, 2021 at 04:34:59PM -0700, [email protected] wrote:
Quoted 39 lines · Sean Paul
From: Sean Paul <[email protected]>
This patch expands upon the HDCP helper library to manage HDCP enable, disable, and check.
Previous to this patch, the majority of the state management and sink interaction is tucked inside the Intel driver with the understanding that once a new platform supported HDCP we could make good decisions about what should be centralized. With the addition of HDCP support for Qualcomm, it's time to migrate the protocol-specific bits of HDCP authentication, key exchange, and link checks to the HDCP helper.
In terms of functionality, this migration is 1:1 with the Intel driver, however things are laid out a bit differently than with
intel_hdcp.c, which is why this is a separate patch from the i915 transition to the helper. On i915, the "shim" vtable is used to account for HDMI vs. DP vs. DP-MST differences whereas the helper library uses a LUT to account for the register offsets and a remote read function to route the messages. On i915, storing the sink information in the source is done inline whereas now we use the newdrm_hdcp_helper_funcsvtable to store and fetch information to/from source hw. Finally, instead of calling enable/disable directly from the driver, we'll leave that decision to the helper and by callingdrm_hdcp_helper_atomic_commit()from the driver. All told, this will centralize the protocol and state handling in the helper, ensuring we collect all of our bugs^Wlogic in one place.Signed-off-by Sean Paul <[email protected]>Link:
https://patchwork.freedesktop.org/patch/msgid/[email protected]
#v1Changes in v2:
-Fixed set-but-unused variable identified by 0-day--- drivers/gpu/drm/drm_hdcp.c | 1103 ++++++++++++++++++++++++++++++++++++ include/drm/drm_hdcp.h | 191 +++++++ 2 files changed, 1294 insertions(+)Quoted 4 lines
drivers/gpu/drm/drm_hdcp.c
Quoted 4 lines
drivers/gpu/drm/drm_hdcp.c +0
-0/snip
Quoted 9 lines
drivers/gpu/drm/drm_hdcp.c bool drm_hdcp_atomic_check(struct drm_connector *connector, · line 1431
Quoted 8 lines
drivers/gpu/drm/drm_hdcp.c +3
-0+static void drm_hdcp_helper_check_work (struct work_struct *work) +{ + struct drm_hdcp_helper_data *data =container_of(to_delayed_work(work),
drivers/gpu/drm/drm_hdcp.c +4
-0+ struct drm_hdcp_helper_data, + check_work); +unsigned long check_link_interval; +Quoted 9 lines
Does this SW polling for Ri' mismatch need to be done even if the HW is capable of doing it
on its own?
MSM HDCP 1x HW can periodically check Ri' mismatches and issue an interrupt if there is a mismatch.
In that case this SW polling is not needed. So maybe check if the HW supports polling and if so
skip this SW polling?
Quoted 8 lines
One could certainly change this to be HW driven. There is also an interrupt on Intel for DP links which [re]schedules link check in the interrupt handler, something similar could be done for msm. Note that even on these Intel links which support the CP interrupt, the worker still runs on the normal cadence. I haven't considered relying solely on the interrupt since I want to be sure we didn't miss anything.
Sean
I think we should have the support for HW polling added. From our experience, it has been pretty reliable for us and has a pretty consistent cadence in alignment with the spec. I dont quite understand why we should have both in chipsets capable of HW polling and am bit surprised if SW polling will catch something which HW polling and the subsequent interrupt has missed.
Quoted 25 lines
Quoted 15 lines
Quoted 15 lines
drivers/gpu/drm/drm_hdcp.c +14
-0+mutex_lock (&data->mutex); +if (data->value !=DRM_MODE_CONTENT_PROTECTION_ENABLED ) + goto out_data_mutex; + +drm_hdcp_helper_driver_lock (data); + +if (data->enabled_type ==DRM_MODE_HDCP_CONTENT_TYPE1 ) { +if (drm_hdcp_hdcp2_check_link (data)) + goto out; + check_link_interval =DRM_HDCP2_CHECK_PERIOD_MS ; + }else { +if (drm_hdcp_hdcp1_check_link (data)) + goto out; + check_link_interval =DRM_HDCP_CHECK_PERIOD_MS ;Quoted 8 lines
drivers/gpu/drm/drm_hdcp.c bool drm_hdcp_atomic_check(struct drm_connector *connector, · line 1453
Quoted 8 lines
drivers/gpu/drm/drm_hdcp.c +8
-0+ } +schedule_delayed_work (&data->check_work, check_link_interval); + +out: +drm_hdcp_helper_driver_unlock (data); +out_data_mutex: +mutex_unlock (&data->mutex); +}/snip
Sean Paul
reviewerPATCH v2 5/13 drm/i915/hdcp: Consolidate HDCP setup/state cache
In reply to Sean PaulFrom: Sean Paul <[email protected]>
Stick all of the setup for HDCP into a dedicated function. No functional change, but this will facilitate moving HDCP logic into helpers.
Changes in v2:
-None
--- drivers/gpu/drm/i915/display/intel_hdcp.c | 52 +++++++++++++++-------- 1 file changed, 35 insertions(+), 17 deletions(-)
drivers/gpu/drm/i915/display/intel_hdcp.c +35 -17
@@ -2167,6 +2167,37 @@ static enum mei_fw_tc intel_get_mei_fw_tc(enum transcoder cpu_transcoder) } } +static int +_intel_hdcp_setup (struct intel_connector *connector, +const struct intel_crtc_state *pipe_config,u8 content_type) +{ +struct drm_i915_private *dev_priv =to_i915 (connector->base.dev); +struct intel_digital_port *dig_port =intel_attached_dig_port (connector); +struct intel_hdcp *hdcp = &connector->hdcp; +int ret =0 ; + +if (!connector->encoder) { +drm_err (&dev_priv->drm,"[%s:%d] encoder is not initialized\n" , + connector->base.name, connector->base.base.id); +return -ENODEV ; + } + + hdcp->content_type = content_type; + +if (intel_crtc_has_type (pipe_config,INTEL_OUTPUT_DP_MST )) { + hdcp->cpu_transcoder = pipe_config->mst_master_transcoder; + hdcp->stream_transcoder = pipe_config->cpu_transcoder; + }else { + hdcp->cpu_transcoder = pipe_config->cpu_transcoder; + hdcp->stream_transcoder =INVALID_TRANSCODER ; + } + +if (DISPLAY_VER (dev_priv) >=12 ) + dig_port->hdcp_port_data.fw_tc =intel_get_mei_fw_tc (hdcp->cpu_transcoder); + +return ret; +} +static int initialize_hdcp_port_data (struct intel_connector *connector,struct intel_digital_port *dig_port,const struct intel_hdcp_shim *shim)
@@ -2306,28 +2337,14 @@ int intel_hdcp_enable(struct intel_connector *connector,if (!hdcp->shim)return -ENOENT ; -if (!connector->encoder) { -drm_err (&dev_priv->drm,"[%s:%d] encoder is not initialized\n" , - connector->base.name, connector->base.base.id); -return -ENODEV ; - } -mutex_lock (&hdcp->mutex);mutex_lock (&dig_port->hdcp_mutex);drm_WARN_ON (&dev_priv->drm, hdcp->value ==DRM_MODE_CONTENT_PROTECTION_ENABLED ); - hdcp->content_type = content_type; - -if (intel_crtc_has_type (pipe_config,INTEL_OUTPUT_DP_MST )) { - hdcp->cpu_transcoder = pipe_config->mst_master_transcoder; - hdcp->stream_transcoder = pipe_config->cpu_transcoder; - }else { - hdcp->cpu_transcoder = pipe_config->cpu_transcoder; - hdcp->stream_transcoder =INVALID_TRANSCODER ; - } -if (DISPLAY_VER (dev_priv) >=12 ) - dig_port->hdcp_port_data.fw_tc =intel_get_mei_fw_tc (hdcp->cpu_transcoder); + ret =_intel_hdcp_setup (connector, pipe_config, content_type); +if (ret) + goto out;/* * Considering that HDCP2.2 is more secure than HDCP1.4, If the setup
@@ -2355,6 +2372,7 @@ int intel_hdcp_enable(struct intel_connector *connector, true); } +out:mutex_unlock (&dig_port->hdcp_mutex);mutex_unlock (&hdcp->mutex);return ret;
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Sean Paul
reviewerPATCH v2 6/13 drm/i915/hdcp: Retain hdcp_capable return codes
In reply to Sean PaulFrom: Sean Paul <[email protected]>
The shim functions return error codes, but they are discarded in intel_hdcp.c. This patch plumbs the return codes through so they are properly handled.
Changes in v2:
-None
--- .../drm/i915/display/intel_display_debugfs.c | 9 +++- drivers/gpu/drm/i915/display/intel_hdcp.c | 51 ++++++++++--------- drivers/gpu/drm/i915/display/intel_hdcp.h | 4 +- 3 files changed, 37 insertions(+), 27 deletions(-)
drivers/gpu/drm/i915/display/intel_display_debugfs.c +7 -2
@@ -644,6 +644,7 @@ static void intel_panel_info(struct seq_file *m, struct intel_panel *panel)static void intel_hdcp_info (struct seq_file *m,struct intel_connector *intel_connector) { +int ret;bool hdcp_cap, hdcp2_cap;if (!intel_connector->hdcp.shim) {
@@ -651,8 +652,12 @@ static void intel_hdcp_info(struct seq_file *m, goto out; } - hdcp_cap =intel_hdcp_capable (intel_connector); - hdcp2_cap =intel_hdcp2_capable (intel_connector); + ret =intel_hdcp_capable (intel_connector, &hdcp_cap); +if (ret) + hdcp_cap = false; + ret =intel_hdcp2_capable (intel_connector, &hdcp2_cap); +if (ret) + hdcp2_cap = false;if (hdcp_cap)seq_puts (m,"HDCP1.4 " );
drivers/gpu/drm/i915/display/intel_hdcp.c +28 -23
112 lines not on this page · raw message
drivers/gpu/drm/i915/display/intel_hdcp.h +2 -2
@@ -33,8 +33,8 @@ void intel_hdcp_update_pipe(struct intel_atomic_state *state,const struct intel_crtc_state *crtc_state, const struct drm_connector_state *conn_state);bool is_hdcp_supported (struct drm_i915_private *dev_priv,enum port port); -bool intel_hdcp_capable (struct intel_connector *connector); -bool intel_hdcp2_capable (struct intel_connector *connector); +int intel_hdcp_capable (struct intel_connector *connector,bool *capable); +int intel_hdcp2_capable (struct intel_connector *connector,bool *capable);void intel_hdcp_component_init (struct drm_i915_private *dev_priv);void intel_hdcp_component_fini (struct drm_i915_private *dev_priv);void intel_hdcp_cleanup (struct intel_connector *connector);
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Sean Paul
reviewerPATCH v2 7/13 drm/i915/hdcp: Use HDCP helpers for i915
In reply to Sean PaulFrom: Sean Paul <[email protected]>
Now that all of the HDCP 1.x logic has been migrated to the central HDCP helpers, use it in the i915 driver.
The majority of the driver code for HDCP 1.x will live in intel_hdcp.c, however there are a few helper hooks which are connector-specific and need to be partially or fully implemented in the intel_dp_hdcp.c or intel_hdmi.c.
We'll leave most of the HDCP 2.x code alone since we don't have another implementation of HDCP 2.x to use as reference for what should and should not live in the drm helpers. The helper will call the overly general enable/disable/is_capable HDCP 2.x callbacks and leave the interesting stuff for the driver. Once we have another HDCP 2.x implementation, we should do a similar migration.
Changes in v2:
-Fix mst helper function pointer reported by 0-day
--- drivers/gpu/drm/i915/display/intel_ddi.c | 29 +- .../drm/i915/display/intel_display_debugfs.c | 6 +- .../drm/i915/display/intel_display_types.h | 58 +- drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 345 +++---- drivers/gpu/drm/i915/display/intel_dp_mst.c | 17 +- drivers/gpu/drm/i915/display/intel_hdcp.c | 935 +++--------------- drivers/gpu/drm/i915/display/intel_hdcp.h | 30 +- drivers/gpu/drm/i915/display/intel_hdmi.c | 256 ++--- 8 files changed, 417 insertions(+), 1259 deletions(-)
drivers/gpu/drm/i915/display/intel_ddi.c +21 -8
@@ -26,6 +26,7 @@*/ #include <drm/drm_scdc_helper.h> +#include <drm/drm_hdcp.h> #include "i915_drv.h" #include "intel_audio.h"
@@ -3131,6 +3132,9 @@ static void intel_enable_ddi(struct intel_atomic_state *state,const struct intel_crtc_state *crtc_state, const struct drm_connector_state *conn_state) { + struct intel_connector *connector = to_intel_connector(conn_state->connector); +struct intel_digital_port *dig_port =enc_to_dig_port (encoder); +drm_WARN_ON (state->base.dev, crtc_state->has_pch_encoder);if (!crtc_state->bigjoiner_slave)
@@ -3147,12 +3151,10 @@ static void intel_enable_ddi(struct intel_atomic_state *state,else intel_enable_ddi_dp (state, encoder, crtc_state, conn_state); -/* Enable hdcp if it's desired */ -if (conn_state->content_protection == -DRM_MODE_CONTENT_PROTECTION_DESIRED ) -intel_hdcp_enable (to_intel_connector (conn_state->connector), - crtc_state, - (u8 )conn_state->hdcp_content_type); +if (connector->hdcp_helper_data) +drm_hdcp_helper_atomic_commit (connector->hdcp_helper_data, + &state->base, + &dig_port->hdcp_mutex); } static void intel_disable_ddi_dp(struct intel_atomic_state *state,
@@ -3212,7 +3214,13 @@ static void intel_disable_ddi(struct intel_atomic_state *state,const struct intel_crtc_state *old_crtc_state, const struct drm_connector_state *old_conn_state) { - intel_hdcp_disable(to_intel_connector(old_conn_state->connector)); + struct intel_connector *connector = to_intel_connector(old_conn_state->connector); +struct intel_digital_port *dig_port =enc_to_dig_port (encoder); + +if (connector->hdcp_helper_data) +drm_hdcp_helper_atomic_commit (connector->hdcp_helper_data, + &state->base, + &dig_port->hdcp_mutex); if (intel_crtc_has_type(old_crtc_state, INTEL_OUTPUT_HDMI)) intel_disable_ddi_hdmi(state, encoder, old_crtc_state,
@@ -3243,13 +3251,18 @@ void intel_ddi_update_pipe(struct intel_atomic_state *state,const struct intel_crtc_state *crtc_state, const struct drm_connector_state *conn_state) { + struct intel_connector *connector = to_intel_connector(conn_state->connector); +struct intel_digital_port *dig_port =enc_to_dig_port (encoder);if (!intel_crtc_has_type (crtc_state,INTEL_OUTPUT_HDMI ) && !intel_encoder_is_mst (encoder))intel_ddi_update_pipe_dp (state, encoder, crtc_state, conn_state); -intel_hdcp_update_pipe (state ,encoder ,crtc_state ,conn_state ); +if (connector->hdcp_helper_data) +drm_hdcp_helper_atomic_commit (connector->hdcp_helper_data, + &state->base, + &dig_port->hdcp_mutex); } static void
drivers/gpu/drm/i915/display/intel_display_debugfs.c +4 -2
@@ -5,6 +5,7 @@#include <drm/drm_debugfs.h> #include <drm/drm_fourcc.h> +#include <drm/drm_hdcp.h> #include "i915_debugfs.h" #include "intel_display_debugfs.h"
@@ -652,10 +653,11 @@ static void intel_hdcp_info(struct seq_file *m, goto out; } - ret =intel_hdcp_capable (intel_connector, &hdcp_cap); + ret =drm_hdcp_helper_hdcp1_capable (intel_connector->hdcp_helper_data, + &hdcp_cap);if (ret) hdcp_cap = false; - ret =intel_hdcp2_capable (intel_connector, &hdcp2_cap); + ret =intel_hdcp2_capable (&intel_connector->base, &hdcp2_cap);if (ret) hdcp2_cap = false;
drivers/gpu/drm/i915/display/intel_display_types.h +1 -57
77 lines not on this page · raw message
drivers/gpu/drm/i915/display/intel_dp_hdcp.c +119 -226
426 lines not on this page · raw message
drivers/gpu/drm/i915/display/intel_dp_mst.c +10 -7
@@ -40,7 +40,6 @@#include "intel_dp_hdcp.h" #include "intel_dp_mst.h" #include "intel_dpio_phy.h" -#include "intel_hdcp.h" #include "intel_hotplug.h" #include "skl_scaler.h"
@@ -374,7 +373,10 @@ static void intel_mst_disable_dp(struct intel_atomic_state *state,drm_dbg_kms (&i915->drm,"active links %d\n" , intel_dp->active_mst_links); -intel_hdcp_disable (intel_mst->connector); +if (connector->hdcp_helper_data) +drm_hdcp_helper_atomic_commit (connector->hdcp_helper_data, + &state->base, + &dig_port->hdcp_mutex);drm_dp_mst_reset_vcpi_slots (&intel_dp->mst_mgr, connector->port);
@@ -544,6 +546,8 @@ static void intel_mst_enable_dp(struct intel_atomic_state *state,struct intel_digital_port *dig_port = intel_mst->primary;struct intel_dp *intel_dp = &dig_port->dp;struct drm_i915_private *dev_priv =to_i915 (encoder->base.dev); +struct intel_connector *connector = +to_intel_connector (conn_state->connector);enum transcoder trans = pipe_config->cpu_transcoder;drm_WARN_ON (&dev_priv->drm, pipe_config->has_pch_encoder);
@@ -574,11 +578,10 @@ static void intel_mst_enable_dp(struct intel_atomic_state *state,intel_audio_codec_enable (encoder, pipe_config, conn_state);/* Enable hdcp if it's desired */ -if (conn_state->content_protection == -DRM_MODE_CONTENT_PROTECTION_DESIRED ) -intel_hdcp_enable (to_intel_connector (conn_state->connector), - pipe_config, - (u8 )conn_state->hdcp_content_type); +if (connector->hdcp_helper_data) +drm_hdcp_helper_atomic_commit (connector->hdcp_helper_data, + &state->base, + &dig_port->hdcp_mutex); } static bool intel_dp_mst_enc_get_hw_state(struct intel_encoder *encoder,
drivers/gpu/drm/i915/display/intel_hdcp.c +152 -783
1,164 lines not on this page · raw message
drivers/gpu/drm/i915/display/intel_hdcp.h +22 -8
@@ -12,6 +12,7 @@struct drm_connector ;struct drm_connector_state ; +struct drm_hdcp_an ;struct drm_i915_private ;struct intel_atomic_state ;struct intel_connector ;
@@ -25,16 +26,29 @@ enum transcoder;int intel_hdcp_init (struct intel_connector *connector,struct intel_digital_port *dig_port,const struct intel_hdcp_shim *hdcp_shim); -int intel_hdcp_enable (struct intel_connector *connector, -const struct intel_crtc_state *pipe_config,u8 content_type); -int intel_hdcp_disable (struct intel_connector *connector); -void intel_hdcp_update_pipe (struct intel_atomic_state *state, -struct intel_encoder *encoder, -const struct intel_crtc_state *crtc_state, -const struct drm_connector_state *conn_state); +int intel_hdcp_setup (struct drm_connector *drm_connector, +struct drm_atomic_state *state); +int intel_hdcp_load_keys (struct drm_connector *drm_connector);bool is_hdcp_supported (struct drm_i915_private *dev_priv,enum port port);int intel_hdcp_capable (struct intel_connector *connector,bool *capable); -int intel_hdcp2_capable (struct intel_connector *connector,bool *capable); +int intel_hdcp2_capable (struct drm_connector *drm_connector,bool *capable); +int intel_hdcp2_enable (struct drm_connector *drm_connector); +int intel_hdcp2_disable (struct drm_connector *drm_connector); +int intel_hdcp2_check_link (struct drm_connector *drm_connector); +int intel_hdcp1_store_receiver_info (struct drm_connector *drm_connector, +u32 *ksv,u32 status,u8 caps, +bool repeater_present); +int intel_hdcp1_read_an (struct drm_connector *drm_connector, +struct drm_hdcp_an *an); +int intel_hdcp1_enable_encryption (struct drm_connector *drm_connector); +int intel_hdcp1_wait_for_r0 (struct drm_connector *drm_connector); +int intel_hdcp1_match_ri (struct drm_connector *drm_connector,u32 ri_prime); +int intel_hdcp1_post_encryption (struct drm_connector *drm_connector); +int intel_hdcp1_store_ksv_fifo (struct drm_connector *drm_connector, +u8 *ksv_fifo,u8 num_downstream,u8 *bstatus, +u32 *v_prime); +int intel_hdcp1_check_link (struct drm_connector *drm_connector); +int intel_hdcp1_disable (struct drm_connector *drm_connector);void intel_hdcp_component_init (struct drm_i915_private *dev_priv);void intel_hdcp_component_fini (struct drm_i915_private *dev_priv);void intel_hdcp_cleanup (struct intel_connector *connector);
drivers/gpu/drm/i915/display/intel_hdmi.c +88 -168
334 lines not on this page · raw message
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
kernel test robot
build botRe: [Intel-gfx] [PATCH v2 07/13] drm/i915/hdcp: Use HDCP helpers for i915
I love your patch! Yet something to improve:
Hi Sean,
I love your patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-tip/drm-tip next-20210916] [cannot apply to robh/for-next linus/master v5.15-rc1]
[If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Sean-Paul/drm-hdcp-Pull-HDCP-auth-exchange-check-into-helpers/20210916-044145 base: git://anongit.freedesktop.org/drm-intel for-linux-next config: x86_64-randconfig-r033-20210916 (attached as .config) compiler: clang version 14.0.0 (https://github.com/llvm/llvm-project c8b3d7d6d6de37af68b2f379d0e37304f78e115f)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/eb031b7a8eac1f8c6f61fee94daa7fd43945ce96
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Sean-Paul/drm-hdcp-Pull-HDCP-auth-exchange-check-into-helpers/20210916-044145 git checkout eb031b7a8eac1f8c6f61fee94daa7fd43945ce96
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 ARCH=x86_64
If you fix the issue, kindly add following tag as appropriate
All errors (new ones prefixed by >>):
In file included from <built-in>:4:
>> drivers/gpu/drm/i915/display/intel_hdcp.h:30:15: error: declaration of 'struct drm_atomic_state' will not be visible outside of this function [-Werror,-Wvisibility]
struct drm_atomic_state *state);
^1 error generated.
vim +30 drivers/gpu/drm/i915/display/intel_hdcp.h
25
26 int intel_hdcp_init(struct intel_connector *connector,
27 struct intel_digital_port *dig_port,
28 const struct intel_hdcp_shim *hdcp_shim);
29 int intel_hdcp_setup(struct drm_connector *drm_connector,
> 30 struct drm_atomic_state *state);
31 int intel_hdcp_load_keys(struct drm_connector *drm_connector);
32 bool is_hdcp_supported(struct drm_i915_private *dev_priv, enum port port);
33 int intel_hdcp_capable(struct intel_connector *connector, bool *capable);
34 int intel_hdcp2_capable(struct drm_connector *drm_connector, bool *capable);
35 int intel_hdcp2_enable(struct drm_connector *drm_connector);
36 int intel_hdcp2_disable(struct drm_connector *drm_connector);
37 int intel_hdcp2_check_link(struct drm_connector *drm_connector);
38 int intel_hdcp1_store_receiver_info(struct drm_connector *drm_connector,
39 u32 *ksv, u32 status, u8 caps,
40 bool repeater_present);
41 int intel_hdcp1_read_an(struct drm_connector *drm_connector,
42 struct drm_hdcp_an *an);
43 int intel_hdcp1_enable_encryption(struct drm_connector *drm_connector);
44 int intel_hdcp1_wait_for_r0(struct drm_connector *drm_connector);
45 int intel_hdcp1_match_ri(struct drm_connector *drm_connector, u32 ri_prime);
46 int intel_hdcp1_post_encryption(struct drm_connector *drm_connector);
47 int intel_hdcp1_store_ksv_fifo(struct drm_connector *drm_connector,
48 u8 *ksv_fifo, u8 num_downstream, u8 *bstatus,
49 u32 *v_prime);
50 int intel_hdcp1_check_link(struct drm_connector *drm_connector);
51 int intel_hdcp1_disable(struct drm_connector *drm_connector);
52 void intel_hdcp_component_init(struct drm_i915_private *dev_priv);
53 void intel_hdcp_component_fini(struct drm_i915_private *dev_priv);
54 void intel_hdcp_cleanup(struct intel_connector *connector);
55 void intel_hdcp_handle_cp_irq(struct intel_connector *connector);
56 ---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all(a)lists.01.org
Sean Paul
reviewerPATCH v2 8/13 drm/msm/dpu_kms: Re-order dpu includes
In reply to Sean PaulFrom: Sean Paul <[email protected]>
Make includes alphabetical in dpu_kms.c
Changes in v2:
-None
--- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c +4 -4
@@ -21,14 +21,14 @@#include "msm_gem.h" #include "disp/msm_disp_snapshot.h" -#include "dpu_kms.h" #include "dpu_core_irq.h" +#include "dpu_crtc.h" +#include "dpu_encoder.h" #include "dpu_formats.h" #include "dpu_hw_vbif.h" -#include "dpu_vbif.h" -#include "dpu_encoder.h" +#include "dpu_kms.h" #include "dpu_plane.h" -#include "dpu_crtc.h" +#include "dpu_vbif.h" #define CREATE_TRACE_POINTS #include "dpu_trace.h"
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Re: [PATCH v2 08/13] drm/msm/dpu_kms: Re-order dpu includes
Quoting Sean Paul (2021-09-15 13:38:27)
Quoted 10 lines
From: Sean Paul <[email protected]>
Make includes alphabetical in
dpu_kms.cSigned-off-by Sean Paul <[email protected]>Changes in v2:
-None
---
Re: [Freedreno] [PATCH v2 08/13] drm/msm/dpu_kms: Re-order dpu includes
In reply to Sean PaulQuoted 5 lines · Sean Paul
From: Sean Paul <[email protected]>
Make includes alphabetical in
dpu_kms.cSigned-off-by Sean Paul <[email protected]>
Quoted 34 lines
Link:
https://patchwork.freedesktop.org/patch/msgid/[email protected]
#v1Changes in v2:
(quoted diff) +0
-2-None --- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-)drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c +4
-4@@ -21,14 +21,14 @@#include "msm_gem.h" #include "disp/msm_disp_snapshot.h" -#include "dpu_kms.h" #include "dpu_core_irq.h" +#include "dpu_crtc.h" +#include "dpu_encoder.h" #include "dpu_formats.h" #include "dpu_hw_vbif.h" -#include "dpu_vbif.h" -#include "dpu_encoder.h" +#include "dpu_kms.h" #include "dpu_plane.h" -#include "dpu_crtc.h" +#include "dpu_vbif.h" #define CREATE_TRACE_POINTS #include "dpu_trace.h"
Sean Paul
reviewerPATCH v2 9/13 drm/msm/dpu: Remove useless checks in dpu_encoder
In reply to Sean PaulFrom: Sean Paul <[email protected]>
A couple more useless checks to remove in dpu_encoder.
Changes in v2:
-None
--- drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 12 ------------ 1 file changed, 12 deletions(-)
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c +0 -12
@@ -1153,10 +1153,6 @@ static void dpu_encoder_virt_enable(struct drm_encoder *drm_enc)struct msm_drm_private *priv;struct drm_display_mode *cur_mode =NULL ; -if (!drm_enc) { -DPU_ERROR ("invalid encoder\n" ); -return ; - } dpu_enc =to_dpu_encoder_virt (drm_enc);mutex_lock (&dpu_enc->enc_lock);
@@ -1203,14 +1199,6 @@ static void dpu_encoder_virt_disable(struct drm_encoder *drm_enc)struct msm_drm_private *priv;int i =0 ; -if (!drm_enc) { -DPU_ERROR ("invalid encoder\n" ); -return ; - }else if (!drm_enc->dev) { -DPU_ERROR ("invalid dev\n" ); -return ; - } - dpu_enc =to_dpu_encoder_virt (drm_enc);DPU_DEBUG_ENC (dpu_enc,"\n" );
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Re: [PATCH v2 09/13] drm/msm/dpu: Remove useless checks in dpu_encoder
Quoting Sean Paul (2021-09-15 13:38:28)
Quoted 10 lines
From: Sean Paul <[email protected]>
A couple more useless checks to remove in
dpu_encoder.Signed-off-by Sean Paul <[email protected]>Changes in v2:
-None
---
Sean Paul
reviewerPATCH v2 10/13 drm/msm/dpu: Remove encoder->enable() hack
In reply to Sean PaulFrom: Sean Paul <[email protected]>
encoder->commit() was being misused because there were some global resources which needed to be tweaked in encoder->enable() which were not accessible in dpu_encoder.c. That is no longer true and the redirect serves no purpose any longer. So remove the indirection.
Changes in v2:
-None
--- drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 5 +---- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 22 --------------------- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 2 -- drivers/gpu/drm/msm/disp/dpu1/dpu_trace.h | 4 ---- 4 files changed, 1 insertion(+), 32 deletions(-)
drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c +1 -4
@@ -2122,11 +2122,8 @@ static void dpu_encoder_frame_done_timeout(struct timer_list *t)static const struct drm_encoder_helper_funcs dpu_encoder_helper_funcs = { .mode_set = dpu_encoder_virt_mode_set, .disable = dpu_encoder_virt_disable, - .enable = dpu_kms_encoder_enable, + .enable = dpu_encoder_virt_enable, .atomic_check = dpu_encoder_virt_atomic_check, - -/* This is called by dpu_kms_encoder_enable */ - .commit = dpu_encoder_virt_enable, };static const struct drm_encoder_funcs dpu_encoder_funcs = {
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c +0 -22
@@ -381,28 +381,6 @@ static void dpu_kms_flush_commit(struct msm_kms *kms, unsigned crtc_mask) } } -/* -* Override the encoder enable since we need to setup the inline rotator and do -* some crtc magic before enabling any bridge that might be present. -*/ -void dpu_kms_encoder_enable (struct drm_encoder *encoder) -{ -const struct drm_encoder_helper_funcs *funcs = encoder->helper_private; -struct drm_device *dev = encoder->dev; -struct drm_crtc *crtc; - -/* Forward this enable call to the commit hook */ -if (funcs && funcs->commit) - funcs->commit (encoder); - -drm_for_each_crtc (crtc, dev) { -if (!(crtc->state->encoder_mask &drm_encoder_mask (encoder))) -continue ; - -trace_dpu_kms_enc_enable (DRMID (crtc)); - } -} -static void dpu_kms_complete_commit (struct msm_kms *kms,unsigned crtc_mask) {struct dpu_kms *dpu_kms =to_dpu_kms (kms);
drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h +0 -2
@@ -248,8 +248,6 @@ void *dpu_debugfs_get_root(struct dpu_kms *dpu_kms);int dpu_enable_vblank (struct msm_kms *kms,struct drm_crtc *crtc);void dpu_disable_vblank (struct msm_kms *kms,struct drm_crtc *crtc); -void dpu_kms_encoder_enable (struct drm_encoder *encoder); -/** * dpu_kms_get_clk_rate() - get the clock rate * @dpu_kms: pointer to dpu_kms structure
drivers/gpu/drm/msm/disp/dpu1/dpu_trace.h +0 -4
@@ -266,10 +266,6 @@ DEFINE_EVENT(dpu_drm_obj_template, dpu_crtc_complete_commit, TP_PROTO(uint32_t drm_id), TP_ARGS(drm_id) ); -DEFINE_EVENT (dpu_drm_obj_template, dpu_kms_enc_enable, - TP_PROTO(uint32_t drm_id), -TP_ARGS (drm_id) -);DEFINE_EVENT (dpu_drm_obj_template, dpu_kms_commit, TP_PROTO(uint32_t drm_id), TP_ARGS(drm_id)
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Re: [PATCH v2 10/13] drm/msm/dpu: Remove encoder->enable() hack
Quoting Sean Paul (2021-09-15 13:38:29)
Quoted 6 lines
From: Sean Paul <[email protected]>
encoder->commit()was being misused because there were some global resources which needed to be tweaked inencoder->enable()which were not accessible indpu_encoder.c. That is no longer true and the redirect serves no purpose any longer. So remove the indirection.
When did it become false? Just curious when this became obsolete.
Quoted 7 lines
Signed-off-by Sean Paul <[email protected]>Changes in v2:
-None
---
Sean Paul
reviewerRe: [PATCH v2 10/13] drm/msm/dpu: Remove encoder->enable() hack
Quoted 9 lines · Stephen Boyd
Quoting Sean Paul (2021-09-15 13:38:29)
Quoted 6 lines
From: Sean Paul <[email protected]>
encoder->commit()was being misused because there were some global resources which needed to be tweaked inencoder->enable()which were not accessible indpu_encoder.c. That is no longer true and the redirect serves no purpose any longer. So remove the indirection.When did it become false? Just curious when this became obsolete.
In commit
commit cd6d923167b1bf3e051f9d90fa129456d78ef06e
Author: Rob Clark <[email protected]> Date: Thu Aug 29 09:45:17 2019 -0700
drm/msm/dpu: async commit support
There was a call to dpu_crtc_commit_kickoff() which was removed from dpu_kms_encoder_enable(). That was the bit which required the back-and-forth between ->enable() and ->commit().
Quoted 11 lines
Quoted 8 lines
Signed-off-by Sean Paul <[email protected]>Changes in v2:
-None
---Reviewed-by Stephen Boyd <[email protected]>Tested-by Stephen Boyd <[email protected]>
Thanks!
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Sean Paul
reviewerPATCH v2 11/13 drm/msm/dp: Re-order dp_audio_put in deinit_sub_modules
In reply to Sean PaulFrom: Sean Paul <[email protected]>
Audio is initialized last, it should be de-initialized first to match the order in dp_init_sub_modules().
Changes in v2:
-None
--- drivers/gpu/drm/msm/dp/dp_display.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/msm/dp/dp_display.c +1 -1
@@ -714,9 +714,9 @@ static int dp_irq_hpd_handle(struct dp_display_private *dp, u32 data)static void dp_display_deinit_sub_modules (struct dp_display_private *dp) {dp_debug_put (dp->debug); +dp_audio_put (dp->audio);dp_panel_put (dp->panel);dp_aux_put (dp->aux); -dp_audio_put (dp->audio); }static int dp_init_sub_modules (struct dp_display_private *dp)
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Re: [PATCH v2 11/13] drm/msm/dp: Re-order dp_audio_put in deinit_sub_modules
Quoting Sean Paul (2021-09-15 13:38:30)
Quoted 4 lines
From: Sean Paul <[email protected]>
Audio is initialized last, it should be de-initialized first to match the order in
dp_init_sub_modules().
I don't really understand why the driver is written with all this "get" stuff but sure.
Quoted 7 lines
Signed-off-by Sean Paul <[email protected]>Changes in v2:
-None
---
Sean Paul
reviewerPATCH v2 12/13 dt-bindings: msm/dp: Add bindings for HDCP registers
In reply to Sean PaulFrom: Sean Paul <[email protected]>
This patch adds the bindings for the MSM DisplayPort HDCP registers which are required to write the HDCP key into the display controller as well as the registers to enable HDCP authentication/key exchange/encryption.
Changes in v2:
-Drop register range names (Stephen)
-Fix yaml errors (Rob)
--- .../devicetree/bindings/display/msm/dp-controller.yaml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
Documentation/devicetree/bindings/display/msm/dp-controller.yaml +4 -3
@@ -19,7 +19,7 @@ properties: - qcom,sc7180-dp reg: - maxItems: 1 + maxItems: 3 interrupts: maxItems: 1
@@ -99,8 +99,9 @@ examples: #include <dt-bindings/power/qcom-rpmpd.h> displayport-controller@ae90000 { - compatible = "qcom,sc7180-dp"; - reg = <0xae90000 0x1400>; + reg = <0 0x0ae90000 0 0x1400>, + <0 0x0aed1000 0 0x174>, + <0 0x0aee1000 0 0x2c>; interrupt-parent = <&mdss>; interrupts = <12>; clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>,
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Rob Herring
maintainerRe: [PATCH v2 12/13] dt-bindings: msm/dp: Add bindings for HDCP registers
Quoted 14 lines · Sean Paul
From: Sean Paul <[email protected]>
This patch adds the bindings for the MSM DisplayPort HDCP registers which are required to write the HDCP key into the display controller as well as the registers to enable HDCP authentication/key exchange/encryption.
Cc Rob Herring <[email protected]>Cc Stephen Boyd <[email protected]>Signed-off-by Sean Paul <[email protected]>Changes in v2:
Review
Quoted 5 lines
(quoted diff) +0
-3-Drop register range names (Stephen) -Fix yaml errors (Rob) --- .../devicetree/bindings/display/msm/dp-controller.yaml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)
My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' on your patch (DT_CHECKER_FLAGS is new in v5.13):
yamllint warnings/errors:
dtschema/dtc warnings/errors:
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/display/msm/dp-controller.example.dt.yaml: example-0: displayport-controller@ae90000:reg:0: [0, 183042048, 0, 5120] is too long
From schema: /usr/local/lib/python3.8/dist-packages/dtschema/schemas/reg.yaml
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/display/msm/dp-controller.example.dt.yaml: example-0: displayport-controller@ae90000:reg:1: [0, 183308288, 0, 372] is too long
From schema: /usr/local/lib/python3.8/dist-packages/dtschema/schemas/reg.yaml
/builds/robherring/linux-dt-review/Documentation/devicetree/bindings/display/msm/dp-controller.example.dt.yaml: example-0: displayport-controller@ae90000:reg:2: [0, 183373824, 0, 44] is too long
From schema: /usr/local/lib/python3.8/dist-packages/dtschema/schemas/reg.yaml
doc reference errors (make refcheckdocs):
See https://patchwork.ozlabs.org/patch/1528559
This check can fail if there are any dependencies. The base for a patch series is generally the most recent rc1.
If you already ran 'make dt_binding_check' and didn't see the above error(s), then make sure 'yamllint' is installed and dt-schema is up to date:
pip3 install dtschema --upgrade
Please check and re-submit.
Rob Herring
maintainerRe: [PATCH v2 12/13] dt-bindings: msm/dp: Add bindings for HDCP registers
In reply to Sean PaulQuoted 24 lines · Sean Paul
From: Sean Paul <[email protected]>
This patch adds the bindings for the MSM DisplayPort HDCP registers which are required to write the HDCP key into the display controller as well as the registers to enable HDCP authentication/key exchange/encryption.
Cc Rob Herring <[email protected]>Cc Stephen Boyd <[email protected]>Signed-off-by Sean Paul <[email protected]>Changes in v2:
(quoted diff) +0
-3-Drop register range names (Stephen) -Fix yaml errors (Rob) --- .../devicetree/bindings/display/msm/dp-controller.yaml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-)Documentation/devicetree/bindings/display/msm/dp-controller.yaml +0
-0
Documentation/devicetree/bindings/display/msm/dp-controller.yaml properties: · line 22
Quoted 5 lines
Documentation/devicetree/bindings/display/msm/dp-controller.yaml +1
-1@@ -19,7 +19,7 @@ properties: - qcom,sc7180-dp reg: - maxItems: 1 + maxItems: 3
You need to define what each entry is.
items:
- description: ...
- description: ...
- description: ...
Quoted 19 lines
Documentation/devicetree/bindings/display/msm/dp-controller.yaml +3
-2interrupts: maxItems: 1@@ -99,8 +99,9 @@ examples: #include <dt-bindings/power/qcom-rpmpd.h> displayport-controller@ae90000 { - compatible = "qcom,sc7180-dp"; - reg = <0xae90000 0x1400>; + reg = <0 0x0ae90000 0 0x1400>, + <0 0x0aed1000 0 0x174>, + <0 0x0aee1000 0 0x2c>; interrupt-parent = <&mdss>; interrupts = <12>; clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>,Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Sean Paul
reviewerPATCH v2 13/13 drm/msm: Implement HDCP 1.x using the new drm HDCP helpers
In reply to Sean PaulFrom: Sean Paul <[email protected]>
This patch adds HDCP 1.x support to msm DP connectors using the new HDCP helpers.
Changes in v2:
-Squash [1] into this patch with the following changes (Stephen)
-Update the sc7180 dtsi file
-Remove resource names and just use index (Stephen)
[1] https://patchwork.freedesktop.org/patch/msgid/[email protected]
--- arch/arm64/boot/dts/qcom/sc7180.dtsi | 4 +- drivers/gpu/drm/msm/Makefile | 1 + drivers/gpu/drm/msm/dp/dp_debug.c | 49 ++- drivers/gpu/drm/msm/dp/dp_debug.h | 6 +- drivers/gpu/drm/msm/dp/dp_display.c | 45 ++- drivers/gpu/drm/msm/dp/dp_display.h | 5 + drivers/gpu/drm/msm/dp/dp_drm.c | 68 ++++- drivers/gpu/drm/msm/dp/dp_drm.h | 5 + drivers/gpu/drm/msm/dp/dp_hdcp.c | 433 +++++++++++++++++++++++++++ drivers/gpu/drm/msm/dp/dp_hdcp.h | 27 ++ drivers/gpu/drm/msm/dp/dp_parser.c | 22 +- drivers/gpu/drm/msm/dp/dp_parser.h | 4 + drivers/gpu/drm/msm/dp/dp_reg.h | 44 ++- drivers/gpu/drm/msm/msm_atomic.c | 15 + 14 files changed, 709 insertions(+), 19 deletions(-) create mode 100644 drivers/gpu/drm/msm/dp/dp_hdcp.c create mode 100644 drivers/gpu/drm/msm/dp/dp_hdcp.h
arch/arm64/boot/dts/qcom/sc7180.dtsi +3 -1
@@ -3088,7 +3088,9 @@ mdss_dp: displayport-controller@ae90000 { compatible = "qcom,sc7180-dp"; status = "disabled"; - reg = <0 0x0ae90000 0 0x1400>; + reg = <0 0x0ae90000 0 0x1400>, + <0 0x0aed1000 0 0x174>, + <0 0x0aee1000 0 0x2c>; interrupt-parent = <&mdss>; interrupts = <12>;
drivers/gpu/drm/msm/Makefile +1 -0
@@ -109,6 +109,7 @@ msm-$(CONFIG_DRM_MSM_DP)+= dp/dp_aux.o \ dp/dp_ctrl.o \ dp/dp_display.o \ dp/dp_drm.o \ + dp/dp_hdcp.o \ dp/dp_hpd.o \ dp/dp_link.o \ dp/dp_panel.o \
drivers/gpu/drm/msm/dp/dp_debug.c +48 -1
97 lines not on this page · raw message
drivers/gpu/drm/msm/dp/dp_debug.h +4 -2
@@ -6,6 +6,7 @@#ifndef _DP_DEBUG_H_#define _DP_DEBUG_H_ +#include "dp_hdcp.h" #include "dp_panel.h" #include "dp_link.h"
@@ -43,7 +44,7 @@ struct dp_debug {*/ struct dp_debug *dp_debug_get (struct device *dev,struct dp_panel *panel,struct dp_usbpd *usbpd,struct dp_link *link, -struct drm_connector **connector, +struct dp_hdcp *hdcp,struct drm_connector **connector,struct drm_minor *minor);/**
@@ -60,7 +61,8 @@ void dp_debug_put(struct dp_debug *dp_debug);static inline struct dp_debug *dp_debug_get (struct device *dev,struct dp_panel *panel,struct dp_usbpd *usbpd,struct dp_link *link, -struct drm_connector **connector,struct drm_minor *minor) +struct dp_hdcp *hdcp,struct drm_connector **connector, +struct drm_minor *minor) {return ERR_PTR (-EINVAL ); }
drivers/gpu/drm/msm/dp/dp_display.c +43 -2
107 lines not on this page · raw message
drivers/gpu/drm/msm/dp/dp_display.h +5 -0
@@ -27,8 +27,13 @@ struct msm_dp {struct dp_audio *dp_audio; }; +struct drm_atomic_state ; +int dp_display_set_plugged_cb (struct msm_dp *dp_display,hdmi_codec_plugged_cb fn,struct device *codec_dev); +struct dp_hdcp *dp_display_connector_to_hdcp (struct drm_connector *connector); +void dp_display_hdcp_commit (struct msm_dp *dp_display, +struct drm_atomic_state *state);int dp_display_validate_mode (struct msm_dp *dp_display,u32 mode_pclk_khz);int dp_display_get_modes (struct msm_dp *dp_display,struct dp_display_mode *dp_mode);
drivers/gpu/drm/msm/dp/dp_drm.c +67 -1
104 lines not on this page · raw message
drivers/gpu/drm/msm/dp/dp_drm.h +5 -0
@@ -14,5 +14,10 @@#include "dp_display.h" struct drm_connector *dp_drm_connector_init (struct msm_dp *dp_display); +struct msm_dp *msm_dp_from_connector (struct drm_connector *connector); +bool dp_drm_is_connector_msm_dp (struct drm_connector *connector); +void dp_drm_atomic_commit (struct drm_connector *connector, +struct drm_connector_state *conn_state, +struct drm_atomic_state *state);#endif /* _DP_DRM_H_ */
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +433 -0
433 lines not on this page · raw message
drivers/gpu/drm/msm/dp/dp_hdcp.h new file +27 -0
@@ -0,0 +1,27 @@ +// SPDX-License-Identifier: MIT +/* +* Copyright (C) 2021 Google, Inc. +* +* Authors: +* Sean Paul <[email protected]> +*/ + +#ifndef DP_HDCP_H_ +#define DP_HDCP_H_ + +#define DP_HDCP_KEY_LEN 7 +#define DP_HDCP_NUM_KEYS 40 + +struct dp_hdcp ; +struct dp_parser ; +struct drm_atomic_state ; +struct drm_dp_aux ; + +struct dp_hdcp *dp_hdcp_get (struct dp_parser *parser,struct drm_dp_aux *aux); +void dp_hdcp_put (struct dp_hdcp *hdcp); + +int dp_hdcp_attach (struct dp_hdcp *hdcp,struct drm_connector *connector); +int dp_hdcp_ingest_key (struct dp_hdcp *hdcp,const u8 *raw_key,int raw_len); +void dp_hdcp_commit (struct dp_hdcp *hdcp,struct drm_atomic_state *state); + +#endif
drivers/gpu/drm/msm/dp/dp_parser.c +17 -5
@@ -20,11 +20,11 @@ static const struct dp_regulator_cfg sdm845_dp_reg_cfg = { };static int msm_dss_ioremap (struct platform_device *pdev, -struct dss_io_data *io_data) +struct dss_io_data *io_data,int idx) {struct resource *res =NULL ; - res =platform_get_resource (pdev,IORESOURCE_MEM ,0 ); + res =platform_get_resource (pdev,IORESOURCE_MEM , idx);if (!res) {DRM_ERROR ("%pS->%s: msm_dss_get_res failed\n" ,__builtin_return_address (0 ), __func__);
@@ -55,6 +55,8 @@ static void dp_parser_unmap_io_resources(struct dp_parser *parser) {struct dp_io *io = &parser->io; +msm_dss_iounmap (&io->hdcp_tz); +msm_dss_iounmap (&io->hdcp_key);msm_dss_iounmap (&io->dp_controller); }
@@ -64,10 +66,20 @@ static int dp_parser_ctrl_res(struct dp_parser *parser)struct platform_device *pdev = parser->pdev;struct dp_io *io = &parser->io; - rc =msm_dss_ioremap (pdev, &io->dp_controller); -if (rc) { -DRM_ERROR ("unable to remap dp io resources, rc=%d\n" , rc); + rc =msm_dss_ioremap (pdev, &io->dp_controller,0 ); +if (rc) goto err; + + rc =msm_dss_ioremap (pdev, &io->hdcp_key,1 ); +if (rc) { + io->hdcp_key.base =NULL ; + io->hdcp_key.len =0 ; + } + + rc =msm_dss_ioremap (pdev, &io->hdcp_tz,2 ); +if (rc) { + io->hdcp_tz.base =NULL ; + io->hdcp_tz.len =0 ; } io->phy =devm_phy_get (&pdev->dev,"dp" );
drivers/gpu/drm/msm/dp/dp_parser.h +4 -0
@@ -62,10 +62,14 @@ struct dp_display_data {* struct dp_ctrl_resource - controller's IO related data * * @dp_controller: Display Port controller mapped memory address +* @hdcp_key: mapped memory for HDCP key ingestion +* @hdcp_tz: mapped memory for HDCP TZ interaction * @phy_io: phy's mapped memory address */ struct dp_io {struct dss_io_data dp_controller; +struct dss_io_data hdcp_key; +struct dss_io_data hdcp_tz;struct phy *phy;union phy_configure_opts phy_opts; };
drivers/gpu/drm/msm/dp/dp_reg.h +37 -7
67 lines not on this page · raw message
drivers/gpu/drm/msm/msm_atomic.c +15 -0
@@ -8,6 +8,7 @@#include <drm/drm_gem_atomic_helper.h> #include <drm/drm_vblank.h> +#include "dp_drm.h" #include "msm_atomic_trace.h" #include "msm_drv.h" #include "msm_gem.h"
@@ -203,6 +204,18 @@ static unsigned get_crtc_mask(struct drm_atomic_state *state)return mask; } +static void msm_atomic_commit_connectors (struct drm_atomic_state *state) +{ +struct drm_connector_state *conn_state; +struct drm_connector *connector; +int i; + +for_each_new_connector_in_state (state, connector, conn_state, i) { +if (dp_drm_is_connector_msm_dp (connector)) +dp_drm_atomic_commit (connector, conn_state, state); + } +} +void msm_atomic_commit_tail (struct drm_atomic_state *state) {struct drm_device *dev = state->dev;
@@ -239,6 +252,8 @@ void msm_atomic_commit_tail(struct drm_atomic_state *state)drm_atomic_helper_commit_planes (dev, state,0 );drm_atomic_helper_commit_modeset_enables (dev, state); +msm_atomic_commit_connectors (state); +if (async) {struct msm_pending_timer *timer = &kms->pending_timers[drm_crtc_index (async_crtc)];
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
kernel test robot
build botRe: [PATCH v2 13/13] drm/msm: Implement HDCP 1.x using the new drm HDCP helpers
I love your patch! Yet something to improve:
Hi Sean,
I love your patch! Yet something to improve:
[auto build test ERROR on drm-intel/for-linux-next]
[also build test ERROR on drm-tip/drm-tip next-20210916] [cannot apply to robh/for-next linus/master v5.15-rc1]
[If your patch is applied to the wrong git tree, kindly drop us a note. And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Sean-Paul/drm-hdcp-Pull-HDCP-auth-exchange-check-into-helpers/20210916-044145 base: git://anongit.freedesktop.org/drm-intel for-linux-next config: arm-allyesconfig (attached as .config) compiler: arm-linux-gnueabi-gcc (GCC) 11.2.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/2fc7bb157fc24840f3fe3b8ece82cea21ded8db6
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Sean-Paul/drm-hdcp-Pull-HDCP-auth-exchange-check-into-helpers/20210916-044145 git checkout 2fc7bb157fc24840f3fe3b8ece82cea21ded8db6
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-11.2.0 make.cross ARCH=arm
If you fix the issue, kindly add following tag as appropriate
All errors (new ones prefixed by >>):
drivers/gpu/drm/msm/dp/dp_debug.c: In function 'dp_hdcp_key_write':
>> drivers/gpu/drm/msm/dp/dp_debug.c:361:28: error: variable 'dev' set but not used [-Werror=unused-but-set-variable]
361 | struct drm_device *dev;
| ^~~cc1: all warnings being treated as errors
vim +/dev +361 drivers/gpu/drm/msm/dp/dp_debug.c
354
355 static ssize_t dp_hdcp_key_write(struct file *file, const char __user *ubuf,
356 size_t len, loff_t *offp)
357 {
358 char *input_buffer;
359 int ret = 0;
360 struct dp_debug_private *debug = file->private_data;
> 361 struct drm_device *dev;
362
363 dev = debug->drm_dev;
364
365 if (len != (DRM_HDCP_KSV_LEN + DP_HDCP_NUM_KEYS * DP_HDCP_KEY_LEN))
366 return -EINVAL;
367
368 if (!debug->hdcp)
369 return -ENOENT;
370
371 input_buffer = memdup_user_nul(ubuf, len);
372 if (IS_ERR(input_buffer))
373 return PTR_ERR(input_buffer);
374
375 ret = dp_hdcp_ingest_key(debug->hdcp, input_buffer, len);
376
377 kfree(input_buffer);
378 if (ret < 0) {
379 DRM_ERROR("Could not ingest HDCP key, ret=%d\n", ret);
380 return ret;
381 }
382
383 *offp += len;
384 return len;
385 }
386
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/[email protected]
Re: [PATCH v2 13/13] drm/msm: Implement HDCP 1.x using the new drm HDCP helpers
In reply to Sean PaulQuoting Sean Paul (2021-09-15 13:38:32)
arch/arm64/boot/dts/qcom/sc7180.dtsi mdss_dp: displayport-controller@ae90000 { · line 3094
Quoted 13 lines
arch/arm64/boot/dts/qcom/sc7180.dtsi +3
-1@@ -3088,7 +3088,9 @@ mdss_dp: displayport-controller@ae90000 { compatible = "qcom,sc7180-dp"; status = "disabled"; - reg = <0 0x0ae90000 0 0x1400>; + reg = <0 0x0ae90000 0 0x1400>, + <0 0x0aed1000 0 0x174>, + <0 0x0aee1000 0 0x2c>;
I suspect we'll still want this hunk of the patch to be split off and go through arm-soc tree.
Quoted 31 lines
arch/arm64/boot/dts/qcom/sc7180.dtsi +0
-0interrupt-parent = <&mdss>; interrupts = <12>;drivers/gpu/drm/msm/dp/dp_debug.c +3
-0@@ -8,6 +8,7 @@#include <linux/debugfs.h> #include <drm/drm_connector.h> #include <drm/drm_file.h> +#include <drm/drm_hdcp.h> #include "dp_parser.h" #include "dp_catalog.h" @@ -15,6 +16,7 @@#include "dp_ctrl.h" #include "dp_debug.h" #include "dp_display.h" +#include "dp_hdcp.h" #define DEBUG_NAME "msm_dp"@@ -24,6 +26,7 @@ struct dp_debug_private {struct dp_usbpd *usbpd;struct dp_link *link;struct dp_panel *panel; +struct dp_hdcp *hdcp;struct drm_connector **connector;struct device *dev;struct drm_device *drm_dev;
drivers/gpu/drm/msm/dp/dp_debug.c static int dp_test_active_open(struct inode *inode, · line 355
Quoted 4 lines
drivers/gpu/drm/msm/dp/dp_debug.c +1
-0@@ -349,6 +352,38 @@ static int dp_test_active_open(struct inode *inode, inode->i_private); } +static ssize_t dp_hdcp_key_write(struct file *file, const char __user *ubuf,
Is this the API that userspace is going to use to set the key? Or a simple debug interface that's used to test this code out? I hope it's a debugging aid and not the normal flow given that it's through debugfs.
drivers/gpu/drm/msm/dp/dp_debug.c static int dp_test_active_open(struct inode *inode, · line 359
Quoted 4 lines
drivers/gpu/drm/msm/dp/dp_debug.c +4
-0+ size_t len, loff_t *offp) +{ + char *input_buffer; +int ret =0 ;
Please don't assign variables and then overwrite without testing the variable.
Quoted 276 lines
drivers/gpu/drm/msm/dp/dp_debug.c +40
-1+struct dp_debug_private *debug = file->private_data; +struct drm_device *dev; + + dev = debug->drm_dev; + +if (len != (DRM_HDCP_KSV_LEN +DP_HDCP_NUM_KEYS *DP_HDCP_KEY_LEN )) +return -EINVAL ; + +if (!debug->hdcp) +return -ENOENT ; + + input_buffer =memdup_user_nul (ubuf, len); +if (IS_ERR (input_buffer)) +return PTR_ERR (input_buffer); + + ret =dp_hdcp_ingest_key (debug->hdcp, input_buffer, len); + +kfree (input_buffer); +if (ret <0 ) { +DRM_ERROR ("Could not ingest HDCP key, ret=%d\n" , ret); +return ret; + } + + *offp += len; +return len; +} +static const struct file_operations dp_debug_fops = { .open = simple_open, .read = dp_debug_read_info,@@ -363,6 +398,12 @@ static const struct file_operations test_active_fops = { .write = dp_test_active_write }; +static const struct file_operations dp_hdcp_key_fops = { + .owner =THIS_MODULE , + .open = simple_open, + .write = dp_hdcp_key_write, +}; +static int dp_debug_init (struct dp_debug *dp_debug,struct drm_minor *minor) {int rc =0 ;@@ -384,6 +425,10 @@ static int dp_debug_init(struct dp_debug *dp_debug, struct drm_minor *minor) minor->debugfs_root, debug, &dp_test_type_fops); +debugfs_create_file ("msm_dp_hdcp_key" ,0222 , + minor->debugfs_root, + debug, &dp_hdcp_key_fops); + debug->root = minor->debugfs_root;return rc;@@ -391,7 +436,8 @@ static int dp_debug_init(struct dp_debug *dp_debug, struct drm_minor *minor)struct dp_debug *dp_debug_get (struct device *dev,struct dp_panel *panel,struct dp_usbpd *usbpd,struct dp_link *link, -struct drm_connector **connector,struct drm_minor *minor) +struct dp_hdcp *hdcp,struct drm_connector **connector, +struct drm_minor *minor) {int rc =0 ;struct dp_debug_private *debug;@@ -413,6 +459,7 @@ struct dp_debug *dp_debug_get(struct device *dev, struct dp_panel *panel, debug->usbpd = usbpd; debug->link = link; debug->panel = panel; + debug->hdcp = hdcp; debug->dev = dev; debug->drm_dev = minor->dev; debug->connector = connector;drivers/gpu/drm/msm/dp/dp_display.h +5
-0@@ -27,8 +27,13 @@ struct msm_dp {struct dp_audio *dp_audio; }; +struct drm_atomic_state ; +int dp_display_set_plugged_cb (struct msm_dp *dp_display,hdmi_codec_plugged_cb fn,struct device *codec_dev); +struct dp_hdcp *dp_display_connector_to_hdcp (struct drm_connector *connector); +void dp_display_hdcp_commit (struct msm_dp *dp_display, +struct drm_atomic_state *state);int dp_display_validate_mode (struct msm_dp *dp_display,u32 mode_pclk_khz);int dp_display_get_modes (struct msm_dp *dp_display,struct dp_display_mode *dp_mode);drivers/gpu/drm/msm/dp/dp_drm.c +67
-1@@ -5,11 +5,20 @@#include <drm/drm_atomic_helper.h> #include <drm/drm_atomic.h> +#include <drm/drm_connector.h> #include <drm/drm_crtc.h> +#include <drm/drm_hdcp.h> #include "msm_drv.h" #include "msm_kms.h" #include "dp_drm.h" +#include "dp_hdcp.h" + +struct dp_connector_state { +struct drm_connector_state base; +bool hdcp_transition; +}; +#define to_dp_connector_state (x) container_of(x, struct dp_connector_state, base)struct dp_connector {struct drm_connector base;@@ -17,6 +26,11 @@ struct dp_connector { };#define to_dp_connector (x) container_of(x, struct dp_connector, base) +struct msm_dp *msm_dp_from_connector (struct drm_connector *connector) +{ +return to_dp_connector (connector)->dp_display; +} +/** * dp_connector_detect - callback to determine if connector is connected * @conn: Pointer to drm connector structure @@ -114,20 +128,72 @@ static enum drm_mode_status dp_connector_mode_valid(return dp_display_validate_mode (dp_disp, mode->clock); } +static int dp_connector_atomic_check (struct drm_connector *connector, +struct drm_atomic_state *state) +{ +struct drm_connector_state *conn_state; +struct dp_connector_state *dp_state; + + conn_state =drm_atomic_get_new_connector_state (state, connector); + dp_state =to_dp_connector_state (conn_state); + + dp_state->hdcp_transition =drm_hdcp_atomic_check (connector, state); + +return 0 ; +} + +static struct drm_connector_state * +dp_connector_atomic_duplicate_state (struct drm_connector *connector) +{ +struct dp_connector_state *state; + + state =kzalloc (sizeof (*state),GFP_KERNEL ); +if (!state) +return NULL ; + + state->hdcp_transition = false; + +__drm_atomic_helper_connector_duplicate_state (connector, &state->base); +return &state->base; +} +static const struct drm_connector_funcs dp_connector_funcs = { .detect = dp_connector_detect, .fill_modes = drm_helper_probe_single_connector_modes, .destroy = drm_connector_cleanup, .reset = drm_atomic_helper_connector_reset, - .atomic_duplicate_state = drm_atomic_helper_connector_duplicate_state, + .atomic_duplicate_state = dp_connector_atomic_duplicate_state, .atomic_destroy_state = drm_atomic_helper_connector_destroy_state, };static const struct drm_connector_helper_funcs dp_connector_helper_funcs = { .get_modes = dp_connector_get_modes, .mode_valid = dp_connector_mode_valid, + .atomic_check = dp_connector_atomic_check, }; +bool dp_drm_is_connector_msm_dp (struct drm_connector *connector) +{ +return connector->funcs == &dp_connector_funcs; +} + +void dp_drm_atomic_commit (struct drm_connector *connector, +struct drm_connector_state *conn_state, +struct drm_atomic_state *state) +{ +struct dp_connector_state *dp_state; +struct msm_dp *dp_disp; + + dp_state =to_dp_connector_state (conn_state); + +if (!dp_state->hdcp_transition) +return ; + + dp_disp =msm_dp_from_connector (connector); + +dp_display_hdcp_commit (dp_disp, state); +} +/* connector initialization */ struct drm_connector *dp_drm_connector_init (struct msm_dp *dp_display) {drivers/gpu/drm/msm/dp/dp_drm.h +5
-0@@ -14,5 +14,10 @@#include "dp_display.h" struct drm_connector *dp_drm_connector_init (struct msm_dp *dp_display); +struct msm_dp *msm_dp_from_connector (struct drm_connector *connector); +bool dp_drm_is_connector_msm_dp (struct drm_connector *connector); +void dp_drm_atomic_commit (struct drm_connector *connector, +struct drm_connector_state *conn_state, +struct drm_atomic_state *state);#endif /* _DP_DRM_H_ */ drivers/gpu/drm/msm/dp/dp_hdcp.c new file +54
-0@@ -0,0 +1,433 @@ +// SPDX-License-Identifier: MIT +/* +* Copyright (C) 2021 Google, Inc. +* +* Authors: +* Sean Paul <[email protected]> +*/ + +#include "dp_display.h" +#include "dp_drm.h" +#include "dp_hdcp.h" +#include "dp_reg.h" + +#include <drm/drm_connector.h> +#include <drm/drm_device.h> +#include <drm/drm_dp_helper.h> +#include <drm/drm_hdcp.h> +#include <drm/drm_print.h> + +#include <linux/bitfield.h> +#include <linux/bits.h> +#include <linux/iopoll.h> +#include <linux/mutex.h> +#include <linux/random.h> +#include <linux/slab.h> + +/* Offsets based on hdcp_ksv mmio */ +#define DP_HDCP_KSV_AN_LSB 0x0 +#define DP_HDCP_KSV_AN_MSB 0x4 +#define DP_HDCP_KSV_AKSV_MSB 0x1D8 +#define DP_HDCP_KSV_AKSV_LSB 0x1DC + +/* Key offsets based on hdcp_key mmio */ +#define DP_HDCP_KEY_BASE 0x30 +#define DP_HDCP_KEY_MSB (x) (DP_HDCP_KEY_BASE + (x * 8)) +#define DP_HDCP_KEY_LSB (x) (DP_HDCP_KEY_MSB(x) + 4) +#define DP_HDCP_KEY_VALID 0x170 +#define DP_HDCP_SW_KEY_VALID BIT(0) + +/* +* dp_hdcp_key - structure which contains an HDCP key set +* @ksv: The key selection vector +* @keys: Contains 40 keys +*/ +struct dp_hdcp_key { +struct drm_hdcp_ksv ksv; +union { +u32 words[2 ]; +u8 bytes[DP_HDCP_KEY_LEN ]; + } keys[DP_HDCP_NUM_KEYS ]; +bool valid; +}; + +struct dp_hdcp {
drivers/gpu/drm/msm/dp/dp_hdcp.c line 64
Quoted 10 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +10
-0+struct drm_device *dev; +struct drm_connector *connector; + +struct drm_dp_aux *aux; +struct dp_parser *parser; + +struct drm_hdcp_helper_data *helper_data; + +struct mutex key_lock; +struct dp_hdcp_key *key;
Is there a reason this is a pointer vs. a plain struct member?
Quoted 26 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +26
-0+}; + +static inline void dp_hdcp_write_dp (struct dp_hdcp *hdcp,u32 offset,u32 val) +{ +writel (val, hdcp->parser->io.dp_controller.base + offset); +} + +static inline u32 dp_hdcp_read_dp (struct dp_hdcp *hdcp,u32 offset) +{ +return readl (hdcp->parser->io.dp_controller.base + offset); +} + +static inline void dp_hdcp_write_hdcp (struct dp_hdcp *hdcp,u32 offset,u32 val) +{ +writel (val, hdcp->parser->io.hdcp_key.base + offset); +} + +static inline u32 dp_hdcp_read_hdcp (struct dp_hdcp *hdcp,u32 offset) +{ +return readl (hdcp->parser->io.hdcp_key.base + offset); +} + +static inline void dp_hdcp_write_tz (struct dp_hdcp *hdcp,u32 offset,u32 val) +{ +writel (val, hdcp->parser->io.hdcp_tz.base + offset); +}
drivers/gpu/drm/msm/dp/dp_hdcp.c line 100
Quoted 10 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +10
-0+ +static inline u32 dp_hdcp_read_tz (struct dp_hdcp *hdcp,u32 offset) +{ +return readl (hdcp->parser->io.hdcp_tz.base + offset); +} + +int dp_hdcp_ingest_key (struct dp_hdcp *hdcp,const u8 *raw_key,int raw_len) +{ +struct dp_hdcp_key *key; +const u8 *ptr = raw_key;
Why have the local variable when raw_key will do?
drivers/gpu/drm/msm/dp/dp_hdcp.c line 104
Quoted 4 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +4
-0+unsigned int ksv_weight; +int i, ret =0 ; + +mutex_lock (&hdcp->key_lock);
This can move after the length check?
Quoted 60 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +60
-0+ +if (raw_len != (DRM_HDCP_KSV_LEN +DP_HDCP_NUM_KEYS *DP_HDCP_KEY_LEN )) { +DRM_ERROR ("Invalid HDCP key length expected=%d actual=%d\n" , + (DRM_HDCP_KSV_LEN +DP_HDCP_NUM_KEYS *DP_HDCP_KEY_LEN ), + raw_len); + ret = -EINVAL ; + goto out; + } + + key = hdcp->key; + +memcpy (key->ksv.bytes, ptr,DRM_HDCP_KSV_LEN ); + ksv_weight =hweight32 (key->ksv.words[0 ]) +hweight32 (key->ksv.words[1 ]); +if (ksv_weight !=20 ) { +DRM_ERROR ("Invalid ksv weight, expected=20 actual=%d\n" , + ksv_weight); + ret = -EINVAL ; + goto out; + } + + ptr +=DRM_HDCP_KSV_LEN ; +for (i =0 ; i <DP_HDCP_NUM_KEYS ; i++) { +memcpy (key->keys[i].bytes, ptr,DP_HDCP_KEY_LEN ); + ptr +=DP_HDCP_KEY_LEN ; + } + +DRM_DEBUG_DRIVER ("Successfully ingested HDCP key\n" ); + hdcp->key->valid = true; + +out: +mutex_unlock (&hdcp->key_lock); +return ret; +} + +static bool dp_hdcp_are_keys_valid (struct drm_connector *connector) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +u32 val; + + val =dp_hdcp_read_dp (hdcp,DP_HDCP_STATUS ); +return FIELD_GET (DP_HDCP_KEY_STATUS , val) ==DP_HDCP_KEY_STATUS_VALID ; +} + +static int dp_hdcp_load_keys (struct drm_connector *connector) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +struct dp_hdcp_key *key; +int i, ret =0 ; + +mutex_lock (&hdcp->key_lock); + + key = hdcp->key; + +if (!key->valid) { + ret = -ENOENT ; + goto out; + } + +dp_hdcp_write_dp (hdcp,DP_HDCP_SW_LOWER_AKSV , key->ksv.words[0 ]); +dp_hdcp_write_dp (hdcp,DP_HDCP_SW_UPPER_AKSV , key->ksv.words[1 ]);
drivers/gpu/drm/msm/dp/dp_hdcp.c line 174
Quoted 10 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +10
-0+ +for (i =0 ; i <DP_HDCP_NUM_KEYS ; i++) { +dp_hdcp_write_hdcp (hdcp,DP_HDCP_KEY_LSB (i), + key->keys[i].words[0 ]); +dp_hdcp_write_hdcp (hdcp,DP_HDCP_KEY_MSB (i), + key->keys[i].words[1 ]); + } + +dp_hdcp_write_hdcp (hdcp,DP_HDCP_KEY_VALID ,DP_HDCP_SW_KEY_VALID ); +wmb ();
What are the wmb()s for? Can you add a comment indicating what we're trying to fix by having them?
drivers/gpu/drm/msm/dp/dp_hdcp.c line 177
Quoted 3 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +3
-0+ +dp_hdcp_write_dp (hdcp,DP_HDCP_ENTROPY_CTRL0 ,get_random_u32 ()); +dp_hdcp_write_dp (hdcp,DP_HDCP_ENTROPY_CTRL1 ,get_random_u32 ());
Can we call get_random_u64() at the start of this function outside the mutex lock and then use the upper and lower halves for these two lines above?
Quoted 37 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +37
-0+wmb (); + +out: +mutex_unlock (&hdcp->key_lock); +return ret; +} + +static int dp_hdcp_hdcp2_capable (struct drm_connector *connector,bool *capable) +{ + *capable = false; +return 0 ; +} + +static int dp_hdcp_hdcp1_read_an_aksv (struct drm_connector *connector, +u32 *an,u32 *aksv) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +bool keys_valid; +int ret; +u32 val; + +dp_hdcp_write_dp (hdcp,DP_HDCP_CTRL ,1 ); + + ret =read_poll_timeout (dp_hdcp_are_keys_valid, keys_valid, keys_valid, +20 *1000 ,10 *1000 , false, connector); +if (ret) { +drm_err (hdcp->dev,"HDCP keys invalid %d\n" , ret); +return ret; + } + +/* Clear AInfo */ +dp_hdcp_write_dp (hdcp,DP_HDCP_RCVPORT_DATA4 ,0 ); + + aksv[0 ] =dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA3 ); + aksv[1 ] =GENMASK (7 ,0 ) &dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA4 ); + + ret = read_poll_timeout(dp_hdcp_read_dp, val,
drivers/gpu/drm/msm/dp/dp_hdcp.c line 224
Quoted 10 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +10
-0+ (val &DP_HDCP_AN_READY_MASK ) ==DP_HDCP_AN_READY_MASK , + 100, 10 * 1000, false, hdcp, DP_HDCP_STATUS); +if (ret) { +drm_err (hdcp->dev,"AN failed to become ready %x/%d\n" , val, ret); +return ret; + } + +/* +* Get An from hardware, for unknown reasons we need to read the reg +* twice to get valid data.
That's annoying.
Quoted 13 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +13
-0+*/ +dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA5 ); + an[0 ] =dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA5 ); + +dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA6 ); + an[1 ] =dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA6 ); + +return 0 ; +} + +static int dp_hdcp_hdcp1_store_receiver_info (struct drm_connector *connector, +u32 *ksv,u32 status,u8 bcaps, +bool is_repeater)
drivers/gpu/drm/msm/dp/dp_hdcp.c line 247
Quoted 10 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +10
-0+{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +u32 val; + +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA0 , + ksv[0 ]); +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA1 , + ksv[1 ]); + + val = ((status &GENMASK (15 ,0 )) <<8 ) | (bcaps &GENMASK (7 ,0 ));
Nitpick: Can this use FIELD_PREP() too?
Quoted 28 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +28
-0+ +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA12 , val); + +return 0 ; +} + +static int dp_hdcp_hdcp1_enable_encryption (struct drm_connector *connector) +{ +return 0 ; +} + +static int dp_hdcp_hdcp1_wait_for_r0 (struct drm_connector *connector) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +int ret; +u32 val; + + ret =read_poll_timeout (dp_hdcp_read_dp, val, (val &DP_HDCP_R0_READY ), +100 ,1000 , false, hdcp, +DP_HDCP_STATUS ); +if (ret) { +drm_err (hdcp->dev,"HDCP R0 not ready %x/%d\n" , val, ret); +return ret; + } + +return 0 ; +} +
drivers/gpu/drm/msm/dp/dp_hdcp.c line 285
Quoted 10 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +10
-0+static int dp_hdcp_hdcp1_match_ri (struct drm_connector *connector,u32 ri_prime) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +int ret; +u32 val; + +dp_hdcp_write_dp (hdcp,DP_HDCP_RCVPORT_DATA2_0 , ri_prime); + + ret = read_poll_timeout(dp_hdcp_read_dp, val, (val & DP_HDCP_RI_MATCH), + 20 * 1000, 100 * 1000, false, hdcp,
Maybe 20 * 1000 and 100 * 1000 should be some defines at the top of this file?
Quoted 5 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +5
-0+ DP_HDCP_STATUS); +if (ret) { +drm_err (hdcp->dev,"Failed to match Ri and Ri` (%08x) %08x/%d\n" , + ri_prime, val, ret); +return ret;
drivers/gpu/drm/msm/dp/dp_hdcp.c line 300
Quoted 10 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +10
-0+ } +return 0 ; +} + +static int dp_hdcp_hdcp1_store_ksv_fifo (struct drm_connector *connector, +u8 *ksv_fifo,u8 num_downstream, +u8 *bstatus,u32 *vprime) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +int num_bytes = (num_downstream *DRM_HDCP_KSV_LEN );
Nitpick: Why the parenthesis?
Quoted 174 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +133
-0+int ret, i; +u32 val; + +/* Reset the SHA computation block */ +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_SHA_CTRL , +DP_HDCP_SHA_CTRL_RESET ); +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_SHA_CTRL ,0 ); + +/* +* KSV info gets written a byte at a time in the same order it was +* received. Every 64 bytes, we need to wait for the SHA_BLOCK_DONE +* bit to be set in SHA_CTRL. +*/ +for (i =0 ; i < num_bytes; i++) { + val =FIELD_PREP (DP_HDCP_SHA_DATA_MASK , ksv_fifo[i]); + +if (i == (num_bytes -1 )) + val |=DP_HDCP_SHA_DATA_DONE ; + +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_SHA_DATA , + val); + +if (((i +1 ) %64 ) !=0 ) +continue ; + + ret =read_poll_timeout (dp_hdcp_read_dp, val, + (val &DP_HDCP_SHA_DONE ),100 , +100 *1000 , false, hdcp, +DP_HDCP_SHA_STATUS ); +if (ret) { +drm_err (hdcp->dev,"SHA block incomplete %d\n" , ret); +return ret; + } + } + + ret =read_poll_timeout (dp_hdcp_read_dp, val, + (val &DP_HDCP_SHA_COMP_DONE ),100 ,100 *1000 , + false, hdcp,DP_HDCP_SHA_STATUS ); +if (ret) { +drm_err (hdcp->dev,"SHA computation incomplete %d\n" , ret); +return ret; + } + +return 0 ; +} + +static int dp_hdcp_hdcp1_disable (struct drm_connector *connector) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +u32 val; + + val =dp_hdcp_read_dp (hdcp,REG_DP_SW_RESET ); +dp_hdcp_write_dp (hdcp,REG_DP_SW_RESET , val |DP_HDCP_SW_RESET ); + +/* Disable encryption and disable the HDCP block */ +dp_hdcp_write_dp (hdcp,DP_HDCP_CTRL ,0 ); + +dp_hdcp_write_dp (hdcp,REG_DP_SW_RESET , val); + +return 0 ; +} + +void dp_hdcp_commit (struct dp_hdcp *hdcp,struct drm_atomic_state *state) +{ +drm_hdcp_helper_atomic_commit (hdcp->helper_data, state,NULL ); +} + +static const struct drm_hdcp_helper_funcs dp_hdcp_funcs = { + .are_keys_valid = dp_hdcp_are_keys_valid, + .load_keys = dp_hdcp_load_keys, + .hdcp2_capable = dp_hdcp_hdcp2_capable, + .hdcp1_read_an_aksv = dp_hdcp_hdcp1_read_an_aksv, + .hdcp1_store_receiver_info = dp_hdcp_hdcp1_store_receiver_info, + .hdcp1_enable_encryption = dp_hdcp_hdcp1_enable_encryption, + .hdcp1_wait_for_r0 = dp_hdcp_hdcp1_wait_for_r0, + .hdcp1_match_ri = dp_hdcp_hdcp1_match_ri, + .hdcp1_store_ksv_fifo = dp_hdcp_hdcp1_store_ksv_fifo, + .hdcp1_disable = dp_hdcp_hdcp1_disable, +}; + +int dp_hdcp_attach (struct dp_hdcp *hdcp,struct drm_connector *connector) +{ +struct drm_device *dev = connector->dev; +struct drm_hdcp_helper_data *helper_data; +int ret; + +/* HDCP is not configured for this device */ +if (!hdcp || !hdcp->parser || hdcp->parser->io.hdcp_key.len ==0 ) +return 0 ; + + helper_data =drm_hdcp_helper_initialize_dp (connector, hdcp->aux, + &dp_hdcp_funcs, false); +if (IS_ERR_OR_NULL (helper_data)) +return PTR_ERR (helper_data); + + ret =drm_connector_attach_content_protection_property (connector, false); +if (ret) { +drm_hdcp_helper_destroy (helper_data); +drm_err (dev,"Failed to attach content protection prop %d\n" , ret); +return ret; + } + + hdcp->dev = connector->dev; + hdcp->connector = connector; + hdcp->helper_data = helper_data; + +return 0 ; +} + +struct dp_hdcp *dp_hdcp_get (struct dp_parser *parser,struct drm_dp_aux *aux) +{ +struct dp_hdcp *hdcp; + + hdcp =devm_kzalloc (&parser->pdev->dev,sizeof (*hdcp),GFP_KERNEL ); +if (!hdcp) +return ERR_PTR (-ENOMEM ); + + hdcp->key =devm_kzalloc (&parser->pdev->dev,sizeof (*hdcp->key),GFP_KERNEL ); +if (!hdcp->key) +return ERR_PTR (-ENOMEM ); + + hdcp->parser = parser; + hdcp->aux = aux; + +mutex_init (&hdcp->key_lock); + +return hdcp; +} + +void dp_hdcp_put (struct dp_hdcp *hdcp) +{ +drm_hdcp_helper_destroy (hdcp->helper_data); +}drivers/gpu/drm/msm/dp/dp_hdcp.h new file +27
-0@@ -0,0 +1,27 @@ +// SPDX-License-Identifier: MIT +/* +* Copyright (C) 2021 Google, Inc. +* +* Authors: +* Sean Paul <[email protected]> +*/ + +#ifndef DP_HDCP_H_ +#define DP_HDCP_H_ + +#define DP_HDCP_KEY_LEN 7 +#define DP_HDCP_NUM_KEYS 40 + +struct dp_hdcp ; +struct dp_parser ; +struct drm_atomic_state ; +struct drm_dp_aux ; + +struct dp_hdcp *dp_hdcp_get (struct dp_parser *parser,struct drm_dp_aux *aux); +void dp_hdcp_put (struct dp_hdcp *hdcp); + +int dp_hdcp_attach (struct dp_hdcp *hdcp,struct drm_connector *connector); +int dp_hdcp_ingest_key (struct dp_hdcp *hdcp,const u8 *raw_key,int raw_len); +void dp_hdcp_commit (struct dp_hdcp *hdcp,struct drm_atomic_state *state); + +#endif drivers/gpu/drm/msm/dp/dp_parser.c +0
-0@@ -20,11 +20,11 @@ static const struct dp_regulator_cfg sdm845_dp_reg_cfg = { }; static int msm_dss_ioremap(struct platform_device *pdev,
drivers/gpu/drm/msm/dp/dp_parser.c static const struct dp_regulator_cfg sdm845_dp_reg_cfg = { · line 30
Quoted 10 lines
drivers/gpu/drm/msm/dp/dp_parser.c +2
-2- struct dss_io_data *io_data) + struct dss_io_data *io_data, int idx) {struct resource *res =NULL ; - res =platform_get_resource (pdev,IORESOURCE_MEM ,0 ); + res =platform_get_resource (pdev,IORESOURCE_MEM , idx);if (!res) {DRM_ERROR ("%pS->%s: msm_dss_get_res failed\n" ,__builtin_return_address (0 ), __func__);
We should remove this error message. It's confusing now that some resources are optional.
Quoted 20 lines
drivers/gpu/drm/msm/dp/dp_parser.c +5
-3@@ -55,6 +55,8 @@ static void dp_parser_unmap_io_resources(struct dp_parser *parser) {struct dp_io *io = &parser->io; +msm_dss_iounmap (&io->hdcp_tz); +msm_dss_iounmap (&io->hdcp_key);msm_dss_iounmap (&io->dp_controller); }@@ -64,10 +66,20 @@ static int dp_parser_ctrl_res(struct dp_parser *parser)struct platform_device *pdev = parser->pdev;struct dp_io *io = &parser->io; - rc =msm_dss_ioremap (pdev, &io->dp_controller); -if (rc) { -DRM_ERROR ("unable to remap dp io resources, rc=%d\n" , rc); + rc =msm_dss_ioremap (pdev, &io->dp_controller,0 ); +if (rc) goto err; +
drivers/gpu/drm/msm/dp/dp_parser.c static int dp_parser_ctrl_res(struct dp_parser *parser) · line 82
Quoted 10 lines
drivers/gpu/drm/msm/dp/dp_parser.c +10
-0+ rc =msm_dss_ioremap (pdev, &io->hdcp_key,1 ); +if (rc) { + io->hdcp_key.base =NULL ; + io->hdcp_key.len =0 ; + } + + rc =msm_dss_ioremap (pdev, &io->hdcp_tz,2 ); +if (rc) { + io->hdcp_tz.base =NULL ; + io->hdcp_tz.len =0 ;
Bjorn is trying to split the single io region apart into 4 different regions[1]. This would add two more io regions. Maybe this should come after those patches and be indexed later? I worry about needing to add more register properties later on though. Maybe a better approach would be to make them mandatory for certain compatible strings instead.
Quoted 3 lines
drivers/gpu/drm/msm/dp/dp_parser.c +0
-0} io->phy =devm_phy_get (&pdev->dev,"dp" );
Sean Paul
reviewerRe: [PATCH v2 13/13] drm/msm: Implement HDCP 1.x using the new drm HDCP helpers
Quoted 1 line · Stephen Boyd
Quoting Sean Paul (2021-09-15 13:38:32)
/snip
Quoted 32 lines
Quoted 32 lines
drivers/gpu/drm/msm/dp/dp_debug.c +3
-0@@ -8,6 +8,7 @@#include <linux/debugfs.h> #include <drm/drm_connector.h> #include <drm/drm_file.h> +#include <drm/drm_hdcp.h> #include "dp_parser.h" #include "dp_catalog.h" @@ -15,6 +16,7 @@#include "dp_ctrl.h" #include "dp_debug.h" #include "dp_display.h" +#include "dp_hdcp.h" #define DEBUG_NAME "msm_dp"@@ -24,6 +26,7 @@ struct dp_debug_private {struct dp_usbpd *usbpd;struct dp_link *link;struct dp_panel *panel; +struct dp_hdcp *hdcp;struct drm_connector **connector;struct device *dev;struct drm_device *drm_dev;@@ -349,6 +352,38 @@ static int dp_test_active_open(struct inode *inode, inode->i_private); }
Quoted 6 lines
drivers/gpu/drm/msm/dp/dp_debug.c static int dp_test_active_open(struct inode *inode, · line 355
Quoted 1 line
drivers/gpu/drm/msm/dp/dp_debug.c +1
-0+static ssize_t dp_hdcp_key_write(struct file *file, const char __user *ubuf,Is this the API that userspace is going to use to set the key? Or a simple debug interface that's used to test this code out? I hope it's a debugging aid and not the normal flow given that it's through debugfs.
At the moment, generic UAPI is not useful beyond msm-based CrOS devices, which is not really a burden upstream should be carrying. On other platforms (including qc-based Android devices), the key injection is done in HW. As such, I'm tempted to kick key injection UAPI down the road.
Once I finish the userspace client in CrOS, I can upload the UAPI for folks to comment on.
/snip
Quoted 27 lines
Quoted 27 lines
drivers/gpu/drm/msm/dp/dp_display.h +22
-0+static int dp_hdcp_load_keys (struct drm_connector *connector) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +struct dp_hdcp_key *key; +int i, ret =0 ; + +mutex_lock (&hdcp->key_lock); + + key = hdcp->key; + +if (!key->valid) { + ret = -ENOENT ; + goto out; + } + +dp_hdcp_write_dp (hdcp,DP_HDCP_SW_LOWER_AKSV , key->ksv.words[0 ]); +dp_hdcp_write_dp (hdcp,DP_HDCP_SW_UPPER_AKSV , key->ksv.words[1 ]); + +for (i =0 ; i <DP_HDCP_NUM_KEYS ; i++) { +dp_hdcp_write_hdcp (hdcp,DP_HDCP_KEY_LSB (i), + key->keys[i].words[0 ]); + dp_hdcp_write_hdcp(hdcp, DP_HDCP_KEY_MSB(i),
Quoted 9 lines
drivers/gpu/drm/msm/dp/dp_display.h
Quoted 5 lines
drivers/gpu/drm/msm/dp/dp_display.h +5
-0+ key->keys[i].words[1]); + } + +dp_hdcp_write_hdcp (hdcp,DP_HDCP_KEY_VALID ,DP_HDCP_SW_KEY_VALID ); +wmb ();What are the wmb()s for? Can you add a comment indicating what we're trying to fix by having them?
I think these were left over from testing (when things weren't working for me). Will remove in the next version, thanks for catching!
/snip
Quoted 4 lines
drivers/gpu/drm/msm/dp/dp_parser.c
Quoted 4 lines
drivers/gpu/drm/msm/dp/dp_parser.c +0
-0
/snip
Quoted 28 lines
Quoted 28 lines
drivers/gpu/drm/msm/dp/dp_parser.c +13
-3@@ -55,6 +55,8 @@ static void dp_parser_unmap_io_resources(struct dp_parser *parser) {struct dp_io *io = &parser->io; +msm_dss_iounmap (&io->hdcp_tz); +msm_dss_iounmap (&io->hdcp_key);msm_dss_iounmap (&io->dp_controller); }@@ -64,10 +66,20 @@ static int dp_parser_ctrl_res(struct dp_parser *parser)struct platform_device *pdev = parser->pdev;struct dp_io *io = &parser->io; - rc =msm_dss_ioremap (pdev, &io->dp_controller); -if (rc) { -DRM_ERROR ("unable to remap dp io resources, rc=%d\n" , rc); + rc =msm_dss_ioremap (pdev, &io->dp_controller,0 ); +if (rc) goto err; + + rc =msm_dss_ioremap (pdev, &io->hdcp_key,1 ); +if (rc) { + io->hdcp_key.base =NULL ; + io->hdcp_key.len =0 ; + } + + rc =msm_dss_ioremap (pdev, &io->hdcp_tz,2 ); +if (rc) {
Quoted 8 lines
drivers/gpu/drm/msm/dp/dp_parser.c static int dp_parser_ctrl_res(struct dp_parser *parser) · line 82
Quoted 2 lines
drivers/gpu/drm/msm/dp/dp_parser.c +2
-0+ io->hdcp_tz.base =NULL ; + io->hdcp_tz.len =0 ;Bjorn is trying to split the single io region apart into 4 different regions[1]. This would add two more io regions. Maybe this should come after those patches and be indexed later? I worry about needing to add more register properties later on though. Maybe a better approach would be to make them mandatory for certain compatible strings instead.
Thanks for the heads up, I'll look into adding a compatible string.
All your other comments will be addressed in v3.
Sean
Quoted 6 lines
[1] https://lore.kernel.org/r/[email protected]
Quoted 3 lines
drivers/gpu/drm/msm/dp/dp_parser.c +0
-0} io->phy =devm_phy_get (&pdev->dev,"dp" );
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Re: [Freedreno] [PATCH v2 13/13] drm/msm: Implement HDCP 1.x using the new drm HDCP helpers
In reply to Sean PaulQuoted 123 lines · Sean Paul
From: Sean Paul <[email protected]>
This patch adds HDCP 1.x support to msm DP connectors using the new HDCP helpers.
Cc Stephen Boyd <[email protected]>Signed-off-by Sean Paul <[email protected]>Link:
https://patchwork.freedesktop.org/patch/msgid/[email protected]
#v1Changes in v2:
-Squash [1] into this patch with the following changes (Stephen)
-Update the sc7180 dtsi file
-Remove resource names and just use index (Stephen)[1]
https://patchwork.freedesktop.org/patch/msgid/[email protected]--- arch/arm64/boot/dts/qcom/sc7180.dtsi | 4 +- drivers/gpu/drm/msm/Makefile | 1 + drivers/gpu/drm/msm/dp/dp_debug.c | 49 ++- drivers/gpu/drm/msm/dp/dp_debug.h | 6 +- drivers/gpu/drm/msm/dp/dp_display.c | 45 ++- drivers/gpu/drm/msm/dp/dp_display.h | 5 + drivers/gpu/drm/msm/dp/dp_drm.c | 68 ++++- drivers/gpu/drm/msm/dp/dp_drm.h | 5 + drivers/gpu/drm/msm/dp/dp_hdcp.c | 433 +++++++++++++++++++++++++++ drivers/gpu/drm/msm/dp/dp_hdcp.h | 27 ++ drivers/gpu/drm/msm/dp/dp_parser.c | 22 +- drivers/gpu/drm/msm/dp/dp_parser.h | 4 + drivers/gpu/drm/msm/dp/dp_reg.h | 44 ++- drivers/gpu/drm/msm/msm_atomic.c | 15 + 14 files changed, 709 insertions(+), 19 deletions(-) create mode 100644 drivers/gpu/drm/msm/dp/dp_hdcp.c create mode 100644 drivers/gpu/drm/msm/dp/dp_hdcp.harch/arm64/boot/dts/qcom/sc7180.dtsi +3
-1@@ -3088,7 +3088,9 @@ mdss_dp: displayport-controller@ae90000 { compatible = "qcom,sc7180-dp"; status = "disabled"; - reg = <0 0x0ae90000 0 0x1400>; + reg = <0 0x0ae90000 0 0x1400>, + <0 0x0aed1000 0 0x174>, + <0 0x0aee1000 0 0x2c>; interrupt-parent = <&mdss>; interrupts = <12>;drivers/gpu/drm/msm/Makefile +1
-0@@ -109,6 +109,7 @@ msm-$(CONFIG_DRM_MSM_DP)+= dp/dp_aux.o \ dp/dp_ctrl.o \ dp/dp_display.o \ dp/dp_drm.o \ + dp/dp_hdcp.o \ dp/dp_hpd.o \ dp/dp_link.o \ dp/dp_panel.o \drivers/gpu/drm/msm/dp/dp_debug.c +24
-0@@ -8,6 +8,7 @@#include <linux/debugfs.h> #include <drm/drm_connector.h> #include <drm/drm_file.h> +#include <drm/drm_hdcp.h> #include "dp_parser.h" #include "dp_catalog.h" @@ -15,6 +16,7 @@#include "dp_ctrl.h" #include "dp_debug.h" #include "dp_display.h" +#include "dp_hdcp.h" #define DEBUG_NAME "msm_dp"@@ -24,6 +26,7 @@ struct dp_debug_private {struct dp_usbpd *usbpd;struct dp_link *link;struct dp_panel *panel; +struct dp_hdcp *hdcp;struct drm_connector **connector;struct device *dev;struct drm_device *drm_dev;@@ -349,6 +352,38 @@ static int dp_test_active_open(struct inode *inode, inode->i_private); } +static ssize_t dp_hdcp_key_write (struct file *file,const char __user *ubuf, +size_t len,loff_t *offp) +{ +char *input_buffer; +int ret =0 ; +struct dp_debug_private *debug = file->private_data; +struct drm_device *dev; + + dev = debug->drm_dev; + +if (len != (DRM_HDCP_KSV_LEN +DP_HDCP_NUM_KEYS *DP_HDCP_KEY_LEN )) +return -EINVAL ; + +if (!debug->hdcp) +return -ENOENT ; + + input_buffer =memdup_user_nul (ubuf, len); +if (IS_ERR (input_buffer)) +return PTR_ERR (input_buffer); + + ret =dp_hdcp_ingest_key (debug->hdcp, input_buffer, len);
drivers/gpu/drm/msm/dp/dp_debug.c static int dp_test_active_open(struct inode · line 387
Quoted 10 lines
drivers/gpu/drm/msm/dp/dp_debug.c +10
-0+ +kfree (input_buffer); +if (ret <0 ) { +DRM_ERROR ("Could not ingest HDCP key, ret=%d\n" , ret); +return ret; + } + + *offp += len; +return len; +}
It seems like the HDCP keys written using debugfs, just for my understanding, are you storing this in some secure partition and the usermode reads from it and writes them here?
Quoted 282 lines
drivers/gpu/drm/msm/dp/dp_debug.c +1
-0+static const struct file_operations dp_debug_fops = {drivers/gpu/drm/msm/dp/dp_debug.c +6
-0.open = simple_open, .read = dp_debug_read_info,@@ -363,6 +398,12 @@ static const struct file_operations test_active_fops = { .write = dp_test_active_write }; +static const struct file_operations dp_hdcp_key_fops = { + .owner =THIS_MODULE , + .open = simple_open, + .write = dp_hdcp_key_write, +}; +static int dp_debug_init (struct dp_debug *dp_debug,struct drm_minor *minor){
drivers/gpu/drm/msm/dp/dp_debug.c +4
-0int rc =0 ;@@ -384,6 +425,10 @@ static int dp_debug_init(struct dp_debug *dp_debug, struct drm_minor *minor) minor->debugfs_root, debug, &dp_test_type_fops); +debugfs_create_file ("msm_dp_hdcp_key" ,0222 , + minor->debugfs_root, + debug, &dp_hdcp_key_fops); + debug->root = minor->debugfs_root;drivers/gpu/drm/msm/dp/dp_debug.c +2
-1return rc;@@ -391,7 +436,8 @@ static int dp_debug_init(struct dp_debug *dp_debug, struct drm_minor *minor)struct dp_debug *dp_debug_get (struct device *dev,struct dp_panel *panel,struct dp_usbpd *usbpd,struct dp_link *link, -struct drm_connector **connector,struct drm_minor *minor) +struct dp_hdcp *hdcp,struct drm_connector **connector, +struct drm_minor *minor) {drivers/gpu/drm/msm/dp/dp_debug.c +1
-0int rc =0 ;struct dp_debug_private *debug;@@ -413,6 +459,7 @@ struct dp_debug *dp_debug_get(struct device *dev,struct dp_panel *panel, debug->usbpd = usbpd; debug->link = link; debug->panel = panel; + debug->hdcp = hdcp; debug->dev = dev; debug->drm_dev = minor->dev;drivers/gpu/drm/msm/dp/dp_debug.c +0
-0debug->connector = connector;drivers/gpu/drm/msm/dp/dp_debug.h +2
-1@@ -6,6 +6,7 @@#ifndef _DP_DEBUG_H_#define _DP_DEBUG_H_ +#include "dp_hdcp.h" #include "dp_panel.h" #include "dp_link.h" @@ -43,7 +44,7 @@ struct dp_debug {*/ struct dp_debug *dp_debug_get (struct device *dev,struct dp_panel *panel,struct dp_usbpd *usbpd,struct dp_link *link, -struct drm_connector **connector, +struct dp_hdcp *hdcp,struct drm_connector **connector,struct drm_minor *minor);/**
drivers/gpu/drm/msm/dp/dp_debug.h +2
-1@@ -60,7 +61,8 @@ void dp_debug_put(struct dp_debug *dp_debug);static inline struct dp_debug *dp_debug_get (struct device *dev,struct dp_panel *panel,struct dp_usbpd *usbpd,struct dp_link *link, -struct drm_connector **connector,struct drm_minor *minor) +struct dp_hdcp *hdcp,struct drm_connector **connector, +struct drm_minor *minor) {return ERR_PTR (-EINVAL );}
drivers/gpu/drm/msm/dp/dp_display.c +11
-0@@ -26,6 +26,7 @@#include "dp_drm.h" #include "dp_audio.h" #include "dp_debug.h" +#include "dp_hdcp.h" static struct msm_dp *g_dp_display;#define HPD_STRING_SIZE 30@@ -96,6 +97,7 @@ struct dp_display_private {struct dp_panel *panel;struct dp_ctrl *ctrl;struct dp_debug *debug; +struct dp_hdcp *hdcp;struct dp_usbpd_cb usbpd_cb;struct dp_display_mode dp_mode;@@ -121,6 +123,15 @@ static const struct of_device_id dp_dt_match[] = { {} }; +struct dp_hdcp *dp_display_connector_to_hdcp (struct drm_connector *connector) +{ +struct msm_dp *dp_display =msm_dp_from_connector (connector); +struct dp_display_private *dp; + + dp = container_of(dp_display, struct dp_display_private, dp_display); +return dp->hdcp; +} +static int dp_add_event (struct dp_display_private *dp_priv,u32 event,u32 data,u32 delay){
drivers/gpu/drm/msm/dp/dp_display.c +1
-0@@ -714,6 +725,7 @@ static int dp_irq_hpd_handle(struct dp_display_private *dp, u32 data)static void dp_display_deinit_sub_modules (struct dp_display_private *dp) {dp_debug_put (dp->debug); +dp_hdcp_put (dp->hdcp);dp_audio_put (dp->audio);drivers/gpu/drm/msm/dp/dp_display.c +10
-0dp_panel_put (dp->panel);dp_aux_put (dp->aux);@@ -810,8 +822,18 @@ static int dp_init_sub_modules(struct dp_display_private *dp) goto error_ctrl; } + dp->hdcp =dp_hdcp_get (dp->parser, dp->aux); +if (IS_ERR (dp->hdcp)) { + rc =PTR_ERR (dp->hdcp); +DRM_ERROR ("failed to initialize hdcp, rc = %d\n" , rc); + dp->hdcp =NULL ; + goto error_hdcp; + } +return rc; +error_hdcp: +dp_audio_put (dp->audio); error_ctrl:dp_panel_put (dp->panel);
error_link:drivers/gpu/drm/msm/dp/dp_display.c +9
-0@@ -930,6 +952,15 @@ int dp_display_set_plugged_cb(struct msm_dp *dp_display, return 0; } +void dp_display_hdcp_commit (struct msm_dp *dp,struct drm_atomic_state *state) +{ +struct dp_display_private *dp_display; + + dp_display = container_of(dp, struct dp_display_private, dp_display); + +dp_hdcp_commit (dp_display->hdcp, state); +} +int dp_display_validate_mode (struct msm_dp *dp,u32 mode_pclk_khz){
drivers/gpu/drm/msm/dp/dp_display.c +2
-2const u32 num_components =3 , default_bpp =24 ;@@ -1429,8 +1460,8 @@ void msm_dp_debugfs_init(struct msm_dp *dp_display, struct drm_minor *minor) dev = &dp->pdev->dev; dp->debug =dp_debug_get (dev, dp->panel, dp->usbpd, - dp->link, &dp->dp_display.connector, - minor); + dp->link, dp->hdcp, + &dp->dp_display.connector, minor);if (IS_ERR (dp->debug)) { rc =PTR_ERR (dp->debug);drivers/gpu/drm/msm/dp/dp_display.c +4
-0DRM_ERROR ("failed to initialize debug, rc = %d\n" , rc);@@ -1441,12 +1472,16 @@ void msm_dp_debugfs_init(struct msm_dp *dp_display, struct drm_minor *minor)int msm_dp_modeset_init (struct msm_dp *dp_display,struct drm_device *dev,struct drm_encoder *encoder) { +struct dp_display_private *dp_display_priv;struct msm_drm_private *priv;int ret;if (WARN_ON (!encoder) ||WARN_ON (!dp_display) ||WARN_ON (!dev))return -EINVAL ; + dp_display_priv = container_of(dp_display, struct dp_display_private, + dp_display); + priv = dev->dev_private;drivers/gpu/drm/msm/dp/dp_display.c +6
-0dp_display->drm_dev = dev;@@ -1467,6 +1502,12 @@ int msm_dp_modeset_init(struct msm_dp *dp_display, struct drm_device *dev, return ret; } + ret =dp_hdcp_attach (dp_display_priv->hdcp, dp_display->connector); +if (ret) { +DRM_ERROR ("Failed to attach hdcp, ret=%d\n" , ret); +return ret; + } + priv->connectors[priv->num_connectors++] = dp_display->connector;return 0 ;}
drivers/gpu/drm/msm/dp/dp_display.h +5
-0@@ -27,8 +27,13 @@ struct msm_dp {struct dp_audio *dp_audio; }; +struct drm_atomic_state ; +int dp_display_set_plugged_cb (struct msm_dp *dp_display,hdmi_codec_plugged_cb fn,struct device *codec_dev); +struct dp_hdcp *dp_display_connector_to_hdcp (struct drm_connector *connector); +void dp_display_hdcp_commit (struct msm_dp *dp_display, +struct drm_atomic_state *state);int dp_display_validate_mode (struct msm_dp *dp_display,u32 mode_pclk_khz);int dp_display_get_modes(struct
msm_dp*dp_display,drivers/gpu/drm/msm/dp/dp_display.h +0
-0struct dp_display_mode *dp_mode);drivers/gpu/drm/msm/dp/dp_drm.c +9
-0@@ -5,11 +5,20 @@#include <drm/drm_atomic_helper.h> #include <drm/drm_atomic.h> +#include <drm/drm_connector.h> #include <drm/drm_crtc.h> +#include <drm/drm_hdcp.h> #include "msm_drv.h" #include "msm_kms.h" #include "dp_drm.h" +#include "dp_hdcp.h" + +struct dp_connector_state { +struct drm_connector_state base; +bool hdcp_transition; +}; +#define to_dp_connector_state (x) container_of(x, struct dp_connector_state, base) struct dp_connector {drivers/gpu/drm/msm/dp/dp_drm.c +5
-0struct drm_connector base;@@ -17,6 +26,11 @@ struct dp_connector { };#define to_dp_connector (x) container_of(x, struct dp_connector, base) +struct msm_dp *msm_dp_from_connector (struct drm_connector *connector) +{ +return to_dp_connector (connector)->dp_display; +} +/** * dp_connector_detect - callback to determine if connector is connected
* @conn: Pointer to drm connector structuredrivers/gpu/drm/msm/dp/dp_drm.c +0
-0@@ -114,20 +128,72 @@ static enum drm_mode_statusdp_connector_mode_valid(
drivers/gpu/drm/msm/dp/dp_drm.c +0
-0return dp_display_validate_mode (dp_disp, mode->clock); }
drivers/gpu/drm/msm/dp/dp_drm.c static enum drm_mode_status dp_connector_mode_valid( · line 140
Quoted 10 lines
drivers/gpu/drm/msm/dp/dp_drm.c +10
-0+static int dp_connector_atomic_check (struct drm_connector *connector, +struct drm_atomic_state *state) +{ +struct drm_connector_state *conn_state; +struct dp_connector_state *dp_state; + + conn_state =drm_atomic_get_new_connector_state (state, connector); + dp_state =to_dp_connector_state (conn_state); + + dp_state->hdcp_transition =drm_hdcp_atomic_check (connector, state);
I have a general question related to the transition flag and overall tying the HDCP enable and authentication to the commit.
So lets say there is a case where the driver needs to disable HDCP. It could be due to link integrity failure OR some other error condition which usermode is not aware of. In that case, we will set this hdcp_transition to true but in the next commit we will actually do the authentication. What if usermode doesnt issue a new frame? This question arises because currently the link intergrity check is done using SW polling in the previous patchset. But as I had commented there, this occurs in HW for us. I dont see that isr itself in this patchset. So wanted to understand if thats part of this approach to still tie it with commit.
So if we go with the HW polling based approach which is the preferred method, we need to untie this from the commit.
Quoted 255 lines
drivers/gpu/drm/msm/dp/dp_drm.c +16
-0+ +return 0 ; +} + +static struct drm_connector_state * +dp_connector_atomic_duplicate_state (struct drm_connector *connector) +{ +struct dp_connector_state *state; + + state =kzalloc (sizeof (*state),GFP_KERNEL ); +if (!state) +return NULL ; + + state->hdcp_transition = false; + + __drm_atomic_helper_connector_duplicate_state(connector,
&state->base);drivers/gpu/drm/msm/dp/dp_drm.c +3
-1+return &state->base; +} +static const struct drm_connector_funcs dp_connector_funcs = { .detect = dp_connector_detect, .fill_modes = drm_helper_probe_single_connector_modes, .destroy = drm_connector_cleanup, .reset = drm_atomic_helper_connector_reset, - .atomic_duplicate_state =
drm_atomic_helper_connector_duplicate_state,drivers/gpu/drm/msm/dp/dp_drm.c +1
-0+ .atomic_duplicate_state = dp_connector_atomic_duplicate_state, .atomic_destroy_state = drm_atomic_helper_connector_destroy_state, }; static const struct drm_connector_helper_funcs
dp_connector_helper_funcs= {drivers/gpu/drm/msm/dp/dp_drm.c +23
-0.get_modes = dp_connector_get_modes, .mode_valid = dp_connector_mode_valid, + .atomic_check = dp_connector_atomic_check, }; +bool dp_drm_is_connector_msm_dp (struct drm_connector *connector) +{ +return connector->funcs == &dp_connector_funcs; +} + +void dp_drm_atomic_commit (struct drm_connector *connector, +struct drm_connector_state *conn_state, +struct drm_atomic_state *state) +{ +struct dp_connector_state *dp_state; +struct msm_dp *dp_disp; + + dp_state =to_dp_connector_state (conn_state); + +if (!dp_state->hdcp_transition) +return ; + + dp_disp =msm_dp_from_connector (connector); + +dp_display_hdcp_commit (dp_disp, state); +} +/* connector initialization */ struct drm_connector *dp_drm_connector_init (struct msm_dp *dp_display) {drivers/gpu/drm/msm/dp/dp_drm.h +5
-0@@ -14,5 +14,10 @@#include "dp_display.h" struct drm_connector *dp_drm_connector_init (struct msm_dp *dp_display); +struct msm_dp *msm_dp_from_connector (struct drm_connector *connector); +bool dp_drm_is_connector_msm_dp (struct drm_connector *connector); +void dp_drm_atomic_commit (struct drm_connector *connector, +struct drm_connector_state *conn_state, +struct drm_atomic_state *state);#endif /* _DP_DRM_H_ */
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +67
-0@@ -0,0 +1,433 @@ +// SPDX-License-Identifier: MIT +/* +* Copyright (C) 2021 Google, Inc. +* +* Authors: +* Sean Paul <[email protected]> +*/ + +#include "dp_display.h" +#include "dp_drm.h" +#include "dp_hdcp.h" +#include "dp_reg.h" + +#include <drm/drm_connector.h> +#include <drm/drm_device.h> +#include <drm/drm_dp_helper.h> +#include <drm/drm_hdcp.h> +#include <drm/drm_print.h> + +#include <linux/bitfield.h> +#include <linux/bits.h> +#include <linux/iopoll.h> +#include <linux/mutex.h> +#include <linux/random.h> +#include <linux/slab.h> + +/* Offsets based on hdcp_ksv mmio */ +#define DP_HDCP_KSV_AN_LSB 0x0 +#define DP_HDCP_KSV_AN_MSB 0x4 +#define DP_HDCP_KSV_AKSV_MSB 0x1D8 +#define DP_HDCP_KSV_AKSV_LSB 0x1DC + +/* Key offsets based on hdcp_key mmio */ +#define DP_HDCP_KEY_BASE 0x30 +#define DP_HDCP_KEY_MSB (x) (DP_HDCP_KEY_BASE + (x * 8)) +#define DP_HDCP_KEY_LSB (x) (DP_HDCP_KEY_MSB(x) + 4) +#define DP_HDCP_KEY_VALID 0x170 +#define DP_HDCP_SW_KEY_VALID BIT(0) + +/* +* dp_hdcp_key - structure which contains an HDCP key set +* @ksv: The key selection vector +* @keys: Contains 40 keys +*/ +struct dp_hdcp_key { +struct drm_hdcp_ksv ksv; +union { +u32 words[2 ]; +u8 bytes[DP_HDCP_KEY_LEN ]; + } keys[DP_HDCP_NUM_KEYS ]; +bool valid; +}; + +struct dp_hdcp { +struct drm_device *dev; +struct drm_connector *connector; + +struct drm_dp_aux *aux; +struct dp_parser *parser; + +struct drm_hdcp_helper_data *helper_data; + +struct mutex key_lock; +struct dp_hdcp_key *key; +}; + +static inline void dp_hdcp_write_dp(struct dp_hdcp *hdcp, u32 offset,u32 val)
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +10
-0+{ +writel (val, hdcp->parser->io.dp_controller.base + offset); +} + +static inline u32 dp_hdcp_read_dp (struct dp_hdcp *hdcp,u32 offset) +{ +return readl (hdcp->parser->io.dp_controller.base + offset); +} + +static inline void dp_hdcp_write_hdcp(struct dp_hdcp *hdcp, u32offset, u32 val)
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +10
-0+{ +writel (val, hdcp->parser->io.hdcp_key.base + offset); +} + +static inline u32 dp_hdcp_read_hdcp (struct dp_hdcp *hdcp,u32 offset) +{ +return readl (hdcp->parser->io.hdcp_key.base + offset); +} + +static inline void dp_hdcp_write_tz(struct dp_hdcp *hdcp, u32 offset,u32 val)
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +10
-0+{ +writel (val, hdcp->parser->io.hdcp_tz.base + offset); +} + +static inline u32 dp_hdcp_read_tz (struct dp_hdcp *hdcp,u32 offset) +{ +return readl (hdcp->parser->io.hdcp_tz.base + offset); +} + +int dp_hdcp_ingest_key(struct dp_hdcp *hdcp, const u8 *raw_key, int
raw_len)drivers/gpu/drm/msm/dp/dp_hdcp.c new file +9
-0+{ + struct dp_hdcp_key *key; + const u8 *ptr = raw_key; + unsigned int ksv_weight; + int i, ret = 0; + + mutex_lock(&hdcp->key_lock); + + if (raw_len != (DRM_HDCP_KSV_LEN + DP_HDCP_NUM_KEYS *
DP_HDCP_KEY_LEN)) {drivers/gpu/drm/msm/dp/dp_hdcp.c new file +11
-0+DRM_ERROR ("Invalid HDCP key length expected=%d actual=%d\n" , + (DRM_HDCP_KSV_LEN +DP_HDCP_NUM_KEYS *DP_HDCP_KEY_LEN ), + raw_len); + ret = -EINVAL ; + goto out; + } + + key = hdcp->key; + +memcpy (key->ksv.bytes, ptr,DRM_HDCP_KSV_LEN ); + ksv_weight = hweight32(key->ksv.words[0]) +
hweight32(key->ksv.words[1]);drivers/gpu/drm/msm/dp/dp_hdcp.c new file +28
-0+if (ksv_weight !=20 ) { +DRM_ERROR ("Invalid ksv weight, expected=20 actual=%d\n" , + ksv_weight); + ret = -EINVAL ; + goto out; + } + + ptr +=DRM_HDCP_KSV_LEN ; +for (i =0 ; i <DP_HDCP_NUM_KEYS ; i++) { +memcpy (key->keys[i].bytes, ptr,DP_HDCP_KEY_LEN ); + ptr +=DP_HDCP_KEY_LEN ; + } + +DRM_DEBUG_DRIVER ("Successfully ingested HDCP key\n" ); + hdcp->key->valid = true; + +out: +mutex_unlock (&hdcp->key_lock); +return ret; +} + +static bool dp_hdcp_are_keys_valid (struct drm_connector *connector) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +u32 val; + + val =dp_hdcp_read_dp (hdcp,DP_HDCP_STATUS ); + return FIELD_GET(DP_HDCP_KEY_STATUS, val) ==
DP_HDCP_KEY_STATUS_VALID;drivers/gpu/drm/msm/dp/dp_hdcp.c new file +18
-0+} + +static int dp_hdcp_load_keys (struct drm_connector *connector) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +struct dp_hdcp_key *key; +int i, ret =0 ; + +mutex_lock (&hdcp->key_lock); + + key = hdcp->key; + +if (!key->valid) { + ret = -ENOENT ; + goto out; + } + +dp_hdcp_write_dp (hdcp,DP_HDCP_SW_LOWER_AKSV , key->ksv.words[0 ]);
drivers/gpu/drm/msm/dp/dp_hdcp.c line 173
Quoted 10 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +10
-0+dp_hdcp_write_dp (hdcp,DP_HDCP_SW_UPPER_AKSV , key->ksv.words[1 ]); + +for (i =0 ; i <DP_HDCP_NUM_KEYS ; i++) { +dp_hdcp_write_hdcp (hdcp,DP_HDCP_KEY_LSB (i), + key->keys[i].words[0 ]); +dp_hdcp_write_hdcp (hdcp,DP_HDCP_KEY_MSB (i), + key->keys[i].words[1 ]); + } + +dp_hdcp_write_hdcp (hdcp,DP_HDCP_KEY_VALID ,DP_HDCP_SW_KEY_VALID );
I think all of these are TZ_*** registers. So the separation of write_hdcp() Vs write_hdcp_tz() is not very clear to me.
Maybe change the write APIs to something like dp_hdcp_write_hdcp_tz() for the first address space and dp_hdcp_write_hdcp_tz_hlos() for the other one?
Quoted 50 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +12
-0+wmb (); + +dp_hdcp_write_dp (hdcp,DP_HDCP_ENTROPY_CTRL0 ,get_random_u32 ()); +dp_hdcp_write_dp (hdcp,DP_HDCP_ENTROPY_CTRL1 ,get_random_u32 ()); +wmb (); + +out: +mutex_unlock (&hdcp->key_lock); +return ret; +} + +static int dp_hdcp_hdcp2_capable(struct drm_connector *connector,bool *capable)
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +16
-0+{ + *capable = false; +return 0 ; +} + +static int dp_hdcp_hdcp1_read_an_aksv (struct drm_connector *connector, +u32 *an,u32 *aksv) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +bool keys_valid; +int ret; +u32 val; + +dp_hdcp_write_dp (hdcp,DP_HDCP_CTRL ,1 ); + + ret = read_poll_timeout(dp_hdcp_are_keys_valid, keys_valid,
keys_valid,drivers/gpu/drm/msm/dp/dp_hdcp.c new file +11
-0+ 20 * 1000, 10 * 1000, false, connector); +if (ret) { +drm_err (hdcp->dev,"HDCP keys invalid %d\n" , ret); +return ret; + } + +/* Clear AInfo */ +dp_hdcp_write_dp (hdcp,DP_HDCP_RCVPORT_DATA4 ,0 ); + + aksv[0 ] =dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA3 ); + aksv[1] = GENMASK(7, 0) & dp_hdcp_read_dp(hdcp,
DP_HDCP_RCVPORT_DATA4);drivers/gpu/drm/msm/dp/dp_hdcp.c new file +8
-0+ + ret =read_poll_timeout (dp_hdcp_read_dp, val, + (val &DP_HDCP_AN_READY_MASK ) ==DP_HDCP_AN_READY_MASK , +100 ,10 *1000 , false, hdcp,DP_HDCP_STATUS ); +if (ret) { +drm_err (hdcp->dev,"AN failed to become ready %x/%d\n" , val, ret); +return ret; + }
drivers/gpu/drm/msm/dp/dp_hdcp.c line 230
Quoted 10 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +10
-0+ +/* +* Get An from hardware, for unknown reasons we need to read the reg +* twice to get valid data. +*/ +dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA5 ); + an[0 ] =dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA5 ); + +dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA6 ); + an[1 ] =dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA6 );
Yes its true, but we also have a 1 microsec delay between the first and second one. So I would certainly preserve that.
Quoted 20 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +5
-0+ +return 0 ; +} + +static int dp_hdcp_hdcp1_store_receiver_info(struct drm_connector*connector,
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +14
-0+ u32 *ksv, u32 status, u8 bcaps, + bool is_repeater) +{ + struct dp_hdcp *hdcp = dp_display_connector_to_hdcp(connector); +u32 val; + +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA0 , + ksv[0 ]); +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA1 , + ksv[1 ]); + + val = ((status &GENMASK (15 ,0 )) <<8 ) | (bcaps &GENMASK (7 ,0 )); + + dp_hdcp_write_tz(hdcp, HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA12,
Quoted 2 lines
val);
+
Cant this entire API be skipped for non-repeater cases from the hdcp lib layer? You can write the bcaps to this earlier and write the bstatus only if its a repeater.
Quoted 422 lines
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +4
-0+return 0 ; +} + +static int dp_hdcp_hdcp1_enable_encryption(struct drm_connector*connector)
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +11
-0+{ +return 0 ; +} + +static int dp_hdcp_hdcp1_wait_for_r0 (struct drm_connector *connector) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +int ret; +u32 val; + + ret = read_poll_timeout(dp_hdcp_read_dp, val, (val &
DP_HDCP_R0_READY),drivers/gpu/drm/msm/dp/dp_hdcp.c new file +11
-0+100 ,1000 , false, hdcp, + DP_HDCP_STATUS); +if (ret) { +drm_err (hdcp->dev,"HDCP R0 not ready %x/%d\n" , val, ret); +return ret; + } + +return 0 ; +} + +static int dp_hdcp_hdcp1_match_ri(struct drm_connector *connector,u32
ri_prime)drivers/gpu/drm/msm/dp/dp_hdcp.c new file +8
-0+{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +int ret; +u32 val; + +dp_hdcp_write_dp (hdcp,DP_HDCP_RCVPORT_DATA2_0 , ri_prime); + + ret = read_poll_timeout(dp_hdcp_read_dp, val, (val &
DP_HDCP_RI_MATCH),drivers/gpu/drm/msm/dp/dp_hdcp.c new file +11
-0+20 *1000 ,100 *1000 , false, hdcp, + DP_HDCP_STATUS); +if (ret) { +drm_err (hdcp->dev,"Failed to match Ri and Ri` (%08x) %08x/%d\n" , + ri_prime, val, ret); +return ret; + } +return 0 ; +} + +static int dp_hdcp_hdcp1_store_ksv_fifo(struct drm_connector*connector,
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +68
-0+ u8 *ksv_fifo, u8 num_downstream, + u8 *bstatus, u32 *vprime) +{ + struct dp_hdcp *hdcp = dp_display_connector_to_hdcp(connector); +int num_bytes = (num_downstream *DRM_HDCP_KSV_LEN ); +int ret, i; +u32 val; + +/* Reset the SHA computation block */ +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_SHA_CTRL , +DP_HDCP_SHA_CTRL_RESET ); +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_SHA_CTRL ,0 ); + +/* +* KSV info gets written a byte at a time in the same order it was +* received. Every 64 bytes, we need to wait for the SHA_BLOCK_DONE +* bit to be set in SHA_CTRL. +*/ +for (i =0 ; i < num_bytes; i++) { + val =FIELD_PREP (DP_HDCP_SHA_DATA_MASK , ksv_fifo[i]); + +if (i == (num_bytes -1 )) + val |=DP_HDCP_SHA_DATA_DONE ; + +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_SHA_DATA , + val); + +if (((i +1 ) %64 ) !=0 ) +continue ; + + ret =read_poll_timeout (dp_hdcp_read_dp, val, + (val &DP_HDCP_SHA_DONE ),100 , +100 *1000 , false, hdcp, +DP_HDCP_SHA_STATUS ); +if (ret) { +drm_err (hdcp->dev,"SHA block incomplete %d\n" , ret); +return ret; + } + } + + ret =read_poll_timeout (dp_hdcp_read_dp, val, + (val &DP_HDCP_SHA_COMP_DONE ),100 ,100 *1000 , + false, hdcp,DP_HDCP_SHA_STATUS ); +if (ret) { +drm_err (hdcp->dev,"SHA computation incomplete %d\n" , ret); +return ret; + } + +return 0 ; +} + +static int dp_hdcp_hdcp1_disable (struct drm_connector *connector) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +u32 val; + + val =dp_hdcp_read_dp (hdcp,REG_DP_SW_RESET ); +dp_hdcp_write_dp (hdcp,REG_DP_SW_RESET , val |DP_HDCP_SW_RESET ); + +/* Disable encryption and disable the HDCP block */ +dp_hdcp_write_dp (hdcp,DP_HDCP_CTRL ,0 ); + +dp_hdcp_write_dp (hdcp,REG_DP_SW_RESET , val); + +return 0 ; +} + +void dp_hdcp_commit(struct dp_hdcp *hdcp, struct drm_atomic_state*state)
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +18
-0+{ +drm_hdcp_helper_atomic_commit (hdcp->helper_data, state,NULL ); +} + +static const struct drm_hdcp_helper_funcs dp_hdcp_funcs = { + .are_keys_valid = dp_hdcp_are_keys_valid, + .load_keys = dp_hdcp_load_keys, + .hdcp2_capable = dp_hdcp_hdcp2_capable, + .hdcp1_read_an_aksv = dp_hdcp_hdcp1_read_an_aksv, + .hdcp1_store_receiver_info = dp_hdcp_hdcp1_store_receiver_info, + .hdcp1_enable_encryption = dp_hdcp_hdcp1_enable_encryption, + .hdcp1_wait_for_r0 = dp_hdcp_hdcp1_wait_for_r0, + .hdcp1_match_ri = dp_hdcp_hdcp1_match_ri, + .hdcp1_store_ksv_fifo = dp_hdcp_hdcp1_store_ksv_fifo, + .hdcp1_disable = dp_hdcp_hdcp1_disable, +}; + +int dp_hdcp_attach(struct dp_hdcp *hdcp, struct drm_connector*connector)
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +15
-0+{ +struct drm_device *dev = connector->dev; +struct drm_hdcp_helper_data *helper_data; +int ret; + +/* HDCP is not configured for this device */ +if (!hdcp || !hdcp->parser || hdcp->parser->io.hdcp_key.len ==0 ) +return 0 ; + + helper_data =drm_hdcp_helper_initialize_dp (connector, hdcp->aux, + &dp_hdcp_funcs, false); +if (IS_ERR_OR_NULL (helper_data)) +return PTR_ERR (helper_data); + + ret = drm_connector_attach_content_protection_property(connector,false);
drivers/gpu/drm/msm/dp/dp_hdcp.c new file +14
-0+if (ret) { +drm_hdcp_helper_destroy (helper_data); +drm_err (dev,"Failed to attach content protection prop %d\n" , ret); +return ret; + } + + hdcp->dev = connector->dev; + hdcp->connector = connector; + hdcp->helper_data = helper_data; + +return 0 ; +} + +struct dp_hdcp *dp_hdcp_get(struct dp_parser *parser, struct
drm_dp_aux*aux)drivers/gpu/drm/msm/dp/dp_hdcp.c new file +8
-0+{ +struct dp_hdcp *hdcp; + + hdcp =devm_kzalloc (&parser->pdev->dev,sizeof (*hdcp),GFP_KERNEL ); +if (!hdcp) +return ERR_PTR (-ENOMEM ); + + hdcp->key = devm_kzalloc(&parser->pdev->dev, sizeof(*hdcp->key),
GFP_KERNEL);drivers/gpu/drm/msm/dp/dp_hdcp.c new file +15
-0+if (!hdcp->key) +return ERR_PTR (-ENOMEM ); + + hdcp->parser = parser; + hdcp->aux = aux; + +mutex_init (&hdcp->key_lock); + +return hdcp; +} + +void dp_hdcp_put (struct dp_hdcp *hdcp) +{ +drm_hdcp_helper_destroy (hdcp->helper_data); +}drivers/gpu/drm/msm/dp/dp_hdcp.h new file +20
-0@@ -0,0 +1,27 @@ +// SPDX-License-Identifier: MIT +/* +* Copyright (C) 2021 Google, Inc. +* +* Authors: +* Sean Paul <[email protected]> +*/ + +#ifndef DP_HDCP_H_ +#define DP_HDCP_H_ + +#define DP_HDCP_KEY_LEN 7 +#define DP_HDCP_NUM_KEYS 40 + +struct dp_hdcp ; +struct dp_parser ; +struct drm_atomic_state ; +struct drm_dp_aux ; + +struct dp_hdcp *dp_hdcp_get(struct dp_parser *parser, struct
drm_dp_aux*aux);drivers/gpu/drm/msm/dp/dp_hdcp.h new file +3
-0+void dp_hdcp_put (struct dp_hdcp *hdcp); + +int dp_hdcp_attach(struct dp_hdcp *hdcp, struct drm_connector*connector);
+intdp_hdcp_ingest_key(struct dp_hdcp *hdcp, const u8 *raw_key, int raw_len);
+voiddp_hdcp_commit(struct dp_hdcp *hdcp, struct drm_atomic_state *state);drivers/gpu/drm/msm/dp/dp_hdcp.h new file +2
-0+ +#endif drivers/gpu/drm/msm/dp/dp_parser.c +2
-2@@ -20,11 +20,11 @@ static const struct dp_regulator_cfg sdm845_dp_reg_cfg = { };static int msm_dss_ioremap (struct platform_device *pdev, -struct dss_io_data *io_data) +struct dss_io_data *io_data,int idx) {struct resource *res =NULL ; - res =platform_get_resource (pdev,IORESOURCE_MEM ,0 ); + res =platform_get_resource (pdev,IORESOURCE_MEM , idx);if (!res) { DRM_ERROR("%pS->%s: msm_dss_get_res failed\n",drivers/gpu/drm/msm/dp/dp_parser.c +15
-3__builtin_return_address(0), __func__);@@ -55,6 +55,8 @@ static void dp_parser_unmap_io_resources(struct dp_parser *parser) {struct dp_io *io = &parser->io; +msm_dss_iounmap (&io->hdcp_tz); +msm_dss_iounmap (&io->hdcp_key);msm_dss_iounmap (&io->dp_controller); }@@ -64,10 +66,20 @@ static int dp_parser_ctrl_res(struct dp_parser *parser)struct platform_device *pdev = parser->pdev;struct dp_io *io = &parser->io; - rc =msm_dss_ioremap (pdev, &io->dp_controller); -if (rc) { -DRM_ERROR ("unable to remap dp io resources, rc=%d\n" , rc); + rc =msm_dss_ioremap (pdev, &io->dp_controller,0 ); +if (rc) goto err; + + rc =msm_dss_ioremap (pdev, &io->hdcp_key,1 ); +if (rc) { + io->hdcp_key.base =NULL ; + io->hdcp_key.len =0 ; + } + + rc =msm_dss_ioremap (pdev, &io->hdcp_tz,2 ); +if (rc) { + io->hdcp_tz.base =NULL ; + io->hdcp_tz.len =0 ; }drivers/gpu/drm/msm/dp/dp_parser.c +0
-0io->phy =devm_phy_get (&pdev->dev,"dp" );drivers/gpu/drm/msm/dp/dp_parser.h +4
-0@@ -62,10 +62,14 @@ struct dp_display_data {* struct dp_ctrl_resource - controller's IO related data * * @dp_controller: Display Port controller mapped memory address +* @hdcp_key: mapped memory for HDCP key ingestion +* @hdcp_tz: mapped memory for HDCP TZ interaction * @phy_io: phy's mapped memory address */ struct dp_io {struct dss_io_data dp_controller; +struct dss_io_data hdcp_key; +struct dss_io_data hdcp_tz;struct phy *phy;union phy_configure_opts phy_opts; };drivers/gpu/drm/msm/dp/dp_reg.h +37
-7@@ -6,11 +6,14 @@#ifndef _DP_REG_H_#define _DP_REG_H_ +#include <linux/bits.h> +/* DP_TX Registers */ #define REG_DP_HW_VERSION (0x00000000)#define REG_DP_SW_RESET (0x00000010) -#define DP_SW_RESET (0x00000001) +#define DP_SW_RESET BIT(0) +#define DP_HDCP_SW_RESET BIT(1)#define REG_DP_PHY_CTRL (0x00000014)#define DP_PHY_CTRL_SW_RESET_PLL (0x00000001)@@ -283,19 +286,46 @@/* DP HDCP 1.3 registers */ #define DP_HDCP_CTRL (0x0A0)#define DP_HDCP_STATUS (0x0A4) -#define DP_HDCP_SW_UPPER_AKSV (0x098) -#define DP_HDCP_SW_LOWER_AKSV (0x09C) -#define DP_HDCP_ENTROPY_CTRL0 (0x350) -#define DP_HDCP_ENTROPY_CTRL1 (0x35C) +#define DP_HDCP_KEY_STATUS GENMASK(18, 16) +#define DP_HDCP_KEY_STATUS_NO_KEYS 0 +#define DP_HDCP_KEY_STATUS_NOT_CHECKED 1 +#define DP_HDCP_KEY_STATUS_CHECKING 2 +#define DP_HDCP_KEY_STATUS_VALID 3 +#define DP_HDCP_KEY_STATUS_INVALID_AKSV 4 +#define DP_HDCP_KEY_STATUS_BAD_CHECKSUM 5 +#define DP_HDCP_KEY_STATUS_PROD_AKSV 6 +#define DP_HDCP_KEY_STATUS_RESV 7 +#define DP_HDCP_R0_READY BIT(14) +#define DP_HDCP_SHA_V_MATCH BIT(13) +#define DP_HDCP_RI_MATCH BIT(12) +#define DP_HDCP_AN_MSB_READY BIT(9) +#define DP_HDCP_AN_LSB_READY BIT(8) +#define DP_HDCP_AN_READY_MASK (DP_HDCP_AN_MSB_READY | DP_HDCP_AN_LSB_READY) +#define DP_HDCP_AUTH_FAIL_INFO GENMASK(7, 4) +#define DP_HDCP_AUTH_FAIL_INVALID_AKSV 3 +#define DP_HDCP_AUTH_FAIL_INVALID_BKSV 4 +#define DP_HDCP_AUTH_FAIL_RI_MISMATCH 5 +#define DP_HDCP_AUTH_FAIL BIT(2) +#define DP_HDCP_AUTH_SUCCESS BIT(0) +#define DP_HDCP_SW_UPPER_AKSV (0x298) +#define DP_HDCP_SW_LOWER_AKSV (0x29C) +#define DP_HDCP_ENTROPY_CTRL0 (0x750) +#define DP_HDCP_ENTROPY_CTRL1 (0x75C)#define DP_HDCP_SHA_STATUS (0x0C8) +#define DP_HDCP_SHA_COMP_DONE BIT(4) +#define DP_HDCP_SHA_DONE BIT(0)#define DP_HDCP_RCVPORT_DATA2_0 (0x0B0) -#define DP_HDCP_RCVPORT_DATA3 (0x0A4) -#define DP_HDCP_RCVPORT_DATA4 (0x0A8) +#define DP_HDCP_RCVPORT_DATA3 (0x2A4) +#define DP_HDCP_RCVPORT_DATA4 (0x2A8)#define DP_HDCP_RCVPORT_DATA5 (0x0C0)#define DP_HDCP_RCVPORT_DATA6 (0x0C4) +#define DP_HDCP_RCVPORT_DATA7 (0x0C8)#define HDCP_SEC_DP_TZ_HV_HLOS_HDCP_SHA_CTRL (0x024) +#define DP_HDCP_SHA_CTRL_RESET BIT(0)#define HDCP_SEC_DP_TZ_HV_HLOS_HDCP_SHA_DATA (0x028) +#define DP_HDCP_SHA_DATA_MASK GENMASK(23, 16) +#define DP_HDCP_SHA_DATA_DONE BIT(0)#define HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA0 (0x004)#define HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA1 (0x008)#define
HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA7(0x00C)drivers/gpu/drm/msm/msm_atomic.c +13
-0@@ -8,6 +8,7 @@#include <drm/drm_gem_atomic_helper.h> #include <drm/drm_vblank.h> +#include "dp_drm.h" #include "msm_atomic_trace.h" #include "msm_drv.h" #include "msm_gem.h" @@ -203,6 +204,18 @@ static unsigned get_crtc_mask(struct drm_atomic_state *state)return mask; } +static void msm_atomic_commit_connectors (struct drm_atomic_state *state) +{ +struct drm_connector_state *conn_state; +struct drm_connector *connector; +int i; + +for_each_new_connector_in_state (state, connector, conn_state, i) { +if (dp_drm_is_connector_msm_dp (connector)) +dp_drm_atomic_commit (connector, conn_state, state); + } +} +void msm_atomic_commit_tail (struct drm_atomic_state *state){
drivers/gpu/drm/msm/msm_atomic.c +2
-0struct drm_device *dev = state->dev;@@ -239,6 +252,8 @@ void msm_atomic_commit_tail(struct drm_atomic_state *state)drm_atomic_helper_commit_planes (dev, state,0 );drm_atomic_helper_commit_modeset_enables (dev, state); +msm_atomic_commit_connectors (state); +if (async) { struct msm_pending_timer *timer =&kms->pending_timers[drm_crtc_index(async_crtc)];
Sean Paul
reviewerRe: [Freedreno] [PATCH v2 13/13] drm/msm: Implement HDCP 1.x using the new drm HDCP helpers
Quoted 19 lines · On Tue, Sep 21, 2021 at 07:25:41PM -0700, [email protected] wrote:
Quoted 16 lines · Sean Paul
From: Sean Paul <[email protected]>
This patch adds HDCP 1.x support to msm DP connectors using the new HDCP helpers.
Cc Stephen Boyd <[email protected]>Signed-off-by Sean Paul <[email protected]>Link:
https://patchwork.freedesktop.org/patch/msgid/[email protected]
#v1Changes in v2:
-Squash [1] into this patch with the following changes (Stephen)
-Update the sc7180 dtsi file
-Remove resource names and just use index (Stephen)
Quoted 3 lines
Quoted 3 lines
[1]
https://patchwork.freedesktop.org/patch/msgid/[email protected]
---
/snip
Quoted 9 lines
Quoted 9 lines
drivers/gpu/drm/msm/Makefile +1
-0@@ -109,6 +109,7 @@ msm-$(CONFIG_DRM_MSM_DP)+= dp/dp_aux.o \ dp/dp_ctrl.o \ dp/dp_display.o \ dp/dp_drm.o \ + dp/dp_hdcp.o \
Quoted 8 lines
drivers/gpu/drm/msm/dp/dp_debug.c
Quoted 8 lines
drivers/gpu/drm/msm/Makefile +0
-0dp/dp_hpd.o \ dp/dp_link.o \ dp/dp_panel.o \drivers/gpu/drm/msm/dp/dp_debug.c +0
-0
/snip
Quoted 29 lines
Quoted 29 lines
+static
ssize_tdp_hdcp_key_write(struct file *file, const char__user*ubuf,drivers/gpu/drm/msm/dp/dp_debug.c +27
-0+ size_t len, loff_t *offp) +{ + char *input_buffer; +int ret =0 ; +struct dp_debug_private *debug = file->private_data; +struct drm_device *dev; + + dev = debug->drm_dev; + +if (len != (DRM_HDCP_KSV_LEN +DP_HDCP_NUM_KEYS *DP_HDCP_KEY_LEN )) +return -EINVAL ; + +if (!debug->hdcp) +return -ENOENT ; + + input_buffer =memdup_user_nul (ubuf, len); +if (IS_ERR (input_buffer)) +return PTR_ERR (input_buffer); + + ret =dp_hdcp_ingest_key (debug->hdcp, input_buffer, len); + +kfree (input_buffer); +if (ret <0 ) { +DRM_ERROR ("Could not ingest HDCP key, ret=%d\n" , ret); +return ret; + } +
Quoted 9 lines
drivers/gpu/drm/msm/dp/dp_debug.c static int dp_test_active_open(struct inode *inode, · line 385
Quoted 3 lines
drivers/gpu/drm/msm/dp/dp_debug.c +3
-0+ *offp += len; +return len; +}It seems like the HDCP keys written using debugfs, just for my understanding,
are you storing this in some secure partition and the usermode reads from it and writes them here?
We have not sorted out the userspace side of HDCP enablement yet, so it remains to be seen whether the keys will be injected via debugfs/firmware file/property.
/snip
Quoted 29 lines
drivers/gpu/drm/msm/dp/dp_debug.c
Quoted 10 lines
drivers/gpu/drm/msm/dp/dp_debug.c +10
-0+static int dp_connector_atomic_check (struct drm_connector *connector, +struct drm_atomic_state *state) +{ +struct drm_connector_state *conn_state; +struct dp_connector_state *dp_state; + + conn_state =drm_atomic_get_new_connector_state (state, connector); + dp_state =to_dp_connector_state (conn_state); + + dp_state->hdcp_transition =drm_hdcp_atomic_check (connector, state);I have a general question related to the transition flag and overall tying the HDCP
enable and authentication to the commit.
So lets say there is a case where the driver needs to disable HDCP. It could be due
to link integrity failure OR some other error condition which usermode is not aware of.
In that case, we will set thishdcp_transitionto true but in the next commit we will
actually do the authentication. What if usermode doesnt issue a new frame? This question arises because currently the link intergrity check is done using SW polling
in the previous patchset. But as I had commented there, this occurs in HW for us.
I dont see that isr itself in this patchset. So wanted to understand if thats part of this
approach to still tie it with commit.
Quoted 4 lines
So if we go with the HW polling based approach which is the preferred method, we need to
untie this from the commit.
In the case of error, the worker will detect it and try to re-authenticate. If the re-authentication is successful, userspace will continue to be unaware and everything will keep working. If re-authentication is unsuccessful, the worker will update the property value and issue a uevent to userspace. So HDCP enablement is only tied to commits when the property value is changing as a result of userspace.
Regarding SW vs HW link checks, I don't think there's any difference in efficacy between them. If HW can be relied on to issue an interrupt in failure cases, a follow-up set allowing for this seems like a great idea.
Quoted 3 lines
drivers/gpu/drm/msm/dp/dp_debug.c
Quoted 3 lines
drivers/gpu/drm/msm/dp/dp_debug.c +3
-0+ +return 0 ; +}
/snip
Quoted 25 lines
Quoted 25 lines
drivers/gpu/drm/msm/dp/dp_debug.c +25
-0+static int dp_hdcp_load_keys (struct drm_connector *connector) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +struct dp_hdcp_key *key; +int i, ret =0 ; + +mutex_lock (&hdcp->key_lock); + + key = hdcp->key; + +if (!key->valid) { + ret = -ENOENT ; + goto out; + } + +dp_hdcp_write_dp (hdcp,DP_HDCP_SW_LOWER_AKSV , key->ksv.words[0 ]); +dp_hdcp_write_dp (hdcp,DP_HDCP_SW_UPPER_AKSV , key->ksv.words[1 ]); + +for (i =0 ; i <DP_HDCP_NUM_KEYS ; i++) { +dp_hdcp_write_hdcp (hdcp,DP_HDCP_KEY_LSB (i), + key->keys[i].words[0 ]); +dp_hdcp_write_hdcp (hdcp,DP_HDCP_KEY_MSB (i), + key->keys[i].words[1 ]); + } +
Quoted 9 lines
drivers/gpu/drm/msm/dp/dp_debug.c
Quoted 1 line
drivers/gpu/drm/msm/dp/dp_debug.c +1
-0+dp_hdcp_write_hdcp (hdcp,DP_HDCP_KEY_VALID ,DP_HDCP_SW_KEY_VALID );I think all of these are TZ_*** registers. So the separation of
write_hdcp()Vswrite_hdcp_tz()
is not very clear to me.
Maybe change the write APIs to something likedp_hdcp_write_hdcp_tz()for the first address space
anddp_hdcp_write_hdcp_tz_hlos()for the other one?
Will do in v3, thank you for the suggestion.
Quoted 56 lines
Quoted 56 lines
drivers/gpu/drm/msm/dp/dp_debug.c +12
-0+wmb (); + +dp_hdcp_write_dp (hdcp,DP_HDCP_ENTROPY_CTRL0 ,get_random_u32 ()); +dp_hdcp_write_dp (hdcp,DP_HDCP_ENTROPY_CTRL1 ,get_random_u32 ()); +wmb (); + +out: +mutex_unlock (&hdcp->key_lock); +return ret; +} + +static int dp_hdcp_hdcp2_capable(struct drm_connector *connector,bool *capable)
drivers/gpu/drm/msm/dp/dp_debug.c +16
-0+{ + *capable = false; +return 0 ; +} + +static int dp_hdcp_hdcp1_read_an_aksv (struct drm_connector *connector, +u32 *an,u32 *aksv) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +bool keys_valid; +int ret; +u32 val; + +dp_hdcp_write_dp (hdcp,DP_HDCP_CTRL ,1 ); + + ret = read_poll_timeout(dp_hdcp_are_keys_valid, keys_valid,
keys_valid,drivers/gpu/drm/msm/dp/dp_debug.c +11
-0+ 20 * 1000, 10 * 1000, false, connector); +if (ret) { +drm_err (hdcp->dev,"HDCP keys invalid %d\n" , ret); +return ret; + } + +/* Clear AInfo */ +dp_hdcp_write_dp (hdcp,DP_HDCP_RCVPORT_DATA4 ,0 ); + + aksv[0 ] =dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA3 ); + aksv[1] = GENMASK(7, 0) & dp_hdcp_read_dp(hdcp,
DP_HDCP_RCVPORT_DATA4);drivers/gpu/drm/msm/dp/dp_debug.c +14
-0+ + ret =read_poll_timeout (dp_hdcp_read_dp, val, + (val &DP_HDCP_AN_READY_MASK ) ==DP_HDCP_AN_READY_MASK , +100 ,10 *1000 , false, hdcp,DP_HDCP_STATUS ); +if (ret) { +drm_err (hdcp->dev,"AN failed to become ready %x/%d\n" , val, ret); +return ret; + } + +/* +* Get An from hardware, for unknown reasons we need to read the reg +* twice to get valid data. +*/ +dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA5 );
Quoted 8 lines
drivers/gpu/drm/msm/dp/dp_debug.c
Quoted 4 lines
drivers/gpu/drm/msm/dp/dp_debug.c +4
-0+ an[0 ] =dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA5 ); + +dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA6 ); + an[1 ] =dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA6 );Yes its true, but we also have a 1 microsec delay between the first and second one.
So I would certainly preserve that.
Will do in v3, thank you for the suggestion.
Quoted 20 lines
Quoted 20 lines
drivers/gpu/drm/msm/dp/dp_debug.c +5
-0+ +return 0 ; +} + +static int dp_hdcp_hdcp1_store_receiver_info(struct drm_connector*connector,
drivers/gpu/drm/msm/dp/dp_debug.c +13
-0+ u32 *ksv, u32 status, u8 bcaps, + bool is_repeater) +{ + struct dp_hdcp *hdcp = dp_display_connector_to_hdcp(connector); +u32 val; + +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA0 , + ksv[0 ]); +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA1 , + ksv[1 ]); + + val = ((status &GENMASK (15 ,0 )) <<8 ) | (bcaps &GENMASK (7 ,0 )); +
Quoted 8 lines
Quoted 3 lines
drivers/gpu/drm/msm/dp/dp_debug.c +1
-0+ dp_hdcp_write_tz(hdcp, HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA12,val);
+Cant this entire API be skipped for non-repeater cases from the hdcp lib layer?
You can write the bcaps to this earlier and write the bstatus only if its a repeater.
Could you expand on the benefits of this?
Quoted 3 lines
drivers/gpu/drm/msm/dp/dp_debug.c
Quoted 3 lines
drivers/gpu/drm/msm/dp/dp_debug.c +2
-0+return 0 ; +}
/snip
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Re: [Freedreno] [PATCH v2 13/13] drm/msm: Implement HDCP 1.x using the new drm HDCP helpers
Quoted 131 lines · Sean Paul
Quoted 19 lines · On Tue, Sep 21, 2021 at 07:25:41PM -0700, [email protected] wrote:
Quoted 16 lines · Sean Paul
From: Sean Paul <[email protected]>
This patch adds HDCP 1.x support to msm DP connectors using the new HDCP helpers.
Cc Stephen Boyd <[email protected]>Signed-off-by Sean Paul <[email protected]>Link:
https://patchwork.freedesktop.org/patch/msgid/[email protected]
#v1Changes in v2:
-Squash [1] into this patch with the following changes (Stephen)
-Update the sc7180 dtsi file
-Remove resource names and just use index (Stephen)Quoted 3 lines
Quoted 3 lines
[1]
https://patchwork.freedesktop.org/patch/msgid/[email protected]
---/snip
Quoted 9 lines
Quoted 9 lines
drivers/gpu/drm/msm/Makefile +1
-0@@ -109,6 +109,7 @@ msm-$(CONFIG_DRM_MSM_DP)+= dp/dp_aux.o \ dp/dp_ctrl.o \ dp/dp_display.o \ dp/dp_drm.o \ + dp/dp_hdcp.o \Quoted 8 lines
drivers/gpu/drm/msm/dp/dp_debug.c
Quoted 8 lines
drivers/gpu/drm/msm/Makefile +0
-0dp/dp_hpd.o \ dp/dp_link.o \ dp/dp_panel.o \drivers/gpu/drm/msm/dp/dp_debug.c +0
-0/snip
Quoted 29 lines
Quoted 29 lines
+static
ssize_tdp_hdcp_key_write(struct file *file, const char__user*ubuf,drivers/gpu/drm/msm/dp/dp_debug.c +27
-0+ size_t len, loff_t *offp) +{ + char *input_buffer; +int ret =0 ; +struct dp_debug_private *debug = file->private_data; +struct drm_device *dev; + + dev = debug->drm_dev; + +if (len != (DRM_HDCP_KSV_LEN +DP_HDCP_NUM_KEYS *DP_HDCP_KEY_LEN )) +return -EINVAL ; + +if (!debug->hdcp) +return -ENOENT ; + + input_buffer =memdup_user_nul (ubuf, len); +if (IS_ERR (input_buffer)) +return PTR_ERR (input_buffer); + + ret =dp_hdcp_ingest_key (debug->hdcp, input_buffer, len); + +kfree (input_buffer); +if (ret <0 ) { +DRM_ERROR ("Could not ingest HDCP key, ret=%d\n" , ret); +return ret; + } +Quoted 9 lines
drivers/gpu/drm/msm/dp/dp_debug.c static int dp_test_active_open(struct inode *inode, · line 385
Quoted 3 lines
drivers/gpu/drm/msm/dp/dp_debug.c +3
-0+ *offp += len; +return len; +}It seems like the HDCP keys written using debugfs, just for my understanding,
are you storing this in some secure partition and the usermode reads from it and writes them here?We have not sorted out the userspace side of HDCP enablement yet, so it remains to be seen whether the keys will be injected via debugfs/firmware file/property.
/snip
Quoted 29 lines
drivers/gpu/drm/msm/dp/dp_debug.c
Quoted 10 lines
drivers/gpu/drm/msm/dp/dp_debug.c +10
-0+static int dp_connector_atomic_check (struct drm_connector *connector, +struct drm_atomic_state *state) +{ +struct drm_connector_state *conn_state; +struct dp_connector_state *dp_state; + + conn_state =drm_atomic_get_new_connector_state (state, connector); + dp_state =to_dp_connector_state (conn_state); + + dp_state->hdcp_transition =drm_hdcp_atomic_check (connector, state);I have a general question related to the transition flag and overall tying the HDCP
enable and authentication to the commit.
So lets say there is a case where the driver needs to disable HDCP. It could be due
to link integrity failure OR some other error condition which usermode is not aware of.
In that case, we will set thishdcp_transitionto true but in the next commit we will
actually do the authentication. What if usermode doesnt issue a new frame? This question arises because currently the link intergrity check is done using SW polling
in the previous patchset. But as I had commented there, this occurs in HW for us.
I dont see that isr itself in this patchset. So wanted to understand if thats part of this
approach to still tie it with commit.Quoted 4 lines
So if we go with the HW polling based approach which is the preferred method, we need to
untie this from the commit.In the case of error, the worker will detect it and try to re-authenticate. If the re-authentication is successful, userspace will continue to be unaware and everything will keep working. If re-authentication is unsuccessful, the worker will update the property value and issue a uevent to userspace. So HDCP enablement is only tied to commits when the property value is changing as a result of userspace.
Quoted 4 lines
Regarding SW vs HW link checks, I don't think there's any difference in efficacy between them. If HW can be relied on to issue an interrupt in failure cases, a follow-up set allowing for this seems like a great idea.
Thanks for the explanation. Yes, from our experience it has been pretty reliable to issue signal integrity failures. We already had the isr based approach downstream and would prefer to keep it that way based on our experience of it firing reliably. We can still keep the SW polling code but it should come into effect only if HW polling is not supported / preferred.
Quoted 139 lines
Quoted 3 lines
drivers/gpu/drm/msm/dp/dp_debug.c
Quoted 3 lines
drivers/gpu/drm/msm/dp/dp_debug.c +3
-0+ +return 0 ; +}/snip
Quoted 25 lines
Quoted 25 lines
drivers/gpu/drm/msm/dp/dp_debug.c +25
-0+static int dp_hdcp_load_keys (struct drm_connector *connector) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +struct dp_hdcp_key *key; +int i, ret =0 ; + +mutex_lock (&hdcp->key_lock); + + key = hdcp->key; + +if (!key->valid) { + ret = -ENOENT ; + goto out; + } + +dp_hdcp_write_dp (hdcp,DP_HDCP_SW_LOWER_AKSV , key->ksv.words[0 ]); +dp_hdcp_write_dp (hdcp,DP_HDCP_SW_UPPER_AKSV , key->ksv.words[1 ]); + +for (i =0 ; i <DP_HDCP_NUM_KEYS ; i++) { +dp_hdcp_write_hdcp (hdcp,DP_HDCP_KEY_LSB (i), + key->keys[i].words[0 ]); +dp_hdcp_write_hdcp (hdcp,DP_HDCP_KEY_MSB (i), + key->keys[i].words[1 ]); + } +Quoted 9 lines
drivers/gpu/drm/msm/dp/dp_debug.c
Quoted 1 line
drivers/gpu/drm/msm/dp/dp_debug.c +1
-0+dp_hdcp_write_hdcp (hdcp,DP_HDCP_KEY_VALID ,DP_HDCP_SW_KEY_VALID );I think all of these are TZ_*** registers. So the separation of
write_hdcp()Vswrite_hdcp_tz()
is not very clear to me.
Maybe change the write APIs to something likedp_hdcp_write_hdcp_tz()for the first address space
anddp_hdcp_write_hdcp_tz_hlos()for the other one?Will do in v3, thank you for the suggestion.
Quoted 56 lines
Quoted 56 lines
drivers/gpu/drm/msm/dp/dp_debug.c +12
-0+wmb (); + +dp_hdcp_write_dp (hdcp,DP_HDCP_ENTROPY_CTRL0 ,get_random_u32 ()); +dp_hdcp_write_dp (hdcp,DP_HDCP_ENTROPY_CTRL1 ,get_random_u32 ()); +wmb (); + +out: +mutex_unlock (&hdcp->key_lock); +return ret; +} + +static int dp_hdcp_hdcp2_capable(struct drm_connector *connector,bool *capable)
drivers/gpu/drm/msm/dp/dp_debug.c +16
-0+{ + *capable = false; +return 0 ; +} + +static int dp_hdcp_hdcp1_read_an_aksv (struct drm_connector *connector, +u32 *an,u32 *aksv) +{ +struct dp_hdcp *hdcp =dp_display_connector_to_hdcp (connector); +bool keys_valid; +int ret; +u32 val; + +dp_hdcp_write_dp (hdcp,DP_HDCP_CTRL ,1 ); + + ret = read_poll_timeout(dp_hdcp_are_keys_valid, keys_valid,
keys_valid,drivers/gpu/drm/msm/dp/dp_debug.c +11
-0+ 20 * 1000, 10 * 1000, false, connector); +if (ret) { +drm_err (hdcp->dev,"HDCP keys invalid %d\n" , ret); +return ret; + } + +/* Clear AInfo */ +dp_hdcp_write_dp (hdcp,DP_HDCP_RCVPORT_DATA4 ,0 ); + + aksv[0 ] =dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA3 ); + aksv[1] = GENMASK(7, 0) & dp_hdcp_read_dp(hdcp,
DP_HDCP_RCVPORT_DATA4);drivers/gpu/drm/msm/dp/dp_debug.c +14
-0+ + ret =read_poll_timeout (dp_hdcp_read_dp, val, + (val &DP_HDCP_AN_READY_MASK ) ==DP_HDCP_AN_READY_MASK , +100 ,10 *1000 , false, hdcp,DP_HDCP_STATUS ); +if (ret) { +drm_err (hdcp->dev,"AN failed to become ready %x/%d\n" , val, ret); +return ret; + } + +/* +* Get An from hardware, for unknown reasons we need to read the reg +* twice to get valid data. +*/ +dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA5 );Quoted 8 lines
drivers/gpu/drm/msm/dp/dp_debug.c
Quoted 4 lines
drivers/gpu/drm/msm/dp/dp_debug.c +4
-0+ an[0 ] =dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA5 ); + +dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA6 ); + an[1 ] =dp_hdcp_read_dp (hdcp,DP_HDCP_RCVPORT_DATA6 );Yes its true, but we also have a 1 microsec delay between the first and second one.
So I would certainly preserve that.Will do in v3, thank you for the suggestion.
Quoted 20 lines
Quoted 20 lines
drivers/gpu/drm/msm/dp/dp_debug.c +5
-0+ +return 0 ; +} + +static int dp_hdcp_hdcp1_store_receiver_info(struct drm_connector*connector,
drivers/gpu/drm/msm/dp/dp_debug.c +13
-0+ u32 *ksv, u32 status, u8 bcaps, + bool is_repeater) +{ + struct dp_hdcp *hdcp = dp_display_connector_to_hdcp(connector); +u32 val; + +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA0 , + ksv[0 ]); +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA1 , + ksv[1 ]); + + val = ((status &GENMASK (15 ,0 )) <<8 ) | (bcaps &GENMASK (7 ,0 )); +Quoted 8 lines
Quoted 3 lines
drivers/gpu/drm/msm/dp/dp_debug.c +1
-0+ dp_hdcp_write_tz(hdcp, HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA12,val);
+Cant this entire API be skipped for non-repeater cases from the hdcp lib layer?
You can write the bcaps to this earlier and write the bstatus only if its a repeater.
Quoted 1 line
Could you expand on the benefits of this?
We can avoid the call coming into the vendor driver hook itself as it need not be called for non-repeater cases. So something like this can be done in the HDCP lib?
if ( repeater && ops->hdcp1_store_receiver_info )
ops->hdcp1_store_receiver_info(....);
Quoted 6 lines
Quoted 4 lines
drivers/gpu/drm/msm/dp/dp_debug.c
Quoted 4 lines
drivers/gpu/drm/msm/dp/dp_debug.c +2
-0+return 0 ; +}/snip
Sean Paul
reviewerRe: [Freedreno] [PATCH v2 13/13] drm/msm: Implement HDCP 1.x using the new drm HDCP helpers
Quoted 153 lines · On Tue, Sep 28, 2021 at 02:35:09PM -0700, [email protected] wrote:
Quoted 145 lines · Sean Paul
Quoted 19 lines · On Tue, Sep 21, 2021 at 07:25:41PM -0700, [email protected] wrote:
Quoted 16 lines · Sean Paul
From: Sean Paul <[email protected]>
This patch adds HDCP 1.x support to msm DP connectors using the new HDCP helpers.
Cc Stephen Boyd <[email protected]>Signed-off-by Sean Paul <[email protected]>Link:
https://patchwork.freedesktop.org/patch/msgid/[email protected]
#v1Changes in v2:
-Squash [1] into this patch with the following changes (Stephen)
-Update the sc7180 dtsi file
-Remove resource names and just use index (Stephen)Quoted 3 lines
Quoted 3 lines
[1]
https://patchwork.freedesktop.org/patch/msgid/[email protected]
---/snip
Quoted 9 lines
Quoted 9 lines
drivers/gpu/drm/msm/Makefile +1
-0@@ -109,6 +109,7 @@ msm-$(CONFIG_DRM_MSM_DP)+= dp/dp_aux.o \ dp/dp_ctrl.o \ dp/dp_display.o \ dp/dp_drm.o \ + dp/dp_hdcp.o \Quoted 8 lines
drivers/gpu/drm/msm/dp/dp_debug.c
Quoted 8 lines
drivers/gpu/drm/msm/Makefile +0
-0dp/dp_hpd.o \ dp/dp_link.o \ dp/dp_panel.o \drivers/gpu/drm/msm/dp/dp_debug.c +0
-0/snip
Quoted 30 lines
Quoted 30 lines
+static
ssize_tdp_hdcp_key_write(struct file *file, const char__user*ubuf,drivers/gpu/drm/msm/dp/dp_debug.c +28
-0+ size_t len, loff_t *offp) +{ + char *input_buffer; +int ret =0 ; +struct dp_debug_private *debug = file->private_data; +struct drm_device *dev; + + dev = debug->drm_dev; + +if (len != (DRM_HDCP_KSV_LEN +DP_HDCP_NUM_KEYS *DP_HDCP_KEY_LEN )) +return -EINVAL ; + +if (!debug->hdcp) +return -ENOENT ; + + input_buffer =memdup_user_nul (ubuf, len); +if (IS_ERR (input_buffer)) +return PTR_ERR (input_buffer); + + ret =dp_hdcp_ingest_key (debug->hdcp, input_buffer, len); + +kfree (input_buffer); +if (ret <0 ) { +DRM_ERROR ("Could not ingest HDCP key, ret=%d\n" , ret); +return ret; + } + + *offp += len;Quoted 9 lines
drivers/gpu/drm/msm/dp/dp_debug.c static int dp_test_active_open(struct inode *inode, · line 385
Quoted 2 lines
drivers/gpu/drm/msm/dp/dp_debug.c +2
-0+return len; +}It seems like the HDCP keys written using debugfs, just for my understanding,
are you storing this in some secure partition and the usermode reads from it
and writes them here?We have not sorted out the userspace side of HDCP enablement yet, so it remains
to be seen whether the keys will be injected via debugfs/firmware file/property./snip
Quoted 36 lines
drivers/gpu/drm/msm/dp/dp_debug.c
Quoted 10 lines
drivers/gpu/drm/msm/dp/dp_debug.c +10
-0+static int dp_connector_atomic_check (struct drm_connector *connector, +struct drm_atomic_state *state) +{ +struct drm_connector_state *conn_state; +struct dp_connector_state *dp_state; + + conn_state =drm_atomic_get_new_connector_state (state, connector); + dp_state =to_dp_connector_state (conn_state); + + dp_state->hdcp_transition =drm_hdcp_atomic_check (connector, state);I have a general question related to the transition flag and overall tying
the HDCP
enable and authentication to the commit.
So lets say there is a case where the driver needs to disable HDCP. It could
be due
to link integrity failure OR some other error condition which usermode is
not aware of.
In that case, we will set thishdcp_transitionto true but in the next commit we will
actually do the authentication. What if usermode doesnt issue a new frame?
This question arises because currently the link intergrity check is done
using SW polling
in the previous patchset. But as I had commented there, this occurs in HW
for us.
I dont see that isr itself in this patchset. So wanted to understand if
thats part of this
approach to still tie it with commit.Quoted 4 lines
So if we go with the HW polling based approach which is the preferred method, we need to
untie this from the commit.In the case of error, the worker will detect it and try to re-authenticate. If
the re-authentication is successful, userspace will continue to be unaware and
everything will keep working. If re-authentication is unsuccessful, the worker
will update the property value and issue a uevent to userspace. So HDCP enablement is only tied to commits when the property value is changing as a
result of userspace.Quoted 6 lines
Regarding SW vs HW link checks, I don't think there's any difference in efficacy
between them. If HW can be relied on to issue an interrupt in failure cases, a
follow-up set allowing for this seems like a great idea.
Quoted 9 lines
Thanks for the explanation. Yes, from our experience it has been pretty reliable to
issue signal integrity failures. We already had the isr based approach downstream
and would prefer to keep it that way based on our experience of it firing reliably.
We can still keep the SW polling code but it should come into effect only if HW polling
is not supported / preferred.
Ok, understood. Unfortunately I don't have access to a testing rig which could exercise the interrupt. Do you think you could post a follow-on patch to implement this?
Quoted 7 lines
Quoted 7 lines
Quoted 4 lines
drivers/gpu/drm/msm/dp/dp_debug.c
Quoted 4 lines
drivers/gpu/drm/msm/dp/dp_debug.c +3
-0+ +return 0 ; +}/snip
/snip
Quoted 26 lines
Quoted 26 lines
Quoted 25 lines
Quoted 16 lines
+static int dp_hdcp_hdcp1_store_receiver_info(struct
drm_connector*connector,drivers/gpu/drm/msm/dp/dp_debug.c +14
-0+ u32 *ksv, u32 status, u8 bcaps, + bool is_repeater) +{ + struct dp_hdcp *hdcp = dp_display_connector_to_hdcp(connector); +u32 val; + +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA0 , + ksv[0 ]); +dp_hdcp_write_tz (hdcp,HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA1 , + ksv[1 ]); + + val = ((status &GENMASK (15 ,0 )) <<8 ) | (bcaps &GENMASK (7 ,0 )); + + dp_hdcp_write_tz(hdcp, HDCP_SEC_DP_TZ_HV_HLOS_HDCP_RCVPORT_DATA12,Quoted 2 lines
val);
+Cant this entire API be skipped for non-repeater cases from the hdcp lib
layer?
You can write the bcaps to this earlier and write the bstatus only if its a
repeater.
Quoted 9 lines
Quoted 1 line
Could you expand on the benefits of this?
We can avoid the call coming into the vendor driver hook itself as it need not be called
for non-repeater cases. So something like this can be done in the HDCP lib?if ( repeater &&
ops->hdcp1_store_receiver_info)ops->hdcp1_store_receiver_info(....);
Unfortunately this would break Intel's implementation.
Quoted 6 lines
Quoted 6 lines
Quoted 4 lines
drivers/gpu/drm/msm/dp/dp_debug.c
Quoted 4 lines
drivers/gpu/drm/msm/dp/dp_debug.c +2
-0+return 0 ; +}/snip
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Patchwork
CI[Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/hdcp: Pull HDCP auth/exchange/check into helpers
In reply to Sean Paul== Series Details ==
== Series Details ==
Series: drm/hdcp: Pull HDCP auth/exchange/check into helpers
URL : https://patchwork.freedesktop.org/series/94712/
State : failure
== Summary ==
CALL scripts/checksyscalls.sh
CALL scripts/atomic/check-atomics.sh
DESCEND objtool
CHK include/generated/compile.h
LD [M] drivers/gpu/drm/i915/i915.o
HDRTEST drivers/gpu/drm/i915/display/intel_hdcp.h
In file included from <command-line>:./drivers/gpu/drm/i915/display/intel_hdcp.h:30:15: error: ‘struct drm_atomic_state’ declared inside parameter list will not be visible outside of this definition or declaration [-Werror]
struct drm_atomic_state *state);
^~~~~~~~~~~~~~~~cc1: all warnings being treated as errorsdrivers/gpu/drm/i915/Makefile:324: recipe for target 'drivers/gpu/drm/i915/display/intel_hdcp.hdrtest' failed make[4]: *** [drivers/gpu/drm/i915/display/intel_hdcp.hdrtest] Error 1 scripts/Makefile.build:540: recipe for target 'drivers/gpu/drm/i915' failed
make[3]: *** [drivers/gpu/drm/i915] Error 2scripts/Makefile.build:540: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2scripts/Makefile.build:540: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:1868: recipe for target 'drivers' failed
make: *** [drivers] Error 2
Jani Nikula
maintainerRe: [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/hdcp: Pull HDCP auth/exchange/check into helpers
Quoted 16 lines · Patchwork
== Series Details ==
Series: drm/hdcp: Pull HDCP auth/exchange/check into helpers
URL : https://patchwork.freedesktop.org/series/94712/
State : failure== Summary ==
CALL
scripts/checksyscalls.sh
CALLscripts/atomic/check-atomics.sh
DESCEND objtool
CHKinclude/generated/compile.h
LD [M]drivers/gpu/drm/i915/i915.o
HDRTESTdrivers/gpu/drm/i915/display/intel_hdcp.h
In file included from <command-line>:./drivers/gpu/drm/i915/display/intel_hdcp.h:30:15: error: ‘struct drm_atomic_state’ declared inside parameter list will not be visible outside of this definition or declaration [-Werror]
Quoted 2 lines
struct drm_atomic_state *state);
^~~~~~~~~~~~~~~~Please use CONFIG_DRM_I915_WERROR=y when developing i915, and fix the fallout. In this case, you'll need to add a forward declaration for struct drm_atomic_state. (Preferred over including headers from headers.)
Thanks,
Jani.
Quoted 13 lines
cc1: all warnings being treated as errors
drivers/gpu/drm/i915/Makefile:324: recipe for target 'drivers/gpu/drm/i915/display/intel_hdcp.hdrtest' failed make[4]: *** [drivers/gpu/drm/i915/display/intel_hdcp.hdrtest] Error 1scripts/Makefile.build:540: recipe for target 'drivers/gpu/drm/i915' failed
make[3]: *** [drivers/gpu/drm/i915] Error 2scripts/Makefile.build:540: recipe for target 'drivers/gpu/drm' failed
make[2]: *** [drivers/gpu/drm] Error 2scripts/Makefile.build:540: recipe for target 'drivers/gpu' failed
make[1]: *** [drivers/gpu] Error 2
Makefile:1868: recipe for target 'drivers' failed
make: *** [drivers] Error 2
Signature · 1 line
Jani Nikula, Intel Open Source Graphics Center
Quoted 10 lines · Sean Paul
From: Sean Paul <[email protected]>
Hello again,
This is the second version of the HDCP helper patchset. See version 1
here: https://patchwork.freedesktop.org/series/94623/In this second version, I've fixed up the oopsies exposed by 0-day and yamllint and incorporated early review feedback from the dt/dts reviews.
Please take a look,
I'll try to ping folks to get someone to review the i915 parts, but the general idea of moving common HDCP code from i915 to drm is, I hope obviously,
Quoted 51 lines
Sean
Sean Paul (13):
drm/hdcp: Adddrm_hdcp_atomic_check()
drm/hdcp: Avoid changing crtc state in hdcp atomic check drm/hdcp: Update property value on content type and user changes drm/hdcp: Expand HDCP helper library for enable/disable/check drm/i915/hdcp: Consolidate HDCP setup/state cache drm/i915/hdcp: Retainhdcp_capablereturn codes drm/i915/hdcp: Use HDCP helpers for i915 drm/msm/dpu_kms: Re-order dpu includes
drm/msm/dpu: Remove useless checks indpu_encoderdrm/msm/dpu: Removeencoder->enable()hack drm/msm/dp: Re-orderdp_audio_putindeinit_sub_modules
dt-bindings: msm/dp: Add bindings for HDCP registers drm/msm: Implement HDCP 1.x using the new drm HDCP helpers.../bindings/display/msm/dp-controller.yaml | 7 +- arch/arm64/boot/dts/qcom/sc7180.dtsi | 4 +- drivers/gpu/drm/drm_hdcp.c | 1197 ++++++++++++++++- drivers/gpu/drm/i915/display/intel_atomic.c | 7 +- drivers/gpu/drm/i915/display/intel_ddi.c | 29 +- .../drm/i915/display/intel_display_debugfs.c | 11 +- .../drm/i915/display/intel_display_types.h | 58 +- drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 345 ++--- drivers/gpu/drm/i915/display/intel_dp_mst.c | 17 +- drivers/gpu/drm/i915/display/intel_hdcp.c | 1011 +++----------- drivers/gpu/drm/i915/display/intel_hdcp.h | 35 +- drivers/gpu/drm/i915/display/intel_hdmi.c | 256 ++-- drivers/gpu/drm/msm/Makefile | 1 + drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 17 +- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 30 +- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 2 - drivers/gpu/drm/msm/disp/dpu1/dpu_trace.h | 4 - drivers/gpu/drm/msm/dp/dp_debug.c | 49 +- drivers/gpu/drm/msm/dp/dp_debug.h | 6 +- drivers/gpu/drm/msm/dp/dp_display.c | 47 +- drivers/gpu/drm/msm/dp/dp_display.h | 5 + drivers/gpu/drm/msm/dp/dp_drm.c | 68 +- drivers/gpu/drm/msm/dp/dp_drm.h | 5 + drivers/gpu/drm/msm/dp/dp_hdcp.c | 433 ++++++ drivers/gpu/drm/msm/dp/dp_hdcp.h | 27 + drivers/gpu/drm/msm/dp/dp_parser.c | 22 +- drivers/gpu/drm/msm/dp/dp_parser.h | 4 + drivers/gpu/drm/msm/dp/dp_reg.h | 44 +- drivers/gpu/drm/msm/msm_atomic.c | 15 + include/drm/drm_hdcp.h | 194 +++ 30 files changed, 2561 insertions(+), 1389 deletions(-) create mode 100644 drivers/gpu/drm/msm/dp/dp_hdcp.c create mode 100644 drivers/gpu/drm/msm/dp/dp_hdcp.h
Signature · 1 line
Jani Nikula, Intel Open Source Graphics Center
Hi Sean
Quoted 6 lines · Sean Paul
From: Sean Paul <[email protected]>
Hello again,
This is the second version of the HDCP helper patchset. See version 1
here: https://patchwork.freedesktop.org/series/94623/
Quoted 6 lines
In this second version, I've fixed up the oopsies exposed by 0-day and yamllint and incorporated early review feedback from the dt/dts reviews.
Please take a look,
Sean
One question overall on the series:
1) Regarding validation, did you run any secure video to check the transitions?
2) Is running HDCP 1x compliance also part of the validation efforts?
Thanks
Abhinav
Quoted 49 lines
Sean Paul (13):
drm/hdcp: Adddrm_hdcp_atomic_check()
drm/hdcp: Avoid changing crtc state in hdcp atomic check drm/hdcp: Update property value on content type and user changes drm/hdcp: Expand HDCP helper library for enable/disable/check drm/i915/hdcp: Consolidate HDCP setup/state cache drm/i915/hdcp: Retainhdcp_capablereturn codes drm/i915/hdcp: Use HDCP helpers for i915 drm/msm/dpu_kms: Re-order dpu includes
drm/msm/dpu: Remove useless checks indpu_encoderdrm/msm/dpu: Removeencoder->enable()hack drm/msm/dp: Re-orderdp_audio_putindeinit_sub_modules
dt-bindings: msm/dp: Add bindings for HDCP registers drm/msm: Implement HDCP 1.x using the new drm HDCP helpers.../bindings/display/msm/dp-controller.yaml | 7 +- arch/arm64/boot/dts/qcom/sc7180.dtsi | 4 +- drivers/gpu/drm/drm_hdcp.c | 1197 ++++++++++++++++- drivers/gpu/drm/i915/display/intel_atomic.c | 7 +- drivers/gpu/drm/i915/display/intel_ddi.c | 29 +- .../drm/i915/display/intel_display_debugfs.c | 11 +- .../drm/i915/display/intel_display_types.h | 58 +- drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 345 ++--- drivers/gpu/drm/i915/display/intel_dp_mst.c | 17 +- drivers/gpu/drm/i915/display/intel_hdcp.c | 1011 +++----------- drivers/gpu/drm/i915/display/intel_hdcp.h | 35 +- drivers/gpu/drm/i915/display/intel_hdmi.c | 256 ++-- drivers/gpu/drm/msm/Makefile | 1 + drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 17 +- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 30 +- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 2 - drivers/gpu/drm/msm/disp/dpu1/dpu_trace.h | 4 - drivers/gpu/drm/msm/dp/dp_debug.c | 49 +- drivers/gpu/drm/msm/dp/dp_debug.h | 6 +- drivers/gpu/drm/msm/dp/dp_display.c | 47 +- drivers/gpu/drm/msm/dp/dp_display.h | 5 + drivers/gpu/drm/msm/dp/dp_drm.c | 68 +- drivers/gpu/drm/msm/dp/dp_drm.h | 5 + drivers/gpu/drm/msm/dp/dp_hdcp.c | 433 ++++++ drivers/gpu/drm/msm/dp/dp_hdcp.h | 27 + drivers/gpu/drm/msm/dp/dp_parser.c | 22 +- drivers/gpu/drm/msm/dp/dp_parser.h | 4 + drivers/gpu/drm/msm/dp/dp_reg.h | 44 +- drivers/gpu/drm/msm/msm_atomic.c | 15 + include/drm/drm_hdcp.h | 194 +++ 30 files changed, 2561 insertions(+), 1389 deletions(-) create mode 100644 drivers/gpu/drm/msm/dp/dp_hdcp.c create mode 100644 drivers/gpu/drm/msm/dp/dp_hdcp.h
Sean Paul
reviewerQuoted 12 lines · On Tue, Sep 21, 2021 at 07:30:29PM -0700, [email protected] wrote:
Hi Sean
Quoted 9 lines · Sean Paul
From: Sean Paul <[email protected]>
Hello again,
This is the second version of the HDCP helper patchset. See version 1
here: https://patchwork.freedesktop.org/series/94623/In this second version, I've fixed up the oopsies exposed by 0-day and yamllint and incorporated early review feedback from the dt/dts reviews.
Quoted 8 lines
Quoted 3 lines
Please take a look,
Sean
One question overall on the series:
1) Regarding validation, did you run any secure video to check the transitions?
Yep, the transitions look good, no visual artifacts. Unplug/replug/suspend/resume all seem to be behaving as expected.
Quoted 1 line
2) Is running HDCP 1x compliance also part of the validation efforts?
If Qualcomm has the ability to run validation, I'd be very keen to get some help in that regard.
Sean
Quoted 54 lines
Thanks
Abhinav
Quoted 49 lines
Sean Paul (13):
drm/hdcp: Adddrm_hdcp_atomic_check()
drm/hdcp: Avoid changing crtc state in hdcp atomic check drm/hdcp: Update property value on content type and user changes drm/hdcp: Expand HDCP helper library for enable/disable/check drm/i915/hdcp: Consolidate HDCP setup/state cache drm/i915/hdcp: Retainhdcp_capablereturn codes drm/i915/hdcp: Use HDCP helpers for i915 drm/msm/dpu_kms: Re-order dpu includes
drm/msm/dpu: Remove useless checks indpu_encoderdrm/msm/dpu: Removeencoder->enable()hack drm/msm/dp: Re-orderdp_audio_putindeinit_sub_modules
dt-bindings: msm/dp: Add bindings for HDCP registers drm/msm: Implement HDCP 1.x using the new drm HDCP helpers.../bindings/display/msm/dp-controller.yaml | 7 +- arch/arm64/boot/dts/qcom/sc7180.dtsi | 4 +- drivers/gpu/drm/drm_hdcp.c | 1197 ++++++++++++++++- drivers/gpu/drm/i915/display/intel_atomic.c | 7 +- drivers/gpu/drm/i915/display/intel_ddi.c | 29 +- .../drm/i915/display/intel_display_debugfs.c | 11 +- .../drm/i915/display/intel_display_types.h | 58 +- drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 345 ++--- drivers/gpu/drm/i915/display/intel_dp_mst.c | 17 +- drivers/gpu/drm/i915/display/intel_hdcp.c | 1011 +++----------- drivers/gpu/drm/i915/display/intel_hdcp.h | 35 +- drivers/gpu/drm/i915/display/intel_hdmi.c | 256 ++-- drivers/gpu/drm/msm/Makefile | 1 + drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 17 +- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 30 +- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 2 - drivers/gpu/drm/msm/disp/dpu1/dpu_trace.h | 4 - drivers/gpu/drm/msm/dp/dp_debug.c | 49 +- drivers/gpu/drm/msm/dp/dp_debug.h | 6 +- drivers/gpu/drm/msm/dp/dp_display.c | 47 +- drivers/gpu/drm/msm/dp/dp_display.h | 5 + drivers/gpu/drm/msm/dp/dp_drm.c | 68 +- drivers/gpu/drm/msm/dp/dp_drm.h | 5 + drivers/gpu/drm/msm/dp/dp_hdcp.c | 433 ++++++ drivers/gpu/drm/msm/dp/dp_hdcp.h | 27 + drivers/gpu/drm/msm/dp/dp_parser.c | 22 +- drivers/gpu/drm/msm/dp/dp_parser.h | 4 + drivers/gpu/drm/msm/dp/dp_reg.h | 44 +- drivers/gpu/drm/msm/msm_atomic.c | 15 + include/drm/drm_hdcp.h | 194 +++ 30 files changed, 2561 insertions(+), 1389 deletions(-) create mode 100644 drivers/gpu/drm/msm/dp/dp_hdcp.c create mode 100644 drivers/gpu/drm/msm/dp/dp_hdcp.h
Signature · 1 line
Sean Paul, Software Engineer, Google / Chromium OS
Quoted 22 lines · Sean Paul
Quoted 12 lines · On Tue, Sep 21, 2021 at 07:30:29PM -0700, [email protected] wrote:
Hi Sean
Quoted 9 lines · Sean Paul
From: Sean Paul <[email protected]>
Hello again,
This is the second version of the HDCP helper patchset. See version 1
here: https://patchwork.freedesktop.org/series/94623/In this second version, I've fixed up the oopsies exposed by 0-day and yamllint and incorporated early review feedback from the dt/dts reviews.
Quoted 8 lines
Quoted 3 lines
Please take a look,
Sean
One question overall on the series:
1) Regarding validation, did you run any secure video to check the transitions?
Quoted 7 lines
Yep, the transitions look good, no visual artifacts. Unplug/replug/suspend/resume all seem to be behaving as expected.
Quoted 1 line
2) Is running HDCP 1x compliance also part of the validation efforts?
If Qualcomm has the ability to run validation, I'd be very keen to get some help in that regard.
Thanks for letting us know. To assist with (2) we will have to work with you on some logistics. Will sync up on IRC further on how to go about this.
Quoted 57 lines
Sean
Quoted 54 lines
Thanks
Abhinav
Quoted 49 lines
Sean Paul (13):
drm/hdcp: Adddrm_hdcp_atomic_check()
drm/hdcp: Avoid changing crtc state in hdcp atomic check drm/hdcp: Update property value on content type and user changes drm/hdcp: Expand HDCP helper library for enable/disable/check drm/i915/hdcp: Consolidate HDCP setup/state cache drm/i915/hdcp: Retainhdcp_capablereturn codes drm/i915/hdcp: Use HDCP helpers for i915 drm/msm/dpu_kms: Re-order dpu includes
drm/msm/dpu: Remove useless checks indpu_encoderdrm/msm/dpu: Removeencoder->enable()hack drm/msm/dp: Re-orderdp_audio_putindeinit_sub_modules
dt-bindings: msm/dp: Add bindings for HDCP registers drm/msm: Implement HDCP 1.x using the new drm HDCP helpers.../bindings/display/msm/dp-controller.yaml | 7 +- arch/arm64/boot/dts/qcom/sc7180.dtsi | 4 +- drivers/gpu/drm/drm_hdcp.c | 1197 ++++++++++++++++- drivers/gpu/drm/i915/display/intel_atomic.c | 7 +- drivers/gpu/drm/i915/display/intel_ddi.c | 29 +- .../drm/i915/display/intel_display_debugfs.c | 11 +- .../drm/i915/display/intel_display_types.h | 58 +- drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 345 ++--- drivers/gpu/drm/i915/display/intel_dp_mst.c | 17 +- drivers/gpu/drm/i915/display/intel_hdcp.c | 1011 +++----------- drivers/gpu/drm/i915/display/intel_hdcp.h | 35 +- drivers/gpu/drm/i915/display/intel_hdmi.c | 256 ++-- drivers/gpu/drm/msm/Makefile | 1 + drivers/gpu/drm/msm/disp/dpu1/dpu_encoder.c | 17 +- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.c | 30 +- drivers/gpu/drm/msm/disp/dpu1/dpu_kms.h | 2 - drivers/gpu/drm/msm/disp/dpu1/dpu_trace.h | 4 - drivers/gpu/drm/msm/dp/dp_debug.c | 49 +- drivers/gpu/drm/msm/dp/dp_debug.h | 6 +- drivers/gpu/drm/msm/dp/dp_display.c | 47 +- drivers/gpu/drm/msm/dp/dp_display.h | 5 + drivers/gpu/drm/msm/dp/dp_drm.c | 68 +- drivers/gpu/drm/msm/dp/dp_drm.h | 5 + drivers/gpu/drm/msm/dp/dp_hdcp.c | 433 ++++++ drivers/gpu/drm/msm/dp/dp_hdcp.h | 27 + drivers/gpu/drm/msm/dp/dp_parser.c | 22 +- drivers/gpu/drm/msm/dp/dp_parser.h | 4 + drivers/gpu/drm/msm/dp/dp_reg.h | 44 +- drivers/gpu/drm/msm/msm_atomic.c | 15 + include/drm/drm_hdcp.h | 194 +++ 30 files changed, 2561 insertions(+), 1389 deletions(-) create mode 100644 drivers/gpu/drm/msm/dp/dp_hdcp.c create mode 100644 drivers/gpu/drm/msm/dp/dp_hdcp.h