Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH 00/13] drm/1915: skl+ watermark/latency stuff
Date: Fri, 5 Sep 2025 18:01:53 +0300	[thread overview]
Message-ID: <aLr7YVbvr-9AB8J6@intel.com> (raw)
In-Reply-To: <20250905145212.10845-1-ville.syrjala@linux.intel.com>

On Fri, Sep 05, 2025 at 05:51:59PM +0300, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> A bunch of claenup to the watermark latency setup on skl+, and
> a few potential fixes for some edge cases.

Please ignore this incomplete series. Apparently gnome-keyring has some
decades old bug where it randomly fails, and this time it happened in
the middle of posting this series :(

> 
> Ville Syrjälä (13):
>   drm/i915/dram: Also apply the 16Gb DIMM w/a for larger DRAM chips
>   drm/i915: Apply the 16Gb DIMM w/a only for the platforms that need it
>   drm/i915: Tweak the read latency fixup code
>   drm/i915: Don't pass the latency array to {skl,mtl}_read_wm_latency()
>   drm/i915: Move adjust_wm_latency() out from
>     {mtl,skl}_read_wm_latency()
>   drm/i915: Extract multiply_wm_latency() from skl_read_wm_latency()
>   drm/i915: Extract increase_wm_latency()
>   drm/i915: Use increase_wm_latency() for the 16Gb DIMM w/a
>   drm/i915: Extract sanitize_wm_latency()
>   drm/i915: Flatten sanitize_wm_latency() a bit
>   drm/i915: Make wm latencies monotonic
>   drm/i915: Print both the original and adjusted wm latencies
>   drm/i915: Make sure wm block/lines are non-decreasing
> 
>  drivers/gpu/drm/i915/display/skl_watermark.c | 160 +++++++++++++------
>  drivers/gpu/drm/i915/soc/intel_dram.c        |  10 +-
>  2 files changed, 118 insertions(+), 52 deletions(-)
> 
> -- 
> 2.49.1

-- 
Ville Syrjälä
Intel

  parent reply	other threads:[~2025-09-05 15:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-05 14:51 [PATCH 00/13] drm/1915: skl+ watermark/latency stuff Ville Syrjala
2025-09-05 14:52 ` [PATCH 01/13] drm/i915/dram: Also apply the 16Gb DIMM w/a for larger DRAM chips Ville Syrjala
2025-09-05 14:52 ` [PATCH 02/13] drm/i915: Apply the 16Gb DIMM w/a only for the platforms that need it Ville Syrjala
2025-09-05 14:52 ` [PATCH 03/13] drm/i915: Tweak the read latency fixup code Ville Syrjala
2025-09-05 14:52 ` [PATCH 04/13] drm/i915: Don't pass the latency array to {skl, mtl}_read_wm_latency() Ville Syrjala
2025-09-05 15:01 ` Ville Syrjälä [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-09-05 14:58 [PATCH 00/13] drm/1915: skl+ watermark/latency stuff Ville Syrjala

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=aLr7YVbvr-9AB8J6@intel.com \
    --to=ville.syrjala@linux.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