intel-xe.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Tvrtko Ursulin <tursulin@igalia.com>
To: Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: "Jani Nikula" <jani.nikula@linux.intel.com>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Tvrtko Ursulin" <tursulin@ursulin.net>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Thomas Zimmermann" <tzimmermann@suse.de>,
	"Maarten Lankhorst" <maarten.lankhorst@linux.intel.com>,
	"Maxime Ripard" <mripard@kernel.org>,
	"Thomas Hellström" <thomas.hellstrom@linux.intel.com>,
	"Oded Gabbay" <ogabbay@kernel.org>,
	"Lucas De Marchi" <lucas.demarchi@intel.com>,
	dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
	intel-xe@lists.freedesktop.org, dim-tools@lists.freedesktop.org
Subject: [PULL] drm-intel-next-fixes
Date: Thu, 21 Nov 2024 08:37:45 +0000	[thread overview]
Message-ID: <Zz7xWbodMn9zZD_C@linux> (raw)


Hi Dave, Sima,

Just one fix for the merge window this week - fixing the HDCP flows on
HDMI connectors.

Regards,

Tvrtko

drm-intel-next-fixes-2024-11-21:
- Fix when the first read and write are retried [hdcp] (Suraj Kandpal)
The following changes since commit a163b895077861598be48c1cf7f4a88413c28b22:

  Merge tag 'drm-xe-next-fixes-2024-11-15' of https://gitlab.freedesktop.org/drm/xe/kernel into drm-next (2024-11-18 13:38:46 +1000)

are available in the Git repository at:

  https://gitlab.freedesktop.org/drm/i915/kernel.git tags/drm-intel-next-fixes-2024-11-21

for you to fetch changes up to 376a33c4a0d8344bb575e1a6eeb748ee4d4675d3:

  drm/i915/hdcp: Fix when the first read and write are retried (2024-11-19 08:11:11 +0000)

----------------------------------------------------------------
- Fix when the first read and write are retried [hdcp] (Suraj Kandpal)

----------------------------------------------------------------
Suraj Kandpal (1):
      drm/i915/hdcp: Fix when the first read and write are retried

 drivers/gpu/drm/i915/display/intel_hdcp.c | 32 +++++++++++++++++++------------
 1 file changed, 20 insertions(+), 12 deletions(-)

             reply	other threads:[~2024-11-21  8:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-21  8:37 Tvrtko Ursulin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-08-05  7:48 [PULL] drm-intel-next-fixes Jani Nikula
2025-06-05  8:35 Joonas Lahtinen
2025-05-28  6:56 Joonas Lahtinen
2025-05-22  6:59 Joonas Lahtinen
2025-05-15  8:27 Joonas Lahtinen
2025-03-25  9:07 Jani Nikula
2024-09-26  7:45 Joonas Lahtinen
2024-09-19  9:49 Joonas Lahtinen
2024-09-12  8:59 Joonas Lahtinen
2024-07-25  7:44 Tvrtko Ursulin
2024-07-18  9:30 Tvrtko Ursulin

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=Zz7xWbodMn9zZD_C@linux \
    --to=tursulin@igalia.com \
    --cc=airlied@gmail.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dim-tools@lists.freedesktop.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=lucas.demarchi@intel.com \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=mripard@kernel.org \
    --cc=ogabbay@kernel.org \
    --cc=rodrigo.vivi@intel.com \
    --cc=thomas.hellstrom@linux.intel.com \
    --cc=tursulin@ursulin.net \
    --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;
as well as URLs for NNTP newsgroup(s).