From: Vinod Govindapillai <vinod.govindapillai@intel.com>
To: intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: vinod.govindapillai@intel.com, ville.syrjala@linux.intel.com
Subject: [PATCH v2 00/11] drm/i915/display: reduce the pm demand peak bw based on display data rate
Date: Mon, 11 May 2026 15:28:05 +0300 [thread overview]
Message-ID: <20260511122816.1235478-1-vinod.govindapillai@intel.com> (raw)
In xe3+, soc can lower the fabric frequency when the display
needs less bandwidth than the minimum GV point.
v1: pmdemand peak bw is updated to 20GB/s is the required data rate
is low and less than 20GB/s even though there are no QGV point
with 20GB/s. Only the peak_ww is changed based on the conditions
v2: At the time of BW info calculations, a new row is inserted with
peakbw as 20GB/s and deratebw also to 20GB/s and the required
pmdemand peakbw is automatically calculated based on the old
logic.
Vinod Govindapillai (11):
drm/i915/wm: clear the plane ddb_y entries on plane disable
drm/i915/pm_demand: introduce HAS_PMDEMAND macro
drm/i915/display: sagv pre/post plane calls to check pmdemand support
drm/i915/bw: Extract icl_init_qgv_info()
drm/i915/bw: sort the qgv points based on the dclk
drm/i915/bw: update the routine to get max dclk from qgv points
drm/i915/bw: update the routine to find the peakbw in MTL
drm/i915/bw: update the tile-y dependency based on the display version
drm/i915/bw: consolidate the debug info of bw/dgv/psf data
drm/i915/bw: extract update_sagv_status()
drm/i915/bw: insert a sw bw info entry to cater low data rate usecases
drivers/gpu/drm/i915/display/intel_bw.c | 215 +++++++++++++-----
.../drm/i915/display/intel_display_device.h | 2 +
.../gpu/drm/i915/display/intel_display_irq.c | 2 +-
.../drm/i915/display/intel_display_power.c | 4 +-
drivers/gpu/drm/i915/display/intel_pmdemand.c | 12 +-
drivers/gpu/drm/i915/display/skl_watermark.c | 8 +-
6 files changed, 178 insertions(+), 65 deletions(-)
--
2.43.0
next reply other threads:[~2026-05-11 12:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 12:28 Vinod Govindapillai [this message]
2026-05-11 12:28 ` [PATCH v2 01/11] drm/i915/wm: clear the plane ddb_y entries on plane disable Vinod Govindapillai
2026-05-11 12:28 ` [PATCH v2 02/11] drm/i915/pm_demand: introduce HAS_PMDEMAND macro Vinod Govindapillai
2026-05-11 12:28 ` [PATCH v2 03/11] drm/i915/display: sagv pre/post plane calls to check pmdemand support Vinod Govindapillai
2026-05-11 12:28 ` [PATCH v2 04/11] drm/i915/bw: Extract icl_init_qgv_info() Vinod Govindapillai
2026-05-11 12:28 ` [PATCH v2 05/11] drm/i915/bw: sort the qgv points based on the dclk Vinod Govindapillai
2026-05-11 12:28 ` [PATCH v2 06/11] drm/i915/bw: update the routine to get max dclk from qgv points Vinod Govindapillai
2026-05-11 12:28 ` [PATCH v2 07/11] drm/i915/bw: update the routine to find the peakbw in MTL Vinod Govindapillai
2026-05-11 12:28 ` [PATCH v2 08/11] drm/i915/bw: update the tile-y dependency based on the display version Vinod Govindapillai
2026-05-11 12:28 ` [PATCH v2 09/11] drm/i915/bw: consolidate the debug info of bw/dgv/psf data Vinod Govindapillai
2026-05-12 11:49 ` Jani Nikula
2026-05-11 12:28 ` [PATCH v2 10/11] drm/i915/bw: extract update_sagv_status() Vinod Govindapillai
2026-05-11 12:28 ` [PATCH v2 11/11] drm/i915/bw: insert a sw bw info entry to cater low data rate usecases Vinod Govindapillai
2026-05-12 11:51 ` Jani Nikula
2026-05-12 12:02 ` Govindapillai, Vinod
2026-05-11 16:28 ` ✓ CI.KUnit: success for drm/i915/display: reduce the pm demand peak bw based on display data rate Patchwork
2026-05-11 17:33 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-11 19:30 ` ✗ 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=20260511122816.1235478-1-vinod.govindapillai@intel.com \
--to=vinod.govindapillai@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).