Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Animesh Manna <animesh.manna@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: jouni.hogander@intel.com, jani.nikula@intel.com,
	jeevan.b@intel.com, Animesh Manna <animesh.manna@intel.com>
Subject: [PATCH v5 0/8] LOBF enablement fix
Date: Mon,  3 Mar 2025 14:05:14 +0530	[thread overview]
Message-ID: <20250303083522.845224-1-animesh.manna@intel.com> (raw)

v1: Initial version.
v2: Addressed review comments from Jani.
v3: Addressed review comments from Jouni.
v4: Addressed review comments received on v3.
v5: Addressed review comments received on v4.

Signed-off-by: Animesh Manna <animesh.manna@intel.com>

Animesh Manna (8):
  drm/i915/lobf: Add lobf enablement in post plane update
  drm/i915/lobf: Disintegrate alpm_disable from psr_disable
  drm/i915/lobf: Add fixed refresh rate check in compute_config()
  drm/i915/lobf: Update lobf if any change in dependent parameters
  drm/i915/lobf: Add debug interface for lobf
  drm/i915/lobf: Check for sink error and disable LOBF
  drm/i915/lobf: Add mutex for alpm update
  drm/i915/lobf: Add debug print for LOBF

 drivers/gpu/drm/i915/display/intel_alpm.c     | 143 +++++++++++++++++-
 drivers/gpu/drm/i915/display/intel_alpm.h     |  11 +-
 drivers/gpu/drm/i915/display/intel_ddi.c      |   3 +
 drivers/gpu/drm/i915/display/intel_display.c  |   3 +
 .../drm/i915/display/intel_display_types.h    |   7 +
 drivers/gpu/drm/i915/display/intel_dp.c       |   5 +-
 drivers/gpu/drm/i915/display/intel_psr.c      |  29 +---
 7 files changed, 170 insertions(+), 31 deletions(-)

-- 
2.29.0


             reply	other threads:[~2025-03-03  8:57 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03  8:35 Animesh Manna [this message]
2025-03-03  8:35 ` [PATCH v5 1/8] drm/i915/lobf: Add lobf enablement in post plane update Animesh Manna
2025-03-03  8:35 ` [PATCH v5 2/8] drm/i915/lobf: Disintegrate alpm_disable from psr_disable Animesh Manna
2025-03-03  8:35 ` [PATCH v5 3/8] drm/i915/lobf: Add fixed refresh rate check in compute_config() Animesh Manna
2025-03-03  8:35 ` [PATCH v5 4/8] drm/i915/lobf: Update lobf if any change in dependent parameters Animesh Manna
2025-03-07 13:32   ` Hogander, Jouni
2025-03-03  8:35 ` [PATCH v5 5/8] drm/i915/lobf: Add debug interface for lobf Animesh Manna
2025-03-07 13:37   ` Hogander, Jouni
2025-03-12 14:58     ` Jani Nikula
2025-03-03  8:35 ` [PATCH v5 6/8] drm/i915/lobf: Check for sink error and disable LOBF Animesh Manna
2025-03-07 14:01   ` Hogander, Jouni
2025-03-03  8:35 ` [PATCH v5 7/8] drm/i915/lobf: Add mutex for alpm update Animesh Manna
2025-03-03  8:35 ` [PATCH v5 8/8] drm/i915/lobf: Add debug print for LOBF Animesh Manna
2025-03-03  9:05 ` ✓ CI.Patch_applied: success for LOBF enablement fix (rev4) Patchwork
2025-03-03  9:06 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-03  9:07 ` ✓ CI.KUnit: success " Patchwork
2025-03-03  9:23 ` ✓ CI.Build: " Patchwork
2025-03-03  9:26 ` ✓ CI.Hooks: " Patchwork
2025-03-03  9:27 ` ✗ CI.checksparse: warning " Patchwork
2025-03-03  9:46 ` ✓ Xe.CI.BAT: success " Patchwork
2025-03-03 10:59 ` ✗ 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=20250303083522.845224-1-animesh.manna@intel.com \
    --to=animesh.manna@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@intel.com \
    --cc=jeevan.b@intel.com \
    --cc=jouni.hogander@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