From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Sean Paul <sean@poorly.run>
Cc: Maxime Ripard <mripard@kernel.org>,
jani.nikula@intel.com, markyacoub@chromium.org,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
swboyd@chromium.org, David Airlie <airlied@linux.ie>,
Sean Paul <seanpaul@chromium.org>,
abhinavk@codeaurora.org, Thomas Zimmermann <tzimmermann@suse.de>,
bjorn.andersson@linaro.org, freedreno@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v5 01/10] drm/hdcp: Add drm_hdcp_atomic_check()
Date: Tue, 12 Apr 2022 09:15:18 -0400 [thread overview]
Message-ID: <YlV7ZhnsOPKoOpes@intel.com> (raw)
In-Reply-To: <20220411204741.1074308-2-sean@poorly.run>
On Mon, Apr 11, 2022 at 08:47:30PM +0000, Sean Paul wrote:
> From: Sean Paul <seanpaul@chromium.org>
>
> 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.
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> Acked-by: Jani Nikula <jani.nikula@intel.com>
> Acked-by: Jani Nikula <jani.nikula@intel.com>
> Reviewed-by: Abhinav Kumar <abhinavk@codeaurora.org>
> Signed-off-by: Sean Paul <seanpaul@chromium.org>
> Link: https://patchwork.freedesktop.org/patch/msgid/20210913175747.47456-2-sean@poorly.run #v1
> Link: https://patchwork.freedesktop.org/patch/msgid/20210915203834.1439-2-sean@poorly.run #v2
> Link: https://patchwork.freedesktop.org/patch/msgid/20211001151145.55916-2-sean@poorly.run #v3
> Link: https://patchwork.freedesktop.org/patch/msgid/20211105030434.2828845-2-sean@poorly.run #v4
>
> Changes in v2:
> -None
> Changes in v3:
> -None
> Changes in v4:
> -None
> Changes in v5:
> -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(-)
>
> diff --git a/drivers/gpu/drm/drm_hdcp.c b/drivers/gpu/drm/drm_hdcp.c
> index ca9b8f697202..522326b03e66 100644
> --- a/drivers/gpu/drm/drm_hdcp.c
> +++ b/drivers/gpu/drm/drm_hdcp.c
> @@ -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);
> diff --git a/drivers/gpu/drm/i915/display/intel_atomic.c b/drivers/gpu/drm/i915/display/intel_atomic.c
> index 40da7910f845..b301a4d1017e 100644
> --- a/drivers/gpu/drm/i915/display/intel_atomic.c
> +++ b/drivers/gpu/drm/i915/display/intel_atomic.c
> @@ -32,6 +32,7 @@
> #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 "i915_drv.h"
> @@ -40,7 +41,6 @@
> #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"
>
> @@ -124,7 +124,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;
> diff --git a/drivers/gpu/drm/i915/display/intel_hdcp.c b/drivers/gpu/drm/i915/display/intel_hdcp.c
> index 4de4c174a987..861c550b5bd6 100644
> --- a/drivers/gpu/drm/i915/display/intel_hdcp.c
> +++ b/drivers/gpu/drm/i915/display/intel_hdcp.c
> @@ -2501,53 +2501,6 @@ void intel_hdcp_cleanup(struct intel_connector *connector)
> mutex_unlock(&hdcp->mutex);
> }
>
> -void intel_hdcp_atomic_check(struct drm_connector *connector,
> - struct drm_connector_state *old_state,
> - struct drm_connector_state *new_state)
> -{
> - u64 old_cp = old_state->content_protection;
> - u64 new_cp = new_state->content_protection;
> - struct drm_crtc_state *crtc_state;
> -
> - if (!new_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_cp == DRM_MODE_CONTENT_PROTECTION_ENABLED)
> - new_state->content_protection =
> - DRM_MODE_CONTENT_PROTECTION_DESIRED;
> - return;
> - }
> -
> - crtc_state = drm_atomic_get_new_crtc_state(new_state->state,
> - new_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(crtc_state) &&
> - (old_cp == DRM_MODE_CONTENT_PROTECTION_ENABLED &&
> - new_cp != DRM_MODE_CONTENT_PROTECTION_UNDESIRED))
> - new_state->content_protection =
> - DRM_MODE_CONTENT_PROTECTION_DESIRED;
> -
> - /*
> - * Nothing to do if the state didn't change, or HDCP was activated since
> - * the last commit. And also no change in hdcp content type.
> - */
> - if (old_cp == new_cp ||
> - (old_cp == DRM_MODE_CONTENT_PROTECTION_DESIRED &&
> - new_cp == DRM_MODE_CONTENT_PROTECTION_ENABLED)) {
> - if (old_state->hdcp_content_type ==
> - new_state->hdcp_content_type)
> - return;
> - }
> -
> - crtc_state->mode_changed = true;
> -}
> -
> /* Handles the CP_IRQ raised from the DP HDCP sink */
> void intel_hdcp_handle_cp_irq(struct intel_connector *connector)
> {
> diff --git a/drivers/gpu/drm/i915/display/intel_hdcp.h b/drivers/gpu/drm/i915/display/intel_hdcp.h
> index 8f53b0c7fe5c..7c5fd84a7b65 100644
> --- a/drivers/gpu/drm/i915/display/intel_hdcp.h
> +++ b/drivers/gpu/drm/i915/display/intel_hdcp.h
> @@ -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);
> diff --git a/include/drm/drm_hdcp.h b/include/drm/drm_hdcp.h
> index 0b1111e3228e..d49977a042e1 100644
> --- a/include/drm/drm_hdcp.h
> +++ b/include/drm/drm_hdcp.h
> @@ -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
> --
> Sean Paul, Software Engineer, Google / Chromium OS
>
next prev parent reply other threads:[~2022-04-12 13:15 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 20:47 [Intel-gfx] [PATCH v5 00/10] drm/hdcp: Pull HDCP auth/exchange/check into helpers Sean Paul
2022-04-11 20:47 ` [Intel-gfx] [PATCH v5 01/10] drm/hdcp: Add drm_hdcp_atomic_check() Sean Paul
2022-04-12 13:15 ` Rodrigo Vivi [this message]
2022-04-11 20:47 ` [Intel-gfx] [PATCH v5 02/10] drm/hdcp: Avoid changing crtc state in hdcp atomic check Sean Paul
2022-04-12 13:20 ` Rodrigo Vivi
2022-04-11 20:47 ` [Intel-gfx] [PATCH v5 03/10] drm/hdcp: Update property value on content type and user changes Sean Paul
2022-04-12 13:25 ` Rodrigo Vivi
2022-04-14 15:58 ` Sean Paul
2022-04-14 21:44 ` Rodrigo Vivi
2022-04-11 20:47 ` [Intel-gfx] [PATCH v5 04/10] drm/hdcp: Expand HDCP helper library for enable/disable/check Sean Paul
2022-04-12 1:52 ` kernel test robot
2022-04-11 20:47 ` [Intel-gfx] [PATCH v5 05/10] drm/i915/hdcp: Consolidate HDCP setup/state cache Sean Paul
2022-04-12 13:37 ` Rodrigo Vivi
2022-04-11 20:47 ` [Intel-gfx] [PATCH v5 06/10] drm/i915/hdcp: Retain hdcp_capable return codes Sean Paul
2022-04-12 13:36 ` Rodrigo Vivi
2022-04-11 20:47 ` [Intel-gfx] [PATCH v5 07/10] drm/i915/hdcp: Use HDCP helpers for i915 Sean Paul
2022-04-11 20:47 ` [Intel-gfx] [PATCH v5 08/10] dt-bindings: msm/dp: Add bindings for HDCP registers Sean Paul
2022-04-11 20:47 ` [Intel-gfx] [PATCH v5 09/10] arm64: dts: qcom: sc7180: Add support for HDCP in dp-controller Sean Paul
2022-04-20 3:10 ` Bjorn Andersson
2022-04-11 20:47 ` [Intel-gfx] [PATCH v5 10/10] drm/msm: Implement HDCP 1.x using the new drm HDCP helpers Sean Paul
2022-04-12 0:30 ` kernel test robot
2022-04-12 13:41 ` [Intel-gfx] [PATCH v5 00/10] drm/hdcp: Pull HDCP auth/exchange/check into helpers Rodrigo Vivi
2022-04-14 16:00 ` Sean Paul
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YlV7ZhnsOPKoOpes@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=abhinavk@codeaurora.org \
--cc=airlied@linux.ie \
--cc=bjorn.andersson@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=markyacoub@chromium.org \
--cc=mripard@kernel.org \
--cc=sean@poorly.run \
--cc=seanpaul@chromium.org \
--cc=swboyd@chromium.org \
--cc=tzimmermann@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox