All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Cc: intel-xe@lists.freedesktop.org
Subject: Re: [PATCH v2 00/14] drm/i915: sagv/bw cleanup
Date: Fri, 04 Apr 2025 15:59:04 +0300	[thread overview]
Message-ID: <87ldsgytev.fsf@intel.com> (raw)
In-Reply-To: <20250326162544.3642-1-ville.syrjala@linux.intel.com>

On Wed, 26 Mar 2025, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Continue improving the code around sagv/bw vs.
> watermarks. A lot of the details get better encapsulated
> within intel_bw.c and the complicated interactions between
> different parts of the code are somewhat reduced.

On the series,

Reviewed-by: Jani Nikula <jani.nikula@intel.com>

with the caveat that my understanding of all the subtle bw stuff details
in patches 6-14 is admittedly weak. The patches make sense, and I didn't
spot anything obviously wrong, but there may well be cases that I just
couldn't think of.

BR,
Jani.


>
> v2: Rebase due to intel_display conversions
>
> Ville Syrjälä (14):
>   drm/i915: Drop the cached per-pipe min_cdclk[] from bw state
>   drm/i915: s/intel_crtc_bw/intel_dbuf_bw/
>   drm/i915: Extract intel_dbuf_bw_changed()
>   drm/i915: Pass intel_dbuf_bw to skl_*_calc_dbuf_bw() explicitly
>   drm/i915: Avoid triggering unwanted cdclk changes due to dbuf
>     bandwidth changes
>   drm/i915: Do more bw readout
>   drm/i915: Flag even inactive crtcs as "inherited"
>   drm/i915: Drop force_check_qgv
>   drm/i915: Extract intel_bw_modeset_checks()
>   drm/i915: Extract intel_bw_check_sagv_mask()
>   drm/i915: Make intel_bw_check_sagv_mask() internal to intel_bw.c
>   drm/i915: Make intel_bw_modeset_checks() internal to
>     intel_bw_atomic_check()
>   drm/i915: Skip bw stuff if per-crtc sagv state doesn't change
>   drm/i915: Eliminate intel_compute_sagv_mask()
>
>  drivers/gpu/drm/i915/display/intel_bw.c       | 187 ++++++++++++++----
>  drivers/gpu/drm/i915/display/intel_bw.h       |   9 +-
>  drivers/gpu/drm/i915/display/intel_cdclk.c    |   4 +
>  drivers/gpu/drm/i915/display/intel_display.c  |   5 +-
>  .../drm/i915/display/intel_modeset_setup.c    |  22 +--
>  drivers/gpu/drm/i915/display/skl_watermark.c  | 112 ++++-------
>  drivers/gpu/drm/i915/display/skl_watermark.h  |   1 +
>  7 files changed, 202 insertions(+), 138 deletions(-)

-- 
Jani Nikula, Intel

  parent reply	other threads:[~2025-04-04 12:59 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-26 16:25 [PATCH v2 00/14] drm/i915: sagv/bw cleanup Ville Syrjala
2025-03-26 16:25 ` [PATCH v2 01/14] drm/i915: Drop the cached per-pipe min_cdclk[] from bw state Ville Syrjala
2025-03-27  7:56   ` Jani Nikula
2025-03-26 16:25 ` [PATCH v2 02/14] drm/i915: s/intel_crtc_bw/intel_dbuf_bw/ Ville Syrjala
2025-03-27  7:57   ` Jani Nikula
2025-03-26 16:25 ` [PATCH v2 03/14] drm/i915: Extract intel_dbuf_bw_changed() Ville Syrjala
2025-03-27  7:57   ` Jani Nikula
2025-03-26 16:25 ` [PATCH v2 04/14] drm/i915: Pass intel_dbuf_bw to skl_*_calc_dbuf_bw() explicitly Ville Syrjala
2025-03-27  7:57   ` Jani Nikula
2025-03-26 16:25 ` [PATCH v2 05/14] drm/i915: Avoid triggering unwanted cdclk changes due to dbuf bandwidth changes Ville Syrjala
2025-03-27  8:00   ` Jani Nikula
2025-03-27 12:06     ` Ville Syrjälä
2025-03-26 16:25 ` [PATCH v2 06/14] drm/i915: Do more bw readout Ville Syrjala
2025-03-26 16:25 ` [PATCH v2 07/14] drm/i915: Flag even inactive crtcs as "inherited" Ville Syrjala
2025-03-26 16:25 ` [PATCH v2 08/14] drm/i915: Drop force_check_qgv Ville Syrjala
2025-03-26 16:25 ` [PATCH v2 09/14] drm/i915: Extract intel_bw_modeset_checks() Ville Syrjala
2025-03-26 16:25 ` [PATCH v2 10/14] drm/i915: Extract intel_bw_check_sagv_mask() Ville Syrjala
2025-03-26 16:25 ` [PATCH v2 11/14] drm/i915: Make intel_bw_check_sagv_mask() internal to intel_bw.c Ville Syrjala
2025-03-26 16:25 ` [PATCH v2 12/14] drm/i915: Make intel_bw_modeset_checks() internal to intel_bw_atomic_check() Ville Syrjala
2025-03-26 16:25 ` [PATCH v2 13/14] drm/i915: Skip bw stuff if per-crtc sagv state doesn't change Ville Syrjala
2025-03-26 16:25 ` [PATCH v2 14/14] drm/i915: Eliminate intel_compute_sagv_mask() Ville Syrjala
2025-03-26 17:19 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: sagv/bw cleanup (rev4) Patchwork
2025-03-26 17:20 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-03-26 17:45 ` ✓ CI.Patch_applied: success for drm/i915: sagv/bw cleanup (rev2) Patchwork
2025-03-26 17:45 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-26 17:46 ` ✓ CI.KUnit: success " Patchwork
2025-03-26 17:50 ` ✗ i915.CI.BAT: failure for drm/i915: sagv/bw cleanup (rev4) Patchwork
2025-03-26 18:03 ` ✓ CI.Build: success for drm/i915: sagv/bw cleanup (rev2) Patchwork
2025-03-26 18:05 ` ✓ CI.Hooks: " Patchwork
2025-03-26 18:07 ` ✗ CI.checksparse: warning " Patchwork
2025-03-26 18:29 ` ✓ Xe.CI.BAT: success " Patchwork
2025-03-27  8:02 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-27 11:46 ` Patchwork
2025-04-04 12:59 ` Jani Nikula [this message]
2025-04-04 18:15 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: sagv/bw cleanup (rev5) Patchwork
2025-04-04 18:15 ` ✗ Fi.CI.SPARSE: " Patchwork
2025-04-04 18:30 ` ✓ i915.CI.BAT: success " Patchwork
2025-04-04 21:37 ` ✗ 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=87ldsgytev.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.