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, Suraj Kandpal <suraj.kandpal@intel.com>
Subject: Re: [PATCH 0/2] Changes in hdcp2_stream_encryption
Date: Mon, 23 Jun 2025 11:49:57 +0300 [thread overview]
Message-ID: <eb5ca1f98c7ceee3f3e504a9f6c2ac2bf0557b73@intel.com> (raw)
In-Reply-To: <20250619113340.3379200-1-suraj.kandpal@intel.com>
On Thu, 19 Jun 2025, Suraj Kandpal <suraj.kandpal@intel.com> wrote:
> Contains changes in hdcp2_stream_encryption where we remove the
> intel_de_read from the WARN_ON function also we move to using
> HDCP2_STREAM_STATUS for our WARN_ON for platforms PTL and above.
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
>
> Signed-off-by: Suraj Kandpal <suraj.kandpal@intel.com>
>
> Suraj Kandpal (2):
> drm/i915/hdcp: Do not use inline intel_de_read
> drm/i915/hdcp: Use HDCP2_STREAM_STATUS instead of HDCP2_AUTH_STREAM
>
> drivers/gpu/drm/i915/display/intel_dp_hdcp.c | 22 +++++++++++++++----
> .../gpu/drm/i915/display/intel_hdcp_regs.h | 4 ++--
> 2 files changed, 20 insertions(+), 6 deletions(-)
--
Jani Nikula, Intel
next prev parent reply other threads:[~2025-06-23 8:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-19 11:33 [PATCH 0/2] Changes in hdcp2_stream_encryption Suraj Kandpal
2025-06-19 11:33 ` [PATCH 1/2] drm/i915/hdcp: Do not use inline intel_de_read Suraj Kandpal
2025-06-19 11:33 ` [PATCH 2/2] drm/i915/hdcp: Use HDCP2_STREAM_STATUS instead of HDCP2_AUTH_STREAM Suraj Kandpal
2025-06-19 13:41 ` ✓ i915.CI.BAT: success for Changes in hdcp2_stream_encryption (rev2) Patchwork
2025-06-20 1:14 ` ✓ i915.CI.Full: " Patchwork
2025-06-23 8:49 ` Jani Nikula [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-19 10:28 [PATCH 0/2] Changes in hdcp2_stream_encryption 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=eb5ca1f98c7ceee3f3e504a9f6c2ac2bf0557b73@intel.com \
--to=jani.nikula@intel.com \
--cc=ankit.k.nautiyal@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox