Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Thomas Zimmermann" <tzimmermann@suse.de>,
	"Ville Syrjälä" <ville.syrjala@intel.com>
Cc: <jani.nikula@linux.intel.com>, <joonas.lahtinen@linux.intel.com>,
	<tursulin@ursulin.net>, <airlied@gmail.com>, <simona@ffwll.ch>,
	<intel-gfx@lists.freedesktop.org>,
	<intel-xe@lists.freedesktop.org>,
	<dri-devel@lists.freedesktop.org>,
	<sashiko-reviews@lists.linux.dev>,
	"Javier Martinez Canillas" <javierm@redhat.com>
Subject: Re: [PATCH] drm/i915/display: Handle struct drm_plane_state.ignore_damage_clips
Date: Wed, 8 Jul 2026 16:11:02 -0400	[thread overview]
Message-ID: <ak6u1iPEIDulYTnv@intel.com> (raw)
In-Reply-To: <13f94040-6f6d-4a8e-9581-be769a0e3abb@suse.de>

On Wed, Jul 08, 2026 at 09:44:05AM +0200, Thomas Zimmermann wrote:
> gentle reminder to review this patch

Ville, could you please take a look on this?

Thomas, have you seen shashiko for this?
https://sashiko.dev/#/patchset/20260701130929.234695-1-tzimmermann%40suse.de

> 
> Am 01.07.26 um 15:07 schrieb Thomas Zimmermann:
> > Git commit 35ed38d58257 ("drm: Allow drivers to indicate the damage
> > helpers to ignore damage clips") introduced ignore_damage_clips to
> > selectively ignore damage clipping in certain framebuffer changes. The
> > mode-setting pipeline can disabled damage clippings for an atomic commit
> > by setting ignore_damage_clips in struct drm_plane_state. The atomic
> > commit will then do a full display update.
> > 
> > Although the i915 driver does not modify the flag, DRM's damage iterator
> > will soon rely on it. Calling drm_atomic_helper_check_plane_damage() right
> > before drm_atomic_helper_damage_merged() guarantees that it has the correct
> > state. The i915 driver does not do this elsewhere so far.
> > 
> > Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> > Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
> > ---
> > Taken with minor updates to the commit description from the series at
> > 
> >    https://lore.kernel.org/dri-devel/20260610152505.260172-1-tzimmermann@suse.de/
> > ---
> >   drivers/gpu/drm/i915/display/intel_psr.c | 3 +++
> >   1 file changed, 3 insertions(+)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/intel_psr.c b/drivers/gpu/drm/i915/display/intel_psr.c
> > index 92af21d823a3..5a155f60110f 100644
> > --- a/drivers/gpu/drm/i915/display/intel_psr.c
> > +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> > @@ -2949,6 +2949,9 @@ int intel_psr2_sel_fetch_update(struct intel_atomic_state *state,
> >   		src = drm_plane_state_src(&new_plane_state->uapi);
> >   		drm_rect_fp_to_int(&src, &src);
> > +		/* Prepare plane-damage state before using it */
> > +		drm_atomic_helper_check_plane_damage(&state->base, &new_plane_state->uapi);
> > +
> >   		if (!drm_atomic_helper_damage_merged(&old_plane_state->uapi,
> >   						     &new_plane_state->uapi, &damaged_area))
> >   			continue;
> 
> -- 
> --
> Thomas Zimmermann
> Graphics Driver Developer
> SUSE Software Solutions Germany GmbH
> Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
> GF: Jochen Jaser, Andrew McDonald, (HRB 36809, AG Nürnberg)
> 
> 

  reply	other threads:[~2026-07-08 20:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-01 13:07 [PATCH] drm/i915/display: Handle struct drm_plane_state.ignore_damage_clips Thomas Zimmermann
2026-07-01 15:00 ` ✓ CI.KUnit: success for " Patchwork
2026-07-01 15:43 ` ✗ Xe.CI.BAT: failure " Patchwork
2026-07-02  9:38 ` ✓ Xe.CI.FULL: success " Patchwork
2026-07-08  7:44 ` [PATCH] " Thomas Zimmermann
2026-07-08 20:11   ` Rodrigo Vivi [this message]
2026-07-09  7:15     ` Thomas Zimmermann

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=ak6u1iPEIDulYTnv@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=airlied@gmail.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jani.nikula@linux.intel.com \
    --cc=javierm@redhat.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=sashiko-reviews@lists.linux.dev \
    --cc=simona@ffwll.ch \
    --cc=tursulin@ursulin.net \
    --cc=tzimmermann@suse.de \
    --cc=ville.syrjala@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