Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Jani Nikula <jani.nikula@intel.com>
Subject: [PATCH 0/2] drm/i915/dp: Fix 128b/132b modeset issues
Date: Tue, 18 Feb 2025 00:38:26 +0200	[thread overview]
Message-ID: <20250217223828.1166093-1-imre.deak@intel.com> (raw)

This patchset fixes an issue during the error handling of a 128b/132b
mode link training failure and fixes the transcoder function disabling
sequence in 128b/132b SST mode.

Cc: Jani Nikula <jani.nikula@intel.com>

Imre Deak (2):
  drm/i915/dp: Fix error handling during 128b/132b link training
  drm/i915/dp: Fix disabling the transcoder function in 128b/132b mode

 drivers/gpu/drm/i915/display/intel_ddi.c          |  6 ++----
 .../gpu/drm/i915/display/intel_dp_link_training.c | 15 ++++++++++++++-
 2 files changed, 16 insertions(+), 5 deletions(-)

-- 
2.44.2


             reply	other threads:[~2025-02-17 22:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-17 22:38 Imre Deak [this message]
2025-02-17 22:38 ` [PATCH 1/2] drm/i915/dp: Fix error handling during 128b/132b link training Imre Deak
2025-02-18 12:51   ` Jani Nikula
2025-02-18 13:06     ` Imre Deak
2025-02-17 22:38 ` [PATCH 2/2] drm/i915/dp: Fix disabling the transcoder function in 128b/132b mode Imre Deak
2025-02-18 13:03   ` Jani Nikula
2025-02-18 13:15     ` Imre Deak
2025-02-17 22:43 ` ✓ CI.Patch_applied: success for drm/i915/dp: Fix 128b/132b modeset issues Patchwork
2025-02-17 22:43 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-17 22:44 ` ✓ CI.KUnit: success " Patchwork
2025-02-17 23:01 ` ✓ CI.Build: " Patchwork
2025-02-17 23:03 ` ✓ CI.Hooks: " Patchwork
2025-02-17 23:04 ` ✓ CI.checksparse: " Patchwork
2025-02-17 23:24 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-18 16:27 ` ✗ Xe.CI.Full: failure " Patchwork

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=20250217223828.1166093-1-imre.deak@intel.com \
    --to=imre.deak@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@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