From: Jani Nikula <jani.nikula@linux.intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: matthew.d.roper@intel.com, Suraj Kandpal <suraj.kandpal@intel.com>
Subject: Re: [PATCH] drm/i915/hdcp: Handle HDCP Line Rekeying for HDCP 1.4
Date: Wed, 06 Nov 2024 12:03:34 +0200 [thread overview]
Message-ID: <87zfmcfzm1.fsf@intel.com> (raw)
In-Reply-To: <20241106093840.847932-1-suraj.kandpal@intel.com>
On Wed, 06 Nov 2024, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> TRANS_DDI_FUNC_CTL asks us to disable hdcp line rekeying when not in
> hdcp 2.2 and we are not using an hdmi transcoder and it need to be
> enabled when we are using an HDMI transcoder to enable HDCP 1.4.
> We use intel_de_rmw cycles to update TRANS_DDI_FUNC_CTL register so
> we cannot depend on the value being 0 by default everytime which calls
> for seprate handling of HDCP 1.4 case.
>
> --v2
> -Use the exising function and modify it based on a bool rather than
> have a different function [Matt]
>
> Bspec: 69964, 50493, 50054
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_hdcp.c | 41 ++++++++++++++---------
> 1 file changed, 26 insertions(+), 15 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_hdcp.c b/drivers/gpu/drm/i915/display/intel_hdcp.c
> index 4e937fbba4d2..0530cf855463 100644
> --- a/drivers/gpu/drm/i915/display/intel_hdcp.c
> +++ b/drivers/gpu/drm/i915/display/intel_hdcp.c
> @@ -32,27 +32,36 @@
> #define HDCP2_LC_RETRY_CNT 3
>
> static void
> -intel_hdcp_disable_hdcp_line_rekeying(struct intel_encoder *encoder,
> - struct intel_hdcp *hdcp)
> +intel_hdcp_adjust_hdcp_line_rekeying(struct intel_encoder *encoder,
> + struct intel_hdcp *hdcp,
> + bool enable)
> {
> struct intel_display *display = to_intel_display(encoder);
> + i915_reg_t *rekey_reg;
> + u32 rekey_bit;
>
> /* Here we assume HDMI is in TMDS mode of operation */
> if (encoder->type != INTEL_OUTPUT_HDMI)
> return;
>
> - if (DISPLAY_VER(display) >= 30)
> - intel_de_rmw(display,
> - TRANS_DDI_FUNC_CTL(display, hdcp->cpu_transcoder),
> - 0, XE3_TRANS_DDI_HDCP_LINE_REKEY_DISABLE);
> - else if (IS_DISPLAY_VERx100_STEP(display, 1401, STEP_B0, STEP_FOREVER) ||
> - IS_DISPLAY_VERx100_STEP(display, 2000, STEP_B0, STEP_FOREVER))
> - intel_de_rmw(display,
> - TRANS_DDI_FUNC_CTL(display, hdcp->cpu_transcoder),
> - 0, TRANS_DDI_HDCP_LINE_REKEY_DISABLE);
> - else if (IS_DISPLAY_VERx100_STEP(display, 1400, STEP_D0, STEP_FOREVER))
> - intel_de_rmw(display, MTL_CHICKEN_TRANS(hdcp->cpu_transcoder),
> - 0, HDCP_LINE_REKEY_DISABLE);
> + rekey_reg = kzalloc(sizeof(*rekey_reg), GFP_KERNEL);
No, there's absolutely no reason to allocate this.
BR,
Jani.
> + if (!rekey_reg)
> + return;
> +
> + if (DISPLAY_VER(display) >= 30) {
> + *rekey_reg = TRANS_DDI_FUNC_CTL(display, hdcp->cpu_transcoder);
> + rekey_bit = XE3_TRANS_DDI_HDCP_LINE_REKEY_DISABLE;
> + } else if (IS_DISPLAY_VERx100_STEP(display, 1401, STEP_B0, STEP_FOREVER) ||
> + IS_DISPLAY_VERx100_STEP(display, 2000, STEP_B0, STEP_FOREVER)) {
> + *rekey_reg = TRANS_DDI_FUNC_CTL(display, hdcp->cpu_transcoder);
> + rekey_bit = TRANS_DDI_HDCP_LINE_REKEY_DISABLE;
> + } else if (IS_DISPLAY_VERx100_STEP(display, 1400, STEP_D0, STEP_FOREVER)) {
> + *rekey_reg = MTL_CHICKEN_TRANS(hdcp->cpu_transcoder);
> + rekey_bit = HDCP_LINE_REKEY_DISABLE;
> + }
> +
> + intel_de_rmw(display, *rekey_reg, rekey_bit, enable ? 0 : rekey_bit);
> + kfree(rekey_reg);
> }
>
> static int intel_conn_to_vcpi(struct intel_atomic_state *state,
> @@ -1049,6 +1058,8 @@ static int intel_hdcp1_enable(struct intel_connector *connector)
> return ret;
> }
>
> + intel_hdcp_adjust_hdcp_line_rekeying(connector->encoder, hdcp, true);
> +
> /* Incase of authentication failures, HDCP spec expects reauth. */
> for (i = 0; i < tries; i++) {
> ret = intel_hdcp_auth(connector);
> @@ -2062,7 +2073,7 @@ static int _intel_hdcp2_enable(struct intel_atomic_state *state,
> connector->base.base.id, connector->base.name,
> hdcp->content_type);
>
> - intel_hdcp_disable_hdcp_line_rekeying(connector->encoder, hdcp);
> + intel_hdcp_adjust_hdcp_line_rekeying(connector->encoder, hdcp, false);
>
> ret = hdcp2_authenticate_and_encrypt(state, connector);
> if (ret) {
--
Jani Nikula, Intel
next prev parent reply other threads:[~2024-11-06 10:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-06 9:38 [PATCH] drm/i915/hdcp: Handle HDCP Line Rekeying for HDCP 1.4 Suraj Kandpal
2024-11-06 10:03 ` Jani Nikula [this message]
2024-11-06 10:25 ` ✓ CI.Patch_applied: success for " Patchwork
2024-11-06 10:25 ` ✓ CI.checkpatch: " Patchwork
2024-11-06 10:26 ` ✓ CI.KUnit: " Patchwork
2024-11-06 10:32 ` ✓ Fi.CI.BAT: " Patchwork
2024-11-06 10:38 ` ✓ CI.Build: " Patchwork
2024-11-06 10:40 ` ✓ CI.Hooks: " Patchwork
2024-11-06 10:42 ` ✗ CI.checksparse: warning " Patchwork
2024-11-06 11:02 ` ✓ CI.BAT: success " Patchwork
2024-11-06 13:20 ` ✓ Fi.CI.IGT: " Patchwork
2024-11-07 12:29 ` ✗ CI.FULL: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-11-06 12:51 [PATCH] " Suraj Kandpal
2024-11-06 16:29 ` Jani Nikula
2024-11-06 16:53 ` Kandpal, Suraj
2024-11-06 17:40 Suraj Kandpal
2024-11-07 1:54 ` kernel test robot
2024-11-07 2:28 Suraj Kandpal
2024-11-07 21:44 ` Matt Roper
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=87zfmcfzm1.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=suraj.kandpal@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is 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.