Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Govindapillai <vinod.govindapillai@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org, vinod.govindapillai@intel.com,
	ville.syrjala@linux.intel.com, santhosh.reddy.guddati@intel.com,
	jani.saarinen@intel.com
Subject: [PATCH v9 1/8] drm/damage-helper: add const qualifier in drm_atomic_helper_damage_merged()
Date: Thu, 20 Feb 2025 12:41:37 +0200	[thread overview]
Message-ID: <20250220104144.207526-2-vinod.govindapillai@intel.com> (raw)
In-Reply-To: <20250220104144.207526-1-vinod.govindapillai@intel.com>

Add a const qualifier for the "state" parameter as well as we could
use this helper to get the combined damage in cases of const
drm_plane_state as well. Needed mainly for xe driver big joiner cases
where we need to track the damage from immutable plane state.

Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
Signed-off-by: Vinod Govindapillai <vinod.govindapillai@intel.com>
---
 drivers/gpu/drm/drm_damage_helper.c | 2 +-
 include/drm/drm_damage_helper.h     | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/gpu/drm/drm_damage_helper.c b/drivers/gpu/drm/drm_damage_helper.c
index afb02aae707b..44a5a36806e3 100644
--- a/drivers/gpu/drm/drm_damage_helper.c
+++ b/drivers/gpu/drm/drm_damage_helper.c
@@ -308,7 +308,7 @@ EXPORT_SYMBOL(drm_atomic_helper_damage_iter_next);
  * True if there is valid plane damage otherwise false.
  */
 bool drm_atomic_helper_damage_merged(const struct drm_plane_state *old_state,
-				     struct drm_plane_state *state,
+				     const struct drm_plane_state *state,
 				     struct drm_rect *rect)
 {
 	struct drm_atomic_helper_damage_iter iter;
diff --git a/include/drm/drm_damage_helper.h b/include/drm/drm_damage_helper.h
index effda42cce31..a58cbcd11276 100644
--- a/include/drm/drm_damage_helper.h
+++ b/include/drm/drm_damage_helper.h
@@ -78,7 +78,7 @@ bool
 drm_atomic_helper_damage_iter_next(struct drm_atomic_helper_damage_iter *iter,
 				   struct drm_rect *rect);
 bool drm_atomic_helper_damage_merged(const struct drm_plane_state *old_state,
-				     struct drm_plane_state *state,
+				     const struct drm_plane_state *state,
 				     struct drm_rect *rect);
 
 #endif
-- 
2.43.0


  reply	other threads:[~2025-02-20 10:42 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 10:41 [PATCH v9 0/8] drm/i915/fbc: FBC Dirty rect feature support Vinod Govindapillai
2025-02-20 10:41 ` Vinod Govindapillai [this message]
2025-02-20 10:41 ` [PATCH v9 2/8] drm/i915/display: update and store the plane damage clips Vinod Govindapillai
2025-02-20 10:41 ` [PATCH v9 3/8] drm/i915/fbc: add register definitions for fbc dirty rect support Vinod Govindapillai
2025-02-20 10:41 ` [PATCH v9 4/8] drm/i915/fbc: introduce HAS_FBC_DIRTY_RECT() for FBC " Vinod Govindapillai
2025-02-20 10:41 ` [PATCH v9 5/8] drm/i915/fbc: avoid calling fbc activate if fbc is active Vinod Govindapillai
2025-02-20 10:41 ` [PATCH v9 6/8] drm/i915/fbc: dirty rect support for FBC Vinod Govindapillai
2025-02-20 10:41 ` [PATCH v9 7/8] drm/i915/fbc: disable FBC if PSR2 selective fetch is enabled Vinod Govindapillai
2025-02-20 10:41 ` [PATCH v9 8/8] drm/i915/fbc: handle dirty rect coords for the first frame Vinod Govindapillai
2025-02-21 17:54   ` Ville Syrjälä
2025-02-20 10:47 ` ✓ CI.Patch_applied: success for drm/i915/fbc: FBC Dirty rect feature support (rev3) Patchwork
2025-02-20 10:47 ` ✗ CI.checkpatch: warning " Patchwork
2025-02-20 10:49 ` ✓ CI.KUnit: success " Patchwork
2025-02-20 11:05 ` ✓ CI.Build: " Patchwork
2025-02-20 11:07 ` ✓ CI.Hooks: " Patchwork
2025-02-20 11:09 ` ✗ CI.checksparse: warning " Patchwork
2025-02-20 11:29 ` ✓ Xe.CI.BAT: success " Patchwork
2025-02-21  5:13 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-21  7:45   ` Govindapillai, Vinod

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=20250220104144.207526-2-vinod.govindapillai@intel.com \
    --to=vinod.govindapillai@intel.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.saarinen@intel.com \
    --cc=santhosh.reddy.guddati@intel.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox