From: Jani Nikula <jani.nikula@intel.com>
To: Suraj Kandpal <suraj.kandpal@intel.com>,
intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: ankit.k.nautiyal@intel.com, dnyaneshwar.bhadane@intel.com,
Suraj Kandpal <suraj.kandpal@intel.com>
Subject: Re: [PATCH] drm/i915/hdcp: Use correct function to check if encoder is HDMI
Date: Mon, 20 Jan 2025 12:51:43 +0200 [thread overview]
Message-ID: <87bjw1rc5c.fsf@intel.com> (raw)
In-Reply-To: <20250117041247.1084381-1-suraj.kandpal@intel.com>
On Fri, 17 Jan 2025, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> Use intel_encoder_is_hdmi function which was recently introduced to
> see if encoder is HDMI or not.
>
> --v2
> -Add Fixes tag [Jani]
>
> Fixes: 6a3691ca4799 ("drm/i915/hdcp: Disable HDCP Line Rekeying for HDCP2.2 on HDMI")
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_hdcp.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_hdcp.c b/drivers/gpu/drm/i915/display/intel_hdcp.c
> index 7464b44c8bb3..91d5629cd9f9 100644
> --- a/drivers/gpu/drm/i915/display/intel_hdcp.c
> +++ b/drivers/gpu/drm/i915/display/intel_hdcp.c
> @@ -41,7 +41,7 @@ intel_hdcp_adjust_hdcp_line_rekeying(struct intel_encoder *encoder,
> u32 rekey_bit = 0;
>
> /* Here we assume HDMI is in TMDS mode of operation */
> - if (encoder->type != INTEL_OUTPUT_HDMI)
> + if (!intel_encoder_is_hdmi(encoder))
> return;
>
> if (DISPLAY_VER(display) >= 30) {
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-01-20 10:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-17 4:12 [PATCH] drm/i915/hdcp: Use correct function to check if encoder is HDMI Suraj Kandpal
2025-01-17 4:56 ` ✓ i915.CI.BAT: success for drm/i915/hdcp: Use correct function to check if encoder is HDMI (rev3) Patchwork
2025-01-17 5:03 ` ✓ CI.Patch_applied: " Patchwork
2025-01-17 5:04 ` ✓ CI.checkpatch: " Patchwork
2025-01-17 5:05 ` ✓ CI.KUnit: " Patchwork
2025-01-17 5:23 ` ✓ CI.Build: " Patchwork
2025-01-17 5:26 ` ✓ CI.Hooks: " Patchwork
2025-01-17 5:28 ` ✗ CI.checksparse: warning " Patchwork
2025-01-17 5:56 ` ✓ Xe.CI.BAT: success " Patchwork
2025-01-18 2:38 ` ✗ i915.CI.Full: failure " Patchwork
2025-01-21 4:51 ` Kandpal, Suraj
2025-01-20 10:51 ` Jani Nikula [this message]
2025-01-21 4:52 ` [PATCH] drm/i915/hdcp: Use correct function to check if encoder is HDMI Kandpal, Suraj
-- strict thread matches above, loose matches on Subject: below --
2025-01-16 5:20 Suraj Kandpal
2025-01-16 8:06 ` Jani Nikula
2025-01-16 8:08 ` Jani Nikula
2025-01-16 9:25 ` Kandpal, Suraj
2025-01-16 5:19 Suraj Kandpal
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=87bjw1rc5c.fsf@intel.com \
--to=jani.nikula@intel.com \
--cc=ankit.k.nautiyal@intel.com \
--cc=dnyaneshwar.bhadane@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--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.