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 02/10] drm/hdcp: Avoid changing crtc state in hdcp atomic check
Date: Tue, 12 Apr 2022 09:20:18 -0400 [thread overview]
Message-ID: <YlV8ki79h9jYj3Dw@intel.com> (raw)
In-Reply-To: <20220411204741.1074308-3-sean@poorly.run>
On Mon, Apr 11, 2022 at 08:47:31PM +0000, Sean Paul wrote:
> From: Sean Paul <seanpaul@chromium.org>
>
> 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.
>
> Acked-by: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Sean Paul <seanpaul@chromium.org>
> Link: https://patchwork.freedesktop.org/patch/msgid/20210913175747.47456-3-sean@poorly.run #v1
> Link: https://patchwork.freedesktop.org/patch/msgid/20210915203834.1439-3-sean@poorly.run #v2
> Link: https://patchwork.freedesktop.org/patch/msgid/20211001151145.55916-3-sean@poorly.run #v3
> Link: https://patchwork.freedesktop.org/patch/msgid/20211105030434.2828845-3-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 | 33 +++++++++++++++------
> drivers/gpu/drm/i915/display/intel_atomic.c | 5 ++--
> include/drm/drm_hdcp.h | 2 +-
> 3 files changed, 27 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_hdcp.c b/drivers/gpu/drm/drm_hdcp.c
> index 522326b03e66..dd8fa91c51d6 100644
> --- a/drivers/gpu/drm/drm_hdcp.c
> +++ b/drivers/gpu/drm/drm_hdcp.c
> @@ -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;
I'm with the feeling that this chunk should deserve a separated patch.
But the reason looks correct so anyway
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> /*
> * 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);
> diff --git a/drivers/gpu/drm/i915/display/intel_atomic.c b/drivers/gpu/drm/i915/display/intel_atomic.c
> index b301a4d1017e..6d24b3450399 100644
> --- a/drivers/gpu/drm/i915/display/intel_atomic.c
> +++ b/drivers/gpu/drm/i915/display/intel_atomic.c
> @@ -124,8 +124,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;
>
> @@ -142,7 +140,8 @@ int intel_digital_connector_atomic_check(struct drm_connector *conn,
> new_conn_state->base.content_type != old_conn_state->base.content_type ||
> new_conn_state->base.scaling_mode != old_conn_state->base.scaling_mode ||
> new_conn_state->base.privacy_screen_sw_state != old_conn_state->base.privacy_screen_sw_state ||
> - !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;
> diff --git a/include/drm/drm_hdcp.h b/include/drm/drm_hdcp.h
> index d49977a042e1..e6e3d16bc7d3 100644
> --- a/include/drm/drm_hdcp.h
> +++ b/include/drm/drm_hdcp.h
> @@ -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 */
> --
> Sean Paul, Software Engineer, Google / Chromium OS
>
WARNING: multiple messages have this Message-ID (diff)
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Sean Paul <sean@poorly.run>
Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
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: [PATCH v5 02/10] drm/hdcp: Avoid changing crtc state in hdcp atomic check
Date: Tue, 12 Apr 2022 09:20:18 -0400 [thread overview]
Message-ID: <YlV8ki79h9jYj3Dw@intel.com> (raw)
In-Reply-To: <20220411204741.1074308-3-sean@poorly.run>
On Mon, Apr 11, 2022 at 08:47:31PM +0000, Sean Paul wrote:
> From: Sean Paul <seanpaul@chromium.org>
>
> 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.
>
> Acked-by: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Sean Paul <seanpaul@chromium.org>
> Link: https://patchwork.freedesktop.org/patch/msgid/20210913175747.47456-3-sean@poorly.run #v1
> Link: https://patchwork.freedesktop.org/patch/msgid/20210915203834.1439-3-sean@poorly.run #v2
> Link: https://patchwork.freedesktop.org/patch/msgid/20211001151145.55916-3-sean@poorly.run #v3
> Link: https://patchwork.freedesktop.org/patch/msgid/20211105030434.2828845-3-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 | 33 +++++++++++++++------
> drivers/gpu/drm/i915/display/intel_atomic.c | 5 ++--
> include/drm/drm_hdcp.h | 2 +-
> 3 files changed, 27 insertions(+), 13 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_hdcp.c b/drivers/gpu/drm/drm_hdcp.c
> index 522326b03e66..dd8fa91c51d6 100644
> --- a/drivers/gpu/drm/drm_hdcp.c
> +++ b/drivers/gpu/drm/drm_hdcp.c
> @@ -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;
I'm with the feeling that this chunk should deserve a separated patch.
But the reason looks correct so anyway
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
>
> /*
> * 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);
> diff --git a/drivers/gpu/drm/i915/display/intel_atomic.c b/drivers/gpu/drm/i915/display/intel_atomic.c
> index b301a4d1017e..6d24b3450399 100644
> --- a/drivers/gpu/drm/i915/display/intel_atomic.c
> +++ b/drivers/gpu/drm/i915/display/intel_atomic.c
> @@ -124,8 +124,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;
>
> @@ -142,7 +140,8 @@ int intel_digital_connector_atomic_check(struct drm_connector *conn,
> new_conn_state->base.content_type != old_conn_state->base.content_type ||
> new_conn_state->base.scaling_mode != old_conn_state->base.scaling_mode ||
> new_conn_state->base.privacy_screen_sw_state != old_conn_state->base.privacy_screen_sw_state ||
> - !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;
> diff --git a/include/drm/drm_hdcp.h b/include/drm/drm_hdcp.h
> index d49977a042e1..e6e3d16bc7d3 100644
> --- a/include/drm/drm_hdcp.h
> +++ b/include/drm/drm_hdcp.h
> @@ -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 */
> --
> Sean Paul, Software Engineer, Google / Chromium OS
>
next prev parent reply other threads:[~2022-04-12 13:20 UTC|newest]
Thread overview: 53+ 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 ` Sean Paul
2022-04-11 20:47 ` [Intel-gfx] [PATCH v5 01/10] drm/hdcp: Add drm_hdcp_atomic_check() Sean Paul
2022-04-11 20:47 ` Sean Paul
2022-04-12 13:15 ` [Intel-gfx] " Rodrigo Vivi
2022-04-12 13:15 ` Rodrigo Vivi
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-11 20:47 ` Sean Paul
2022-04-12 13:20 ` Rodrigo Vivi [this message]
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-11 20:47 ` Sean Paul
2022-04-12 13:25 ` [Intel-gfx] " Rodrigo Vivi
2022-04-12 13:25 ` Rodrigo Vivi
2022-04-14 15:58 ` [Intel-gfx] " Sean Paul
2022-04-14 15:58 ` Sean Paul
2022-04-14 21:44 ` [Intel-gfx] " Rodrigo Vivi
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-11 20:47 ` Sean Paul
2022-04-12 1:52 ` [Intel-gfx] " kernel test robot
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-11 20:47 ` Sean Paul
2022-04-12 13:37 ` [Intel-gfx] " Rodrigo Vivi
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-11 20:47 ` Sean Paul
2022-04-12 13:36 ` [Intel-gfx] " Rodrigo Vivi
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 ` 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 ` Sean Paul
2022-04-11 20:47 ` 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-11 20:47 ` Sean Paul
2022-04-11 20:47 ` Sean Paul
2022-04-20 3:10 ` [Intel-gfx] " Bjorn Andersson
2022-04-20 3:10 ` Bjorn Andersson
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-11 20:47 ` Sean Paul
2022-04-11 20:47 ` Sean Paul
2022-04-12 0:30 ` [Intel-gfx] " kernel test robot
2022-04-12 0:30 ` kernel test robot
2022-05-11 18:40 ` Dmitry Baryshkov
2022-05-11 18:40 ` Dmitry Baryshkov
2022-04-12 13:41 ` [Intel-gfx] [PATCH v5 00/10] drm/hdcp: Pull HDCP auth/exchange/check into helpers Rodrigo Vivi
2022-04-12 13:41 ` Rodrigo Vivi
2022-04-14 16:00 ` [Intel-gfx] " Sean Paul
2022-04-14 16:00 ` Sean Paul
2022-06-15 12:53 ` [Freedreno] " Dmitry Baryshkov
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=YlV8ki79h9jYj3Dw@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.