dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Thomas Zimmermann <tzimmermann@suse.de>
Cc: airlied@linux.ie, airlied@redhat.com, sean@poorly.run,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/udl: Enable damage clipping
Date: Wed, 7 Sep 2022 18:38:43 +0200	[thread overview]
Message-ID: <YxjJExmVL1y3gsqg@phenom.ffwll.local> (raw)
In-Reply-To: <a659a499-1afd-aec2-01da-bb79c11d0ba2@suse.de>

On Wed, Sep 07, 2022 at 08:59:17AM +0200, Thomas Zimmermann wrote:
> Hi
> 
> Am 06.09.22 um 21:35 schrieb Daniel Vetter:
> > On Thu, Jul 28, 2022 at 09:47:56AM +0200, Thomas Zimmermann wrote:
> > > Call drm_plane_enable_fb_damage_clips() and give userspace a chance
> > > of minimizing the updated display area.
> > > 
> > > Signed-off-by: Thomas Zimmermann <tzimmermann@suse.de>
> > > ---
> > >   drivers/gpu/drm/udl/udl_modeset.c | 1 +
> > >   1 file changed, 1 insertion(+)
> > > 
> > > diff --git a/drivers/gpu/drm/udl/udl_modeset.c b/drivers/gpu/drm/udl/udl_modeset.c
> > > index e67c40a48fb4..ce427128f034 100644
> > > --- a/drivers/gpu/drm/udl/udl_modeset.c
> > > +++ b/drivers/gpu/drm/udl/udl_modeset.c
> > > @@ -479,6 +479,7 @@ int udl_modeset_init(struct drm_device *dev)
> > >   					   format_count, NULL, connector);
> > >   	if (ret)
> > >   		return ret;
> > > +	drm_plane_enable_fb_damage_clips(&udl->display_pipe.plane);
> > 
> > I'm assuming this passes with all the igts we have (I hope those finally
> > landed) and a damage-capable compositor doesn't go boom either?
> > 
> > Either way patch lgtm. Reviewed-by: Daniel Vetter <daniel.vetter@ffwll.ch>
> > 
> > Also I wonder whether we should have a check in the damage helpers to make
> > sure drivers don't forget to call this function to set up the uapi ...
> 
> It warns, but you can ignore that.

Yeah that's as good as it gets, we can't crash the driver :-)
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch

      reply	other threads:[~2022-09-07 16:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-28  7:47 [PATCH] drm/udl: Enable damage clipping Thomas Zimmermann
2022-09-06 19:35 ` Daniel Vetter
2022-09-07  6:59   ` Thomas Zimmermann
2022-09-07 16:38     ` Daniel Vetter [this message]

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=YxjJExmVL1y3gsqg@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=airlied@linux.ie \
    --cc=airlied@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=sean@poorly.run \
    --cc=tzimmermann@suse.de \
    /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;
as well as URLs for NNTP newsgroup(s).