From: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"jani.nikula@linux.intel.com" <jani.nikula@linux.intel.com>
Cc: "ville.syrjala@linux.intel.com" <ville.syrjala@linux.intel.com>
Subject: Re: [PATCH v2 11/11] drm/i915/bw: insert a sw bw info entry to cater low data rate usecases
Date: Tue, 12 May 2026 12:02:53 +0000 [thread overview]
Message-ID: <d87b96028d085d23407514d2f310bc89eba91819.camel@intel.com> (raw)
In-Reply-To: <72b13fe8baa13cd54791b1c4ab9898e4e2c421e2@intel.com>
On Tue, 2026-05-12 at 14:51 +0300, Jani Nikula wrote:
> On Mon, 11 May 2026, Vinod Govindapillai
> <vinod.govindapillai@intel.com> wrote:
> > In xe3+, soc can lower the fabric frequency when the display
> > needs less bandwidth than the minimum GV point. This threshold
> > has been defined as 20GB/s. To enable this,
> >
> > Add a new low bw info point with this peakbw threshold of 20GB/s
> > based on the following conditions:
> > 1. Only for xe3+ versions
> > 2. There is at least one QGV point
> > 3. Number QGV points is less than 8
> > 4. Lowest peak bw across all the QGV point is less than 20 GB/s
> > 5. And the derated bw is in the lowest peak bw qgv point is also
> > less than this threshold of 20GB/s
> >
> > This will make the driver to send this new threshold of 20GB/s
> > as the pmdemand request whenever the bw required for a usecase
> > is less than 20GB/s. The current pcode can handle this lower
> > peakbw value and adjust the fabric frequency accordingly.
> >
> > Bspec: 68880
> > Assisted-by: Copilot:claude-sonnet-4.6
> > Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_bw.c | 54
> > +++++++++++++++++++
> > .../drm/i915/display/intel_display_device.h | 1 +
> > 2 files changed, 55 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_bw.c
> > b/drivers/gpu/drm/i915/display/intel_bw.c
> > index 938c0294c251..747279075e29 100644
> > --- a/drivers/gpu/drm/i915/display/intel_bw.c
> > +++ b/drivers/gpu/drm/i915/display/intel_bw.c
> > @@ -54,6 +54,8 @@ struct intel_qgv_point {
> >
> > #define DEPROGBWPCLIMIT 60
> >
> > +#define PEAK_BW_THRESHOLD 20000
> > +
> > struct intel_psf_gv_point {
> > u8 clk; /* clock in multiples of 16.6666 MHz */
> > };
> > @@ -589,6 +591,50 @@ static int icl_get_bw_info(struct
> > intel_display *display,
> > return 0;
> > }
> >
> > +static bool xe3_check_lower_peakbw(struct intel_display *display,
> > + const struct intel_qgv_info
> > *qi,
> > + int num_channels)
>
> My pet peeve is naming functions with "check". Is it an assert? What
> does it do? What does the return value mean?
>
> BR,
> Jani.
>
hmm.. Intention is that, it should check the conditions for inserting
the low peak bw..
May be xe3_needs_lower_peakbw_point() ?
BR
Vinod
> > +{
> > + unsigned int lowest_peakbw;
> > +
> > + if (!HAS_PEAK_BW_THRESHOLD(display))
> > + return false;
> > +
> > + if (qi->num_points >= I915_NUM_QGV_POINTS) {
> > + drm_warn(display->drm, "Cannot insert lowest QGV
> > point, not enough space\n");
> > + return false;
> > + }
> > +
> > + lowest_peakbw = DIV_ROUND_CLOSEST(qi->points[0].dclk *
> > + qi->channel_width *
> > num_channels, 8);
> > + if (lowest_peakbw <= PEAK_BW_THRESHOLD) {
> > + drm_dbg_kms(display->drm,
> > + "Lowest QGV point has peak BW %u MB/s,
> > no need to insert lower point\n",
> > + lowest_peakbw);
> > + return false;
> > + }
> > +
> > + return true;
> > +}
> > +
> > +static void xe3_insert_lowest_qgv_point(struct intel_display
> > *display,
> > + struct intel_bw_info *bi)
> > +{
> > + if (bi->num_qgv_points >= ARRAY_SIZE(bi->deratedbw))
> > + return;
> > +
> > + memmove(&bi->deratedbw[1], &bi->deratedbw[0],
> > + bi->num_qgv_points * sizeof(*bi->deratedbw));
> > +
> > + memmove(&bi->peakbw[1], &bi->peakbw[0],
> > + bi->num_qgv_points * sizeof(*bi->peakbw));
> > +
> > + /* Keep the derated bandwidth as the threshold*/
> > + bi->deratedbw[0] = PEAK_BW_THRESHOLD;
> > + bi->peakbw[0] = PEAK_BW_THRESHOLD;
> > + bi->num_qgv_points++;
> > +}
> > +
> > static int tgl_get_bw_info(struct intel_display *display,
> > const struct dram_info *dram_info,
> > const struct intel_sa_info *sa)
> > @@ -598,6 +644,7 @@ static int tgl_get_bw_info(struct intel_display
> > *display,
> > int num_channels = max_t(u8, 1, dram_info->num_channels);
> > int ipqdepth, ipqdepthpch = 16;
> > int dclk_max;
> > + bool insert_low_peakbw;
> > int maxdebw, peakbw;
> > int clperchgroup;
> > int num_groups = ARRAY_SIZE(display->bw.max);
> > @@ -636,6 +683,10 @@ static int tgl_get_bw_info(struct
> > intel_display *display,
> > */
> > clperchgroup = 4 * DIV_ROUND_UP(8, num_channels) *
> > qi.deinterleave;
> >
> > + insert_low_peakbw = xe3_check_lower_peakbw(display, &qi,
> > num_channels);
> > +
> > + display->bw.max[i].num_planes = 0;
> > +
> > for (i = 0; i < num_groups; i++) {
> > struct intel_bw_info *bi = &display->bw.max[i];
> > struct intel_bw_info *bi_next;
> > @@ -678,6 +729,9 @@ static int tgl_get_bw_info(struct intel_display
> > *display,
> >
> > qi.channel_width, 8);
> > }
> >
> > + if (insert_low_peakbw)
> > + xe3_insert_lowest_qgv_point(display, bi);
> > +
> > for (j = 0; j < qi.num_psf_points; j++) {
> > const struct intel_psf_gv_point *sp =
> > &qi.psf_points[j];
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_display_device.h
> > b/drivers/gpu/drm/i915/display/intel_display_device.h
> > index 65283286771a..b31ec42c3248 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display_device.h
> > +++ b/drivers/gpu/drm/i915/display/intel_display_device.h
> > @@ -192,6 +192,7 @@ struct intel_display_platforms {
> > #define HAS_MBUS_JOINING(__display) ((__display)-
> > >platform.alderlake_p || DISPLAY_VER(__display) >= 14)
> > #define HAS_MSO(__display) (DISPLAY_VER(__display) >=
> > 12)
> > #define HAS_OVERLAY(__display) (DISPLAY_INFO(__display)-
> > >has_overlay)
> > +#define
> > HAS_PEAK_BW_THRESHOLD(__display) (DISPLAY_VER(__display) >= 30)
> > #define HAS_PIPEDMC(__display) (DISPLAY_VER(__display) >=
> > 12)
> > #define
> > HAS_PIXEL_NORMALIZER(__display) (DISPLAY_VER(__display) >= 35)
> > #define
> > HAS_PMDEMAND(__display) (DISPLAY_VER(__display) >= 14)
>
next prev parent reply other threads:[~2026-05-12 12:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-11 12:28 [PATCH v2 00/11] drm/i915/display: reduce the pm demand peak bw based on display data rate Vinod Govindapillai
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 [this message]
2026-05-11 18:27 ` ✗ i915.CI.BAT: failure for drm/i915/display: reduce the pm demand peak bw based on display data rate 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=d87b96028d085d23407514d2f310bc89eba91819.camel@intel.com \
--to=vinod.govindapillai@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--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