From: Jani Nikula <jani.nikula@intel.com>
To: Gustavo Sousa <gustavo.sousa@intel.com>,
intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: Gustavo Sousa <gustavo.sousa@intel.com>
Subject: Re: [PATCH v3 1/5] drm/i915/bw: Don't call intel_dram_info() too early
Date: Fri, 15 May 2026 11:26:29 +0300 [thread overview]
Message-ID: <1607a6c47f563d56cb315a7b556a80303ee8a55b@intel.com> (raw)
In-Reply-To: <20260514-separate-platform-from-diplay-ip-specific-bw-params-v3-1-68727d6fe3ec@intel.com>
On Thu, 14 May 2026, Gustavo Sousa <gustavo.sousa@intel.com> wrote:
> If we end-up bailing early from intel_bw_init_hw() due to
> !HAS_DISPLAY(display), the call to intel_dram_info() to initialize
> dram_info will be meaningless. Move the call to be done after that
> check.
>
> Cc: Jani Nikula <jani.nikula@intel.com>
> Signed-off-by: Gustavo Sousa <gustavo.sousa@intel.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_bw.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_bw.c b/drivers/gpu/drm/i915/display/intel_bw.c
> index 9c3a9bbb49f6..7eef693b51ad 100644
> --- a/drivers/gpu/drm/i915/display/intel_bw.c
> +++ b/drivers/gpu/drm/i915/display/intel_bw.c
> @@ -791,11 +791,13 @@ static unsigned int icl_qgv_bw(struct intel_display *display,
>
> void intel_bw_init_hw(struct intel_display *display)
> {
> - const struct dram_info *dram_info = intel_dram_info(display);
> + const struct dram_info *dram_info;
>
> if (!HAS_DISPLAY(display))
> return;
>
> + dram_info = intel_dram_info(display);
> +
> /*
> * Starting with Xe3p_LPD, the hardware tells us whether memory has ECC
> * enabled that would impact display bandwidth. However, so far there
--
Jani Nikula, Intel
next prev parent reply other threads:[~2026-05-15 8:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-14 19:19 [PATCH v3 0/5] drm/i915/bw: Split bandwidth params into platform- and display-IP-specific structs Gustavo Sousa
2026-05-14 19:19 ` [PATCH v3 1/5] drm/i915/bw: Don't call intel_dram_info() too early Gustavo Sousa
2026-05-15 8:26 ` Jani Nikula [this message]
2026-05-14 19:19 ` [PATCH v3 2/5] drm/i915/bw: Extract platform-specific parameters Gustavo Sousa
2026-05-15 15:41 ` Gustavo Sousa
2026-05-15 16:49 ` Jani Nikula
2026-05-15 17:54 ` Gustavo Sousa
2026-05-14 19:19 ` [PATCH v3 3/5] drm/i915/bw: Deduplicate intel_sa_info instances Gustavo Sousa
2026-05-14 19:19 ` [PATCH v3 4/5] drm/i915/bw: Rename struct intel_sa_info to intel_display_bw_params Gustavo Sousa
2026-05-14 19:19 ` [PATCH v3 5/5] drm/i915/bw: Extract get_display_bw_params() Gustavo Sousa
2026-05-14 20:16 ` ✓ CI.KUnit: success for drm/i915/bw: Split bandwidth params into platform- and display-IP-specific structs (rev2) Patchwork
2026-05-14 21:11 ` ✓ Xe.CI.BAT: " Patchwork
2026-05-15 14:02 ` ✓ Xe.CI.FULL: " 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=1607a6c47f563d56cb315a7b556a80303ee8a55b@intel.com \
--to=jani.nikula@intel.com \
--cc=gustavo.sousa@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