From: Uma Shankar <uma.shankar@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: dibin.moolakadan.subrahmanian@intel.com,
Uma Shankar <uma.shankar@intel.com>
Subject: [v4 0/4] drm/i915/display: Enable AS SDP Skip Frames
Date: Tue, 1 Sep 2026 03:04:17 +0530 [thread overview]
Message-ID: <20260831213421.1804635-1-uma.shankar@intel.com> (raw)
When Panel Replay is active the transcoder timing generator runs at the
panel's maximum refresh rate, but content is often presented at a lower
rate. In that case the Adaptive-Sync SDP (AS SDP) only needs to reach the
panel often enough to satisfy its maximum frame time, so transmitting it
on every frame is redundant and shows up as repeated SDPs on the link.
Xe3LPD adds a HW skip-frame counter in PR_ALPM_CTL that lets the source
send a single AS SDP and then suppress it for a programmed number of
frames. Program this counter so that one AS SDP is followed by
(max_vrefresh / flip_rate - 1) idle frames, matching the effective
content rate and allowing the link to be driven down to as low as 1Hz
when the hardware supports it.
v4:
- Fix Sashiko review comments
v3:
- Add module parameter
- Fix Skip count clearing issue (Dibin)
- Add DC3Co checks and enabling conditions
Uma Shankar (4):
drm/i915/display: Enable periodic AS SDP skip frames
drm/i915/display: Force disable DC3co when AS SDP skip frames is
enabled
drm/i915/display: Reprogram AS SDP skip frames on seamless VRR
transitions
drm/i915/display: Gate periodic AS SDP skip frames behind a module
parameter
drivers/gpu/drm/i915/display/intel_alpm.c | 154 ++++++++++++++++--
drivers/gpu/drm/i915/display/intel_alpm.h | 3 +
drivers/gpu/drm/i915/display/intel_display.c | 18 ++
.../drm/i915/display/intel_display_params.c | 6 +
.../drm/i915/display/intel_display_params.h | 1 +
.../drm/i915/display/intel_display_power.c | 9 +
drivers/gpu/drm/i915/display/intel_psr_regs.h | 2 +
7 files changed, 177 insertions(+), 16 deletions(-)
--
2.50.1
next reply other threads:[~2026-08-31 21:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-31 21:34 Uma Shankar [this message]
2026-08-31 21:20 ` ✗ CI.checkpatch: warning for drm/i915/display: Enable AS SDP Skip Frames (rev5) Patchwork
2026-08-31 21:22 ` ✓ CI.KUnit: success " Patchwork
2026-08-31 21:34 ` [v4 1/4] drm/i915/display: Enable periodic AS SDP skip frames Uma Shankar
2026-09-02 16:15 ` Dibin Moolakadan Subrahmanian
2026-08-31 21:34 ` [v4 2/4] drm/i915/display: Force disable DC3co when AS SDP skip frames is enabled Uma Shankar
2026-09-02 16:29 ` Dibin Moolakadan Subrahmanian
2026-09-03 6:18 ` Naladala, Ramanaidu
2026-08-31 21:34 ` [v4 3/4] drm/i915/display: Reprogram AS SDP skip frames on seamless VRR transitions Uma Shankar
2026-09-02 16:44 ` Dibin Moolakadan Subrahmanian
2026-09-03 6:21 ` Naladala, Ramanaidu
2026-09-03 6:36 ` Naladala, Ramanaidu
2026-08-31 21:34 ` [v4 4/4] drm/i915/display: Gate periodic AS SDP skip frames behind a module parameter Uma Shankar
2026-08-31 22:28 ` sashiko-bot
2026-09-02 18:00 ` Dibin Moolakadan Subrahmanian
2026-09-03 6:37 ` Naladala, Ramanaidu
2026-08-31 22:00 ` ✓ Xe.CI.BAT: success for drm/i915/display: Enable AS SDP Skip Frames (rev5) Patchwork
2026-08-31 23:07 ` ✗ 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=20260831213421.1804635-1-uma.shankar@intel.com \
--to=uma.shankar@intel.com \
--cc=dibin.moolakadan.subrahmanian@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
/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