From: Jani Nikula <jani.nikula@linux.intel.com>
To: Vinod Govindapillai <vinod.govindapillai@intel.com>,
intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org
Cc: vinod.govindapillai@intel.com, ville.syrjala@linux.intel.com,
matthew.d.roper@intel.com, shawn.c.lee@intel.com
Subject: Re: [PATCH v2] drm/i915/display: update to the BW buddy configuration
Date: Wed, 17 Jun 2026 14:38:15 +0300 [thread overview]
Message-ID: <4abfacf0bf38d230f5b5ed6236d2f28cd9a77f3e@intel.com> (raw)
In-Reply-To: <20260616184131.295013-1-vinod.govindapillai@intel.com>
On Tue, 16 Jun 2026, Vinod Govindapillai <vinod.govindapillai@intel.com> wrote:
> Bspec has been updated for xe2_lpd+ platforms on how to handle
> the bw buddy prgramming in case no matching memory configuration
> is found w.r.t the current page mask table. The recommendation
> is to keep the default settings for the related registers as it
> is without explicitly disabling the bw buddy.
>
> v2: removed extra explanation
>
> Bspec: 68871
> Suggested-by: Ville Syrjala <ville.syrjala@intel.com>
> Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_display_power.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_power.c b/drivers/gpu/drm/i915/display/intel_display_power.c
> index 2e51dfcd5dce..3d348c5decee 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_power.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_power.c
> @@ -1634,9 +1634,12 @@ static void tgl_bw_buddy_init(struct intel_display *display)
> if (table[config].page_mask == 0) {
> drm_dbg_kms(display->drm,
> "Unknown memory configuration; disabling address buddy logic.\n");
The debug logging becomes misleading for display >= 20.
BR,
Jani.
> - for_each_set_bit(i, &abox_mask, BITS_PER_TYPE(abox_mask))
> - intel_de_write(display, BW_BUDDY_CTL(i),
> - BW_BUDDY_DISABLE);
> +
> + if (DISPLAY_VER(display) < 20) {
> + for_each_set_bit(i, &abox_mask, BITS_PER_TYPE(abox_mask))
> + intel_de_write(display, BW_BUDDY_CTL(i),
> + BW_BUDDY_DISABLE);
> + }
> } else {
> for_each_set_bit(i, &abox_mask, BITS_PER_TYPE(abox_mask)) {
> intel_de_write(display, BW_BUDDY_PAGE_MASK(i),
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-06-17 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-16 18:41 [PATCH v2] drm/i915/display: update to the BW buddy configuration Vinod Govindapillai
2026-06-16 18:48 ` ✓ CI.KUnit: success for drm/i915/display: update to the BW buddy configuration (rev2) Patchwork
2026-06-16 19:26 ` ✓ Xe.CI.BAT: " Patchwork
2026-06-16 21:48 ` [PATCH v2] drm/i915/display: update to the BW buddy configuration Michał Grzelak
2026-06-16 23:06 ` ✓ Xe.CI.FULL: success for drm/i915/display: update to the BW buddy configuration (rev2) Patchwork
2026-06-17 11:38 ` Jani Nikula [this message]
2026-06-17 13:30 ` [PATCH v2] drm/i915/display: update to the BW buddy configuration Govindapillai, Vinod
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=4abfacf0bf38d230f5b5ed6236d2f28cd9a77f3e@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.d.roper@intel.com \
--cc=shawn.c.lee@intel.com \
--cc=ville.syrjala@linux.intel.com \
--cc=vinod.govindapillai@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