All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH 0/3] drm/i915: Rework global state serialization
Date: Tue, 19 Dec 2023 15:07:53 +0200	[thread overview]
Message-ID: <20231219130756.25986-1-ville.syrjala@linux.intel.com> (raw)

From: Ville Syrjälä <ville.syrjala@linux.intel.com>

Rework the way we do the hardware serialization with
global states. This avoids angering drm_atomic_check_only(),
and I suppose it's a bit more efficient as well.

Ville Syrjälä (3):
  drm/i915: Compute use_sagv_wm differently
  drm/i915: Rework global state serializaiton
  drm/i915: Extract intel_atomic_swap_state()

 drivers/gpu/drm/i915/display/intel_display.c  |  42 +++++-
 .../gpu/drm/i915/display/intel_global_state.c | 137 ++++++++++++++++--
 .../gpu/drm/i915/display/intel_global_state.h |   9 +-
 drivers/gpu/drm/i915/display/skl_watermark.c  |  38 +++--
 4 files changed, 193 insertions(+), 33 deletions(-)

-- 
2.41.0


             reply	other threads:[~2023-12-19 13:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-19 13:07 Ville Syrjala [this message]
2023-12-19 13:07 ` [PATCH 1/3] drm/i915: Compute use_sagv_wm differently Ville Syrjala
2024-02-01  8:17   ` Lisovskiy, Stanislav
2023-12-19 13:07 ` [PATCH 2/3] drm/i915: Rework global state serializaiton Ville Syrjala
2024-02-01  8:48   ` Lisovskiy, Stanislav
2023-12-19 13:07 ` [PATCH 3/3] drm/i915: Extract intel_atomic_swap_state() Ville Syrjala
2024-01-15 11:10   ` Lisovskiy, Stanislav
2023-12-19 13:39 ` ✗ Fi.CI.SPARSE: warning for drm/i915: Rework global state serialization Patchwork
2023-12-19 13:52 ` ✓ Fi.CI.BAT: success " Patchwork
2023-12-19 15:25 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-01-10 18:17 ` ✗ Fi.CI.SPARSE: warning for drm/i915: Rework global state serialization (rev2) Patchwork
2024-01-10 18:30 ` ✓ Fi.CI.BAT: success " Patchwork
2024-01-10 22:20 ` ✗ Fi.CI.IGT: 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=20231219130756.25986-1-ville.syrjala@linux.intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@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 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.