From: "Govindapillai, Vinod" <vinod.govindapillai@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Coelho, Luciano" <luciano.coelho@intel.com>
Subject: Re: [PATCH 3/6] drm/i915/wm: remove stale FIXME in skl_needs_memory_bw_wa()
Date: Tue, 16 Sep 2025 09:21:51 +0000 [thread overview]
Message-ID: <5fbc41142883ce22bf350f865c697583988dad1d.camel@intel.com> (raw)
In-Reply-To: <20250908073734.1180687-4-luciano.coelho@intel.com>
On Mon, 2025-09-08 at 10:35 +0300, Luca Coelho wrote:
> This FIXME has been there forever and apparently the _proper code_ has
> never been added, and, since it's a very old platform alreday, most
> likely never will. It hasn't been a problem to keep the workaround
> for all cases, so let's drop the FIXME tag.
>
> Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
> ---
> drivers/gpu/drm/i915/display/skl_watermark.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
Reviewed-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
> diff --git a/drivers/gpu/drm/i915/display/skl_watermark.c
> b/drivers/gpu/drm/i915/display/skl_watermark.c
> index 3b409442db37..0ce3420a919e 100644
> --- a/drivers/gpu/drm/i915/display/skl_watermark.c
> +++ b/drivers/gpu/drm/i915/display/skl_watermark.c
> @@ -83,8 +83,8 @@ u8 intel_enabled_dbuf_slices_mask(struct intel_display *display)
> }
>
> /*
> - * FIXME: We still don't have the proper code detect if we need to apply the WA,
> - * so assume we'll always need it in order to avoid underruns.
> + * We don't have the proper code detect if we need to apply the WA, so
> + * assume we'll always need it in order to avoid underruns.
> */
> static bool skl_needs_memory_bw_wa(struct intel_display *display)
> {
next prev parent reply other threads:[~2025-09-16 9:21 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 7:35 [PATCH 0/6] drm/i915/wm: some clean-ups and a bit of refactoring Luca Coelho
2025-09-08 7:35 ` [PATCH 1/6] drm/i915/wm: clarify watermark ops with comments Luca Coelho
2025-09-16 8:52 ` Govindapillai, Vinod
2025-09-22 10:26 ` Luca Coelho
2025-09-08 7:35 ` [PATCH 2/6] drm/i915/wm: move intel_sagv_init() to avoid forward declaration Luca Coelho
2025-09-16 8:53 ` Govindapillai, Vinod
2025-09-08 7:35 ` [PATCH 3/6] drm/i915/wm: remove stale FIXME in skl_needs_memory_bw_wa() Luca Coelho
2025-09-16 9:21 ` Govindapillai, Vinod [this message]
2025-09-08 7:35 ` [PATCH 4/6] drm/i915/wm: convert x/y-tiling bools to an enum Luca Coelho
2025-09-08 12:43 ` Gustavo Sousa
2025-09-08 12:53 ` Luca Coelho
2025-09-19 8:36 ` Ville Syrjälä
2025-09-22 12:38 ` Luca Coelho
2025-09-22 12:48 ` Ville Syrjälä
2025-09-08 7:35 ` [PATCH 5/6] drm/i915/wm: convert tiling mode check in slk_compute_plane_wm() to a switch-case Luca Coelho
2025-09-08 12:51 ` Gustavo Sousa
2025-09-08 12:57 ` Luca Coelho
2025-09-08 7:35 ` [PATCH 6/6] drm/i915/wm: move method selection and calculation to a separate function Luca Coelho
2025-09-19 18:00 ` Ville Syrjälä
2025-09-29 7:21 ` Luca Coelho
2025-09-08 17:20 ` ✓ i915.CI.BAT: success for drm/i915/wm: some clean-ups and a bit of refactoring Patchwork
2025-09-09 2:47 ` ✗ i915.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=5fbc41142883ce22bf350f865c697583988dad1d.camel@intel.com \
--to=vinod.govindapillai@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=luciano.coelho@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