From: "Jouni Högander" <jouni.hogander@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: "Jouni Högander" <jouni.hogander@intel.com>
Subject: [PATCH 0/4] ALPM LFPS and silence period calculation
Date: Wed, 13 Aug 2025 10:06:13 +0300 [thread overview]
Message-ID: <20250813070617.480793-1-jouni.hogander@intel.com> (raw)
Currently ALPM LFPS and silence period are hardcoded for different
link rates. This patch set implements calculation for these
parameters.
Also AUXLess wake time is optimized by using actual LFPS cycles and
silence period instead of maximum values.
Jouni Högander (4):
drm/i915/alpm: Calculate silence period
drm/i915/alpm: Add own define for LFPS count
drm/i915/alpm: Replace hardcoded LFPS cycle with proper calculation
drm/i915/alpm: Use actual lfps cycle and silence periods in wake time
drivers/gpu/drm/i915/display/intel_alpm.c | 133 ++++++++++------------
1 file changed, 58 insertions(+), 75 deletions(-)
--
2.43.0
next reply other threads:[~2025-08-13 7:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-13 7:06 Jouni Högander [this message]
2025-08-13 7:06 ` [PATCH 1/4] drm/i915/alpm: Calculate silence period Jouni Högander
2025-08-28 6:39 ` Manna, Animesh
2025-08-13 7:06 ` [PATCH 2/4] drm/i915/alpm: Add own define for LFPS count Jouni Högander
2025-08-28 7:00 ` Manna, Animesh
2025-08-13 7:06 ` [PATCH 3/4] drm/i915/alpm: Replace hardcoded LFPS cycle with proper calculation Jouni Högander
2025-08-28 7:35 ` Manna, Animesh
2025-08-28 9:39 ` Hogander, Jouni
2025-08-13 7:06 ` [PATCH 4/4] drm/i915/alpm: Use actual lfps cycle and silence periods in wake time Jouni Högander
2025-08-28 7:54 ` Manna, Animesh
2025-08-28 9:48 ` Hogander, Jouni
2025-08-13 7:31 ` ✓ CI.KUnit: success for ALPM LFPS and silence period calculation Patchwork
2025-08-13 8:41 ` ✓ Xe.CI.BAT: " Patchwork
2025-08-13 9:38 ` ✗ 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=20250813070617.480793-1-jouni.hogander@intel.com \
--to=jouni.hogander@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;
as well as URLs for NNTP newsgroup(s).