Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Jouni Högander" <jouni.hogander@intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: ville.syrjala@linux.intel.com,
	"Jouni Högander" <jouni.hogander@intel.com>
Subject: [PATCH 0/2] Block DC6 on Vblank enable for Panel Replay
Date: Fri, 13 Sep 2024 10:33:45 +0300	[thread overview]
Message-ID: <20240913073347.3273589-1-jouni.hogander@intel.com> (raw)

We need to block DC6 entry in case of Panel Replay as enabling VBI doesn't
prevent DC6 in case of Panel Replay. This causes problems if user-space is
polling for vblank events.

Jouni Högander (2):
  drm/i915/display: Add block_dc6_needed variable into intel_crtc
  drm/i915/display: Prevent DC6 while vblank is enabled for Panel Replay

 .../gpu/drm/i915/display/intel_display_core.h |  2 +
 .../gpu/drm/i915/display/intel_display_irq.c  | 60 +++++++++++++++++++
 .../gpu/drm/i915/display/intel_display_irq.h  |  3 +
 .../drm/i915/display/intel_display_types.h    |  7 +++
 drivers/gpu/drm/i915/display/intel_psr.c      |  7 +++
 5 files changed, 79 insertions(+)

-- 
2.34.1


             reply	other threads:[~2024-09-13  7:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13  7:33 Jouni Högander [this message]
2024-09-13  7:33 ` [PATCH 1/2] drm/i915/display: Add block_dc6_needed variable into intel_crtc Jouni Högander
2024-09-13 15:03   ` Ville Syrjälä
2024-09-14  1:33   ` kernel test robot
2024-09-14  2:55   ` kernel test robot
2024-09-13  7:33 ` [PATCH 2/2] drm/i915/display: Prevent DC6 while vblank is enabled for Panel Replay Jouni Högander
2024-09-13 14:52 ` ✗ Fi.CI.SPARSE: warning for Block DC6 on Vblank enable " Patchwork
2024-09-13 14:52 ` ✗ Fi.CI.DOCS: " Patchwork
2024-09-13 15:02 ` ✓ Fi.CI.BAT: success " Patchwork
2024-09-14 23:04 ` ✗ Fi.CI.IGT: 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=20240913073347.3273589-1-jouni.hogander@intel.com \
    --to=jouni.hogander@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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