From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "daniel@ffwll.ch" <daniel@ffwll.ch>
Cc: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 1/3] drm: Use original src rect while initializing damage iterator
Date: Fri, 19 Aug 2022 06:30:21 +0000 [thread overview]
Message-ID: <389bcc8371d4c47ac45db1a131faa67bbfb7ce75.camel@intel.com> (raw)
In-Reply-To: <YvUtGBkK7B3DZgjc@phenom.ffwll.local>
On Thu, 2022-08-11 at 18:23 +0200, Daniel Vetter wrote:
> On Fri, Jul 15, 2022 at 04:49:56PM +0300, Jouni Högander wrote:
> > drm_plane_state->src might be modified by the driver. This is done
> > e.g. in i915 driver when there is bigger framebuffer than the plane
> > and there is some offset within framebuffer. I915 driver calculates
> > separate offset and adjusts src rect coords to be relative to this
> > offset. Damage clips are still relative to original src coords
> > provided by user-space.
> >
> > This patch ensures original coordinates provided by user-space are
> > used when initiliazing damage iterator.
> >
> > Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
>
> Ah kunit test for this would be awesome. Iirc we have a few already
> for
> rect/damage stuff, defo should extend/fix those.
Can you please provide me some pointer to these tests? I have written
earlier one igt test which reveals this issue:
https://patchwork.freedesktop.org/series/103661/
https://patchwork.freedesktop.org/series/104488/
> -Daniel
>
> > ---
> > drivers/gpu/drm/drm_damage_helper.c | 11 +++++++----
> > 1 file changed, 7 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/drm_damage_helper.c
> > b/drivers/gpu/drm/drm_damage_helper.c
> > index 937b699ac2a8..d8b2955e88fd 100644
> > --- a/drivers/gpu/drm/drm_damage_helper.c
> > +++ b/drivers/gpu/drm/drm_damage_helper.c
> > @@ -224,6 +224,7 @@ drm_atomic_helper_damage_iter_init(struct
> > drm_atomic_helper_damage_iter *iter,
> > const struct drm_plane_state
> > *old_state,
> > const struct drm_plane_state *state)
> > {
> > + struct drm_rect src;
> > memset(iter, 0, sizeof(*iter));
> >
> > if (!state || !state->crtc || !state->fb || !state->visible)
> > @@ -233,10 +234,12 @@ drm_atomic_helper_damage_iter_init(struct
> > drm_atomic_helper_damage_iter *iter,
> > iter->num_clips = drm_plane_get_damage_clips_count(state);
> >
> > /* Round down for x1/y1 and round up for x2/y2 to catch all
> > pixels */
> > - iter->plane_src.x1 = state->src.x1 >> 16;
> > - iter->plane_src.y1 = state->src.y1 >> 16;
> > - iter->plane_src.x2 = (state->src.x2 >> 16) + !!(state->src.x2 &
> > 0xFFFF);
> > - iter->plane_src.y2 = (state->src.y2 >> 16) + !!(state->src.y2 &
> > 0xFFFF);
> > + src = drm_plane_state_src(state);
> > +
> > + iter->plane_src.x1 = src.x1 >> 16;
> > + iter->plane_src.y1 = src.y1 >> 16;
> > + iter->plane_src.x2 = (src.x2 >> 16) + !!(src.x2 & 0xFFFF);
> > + iter->plane_src.y2 = (src.y2 >> 16) + !!(src.y2 & 0xFFFF);
> >
> > if (!iter->clips || !drm_rect_equals(&state->src, &old_state-
> > >src)) {
> > iter->clips = NULL;
> > --
> > 2.25.1
> >
next prev parent reply other threads:[~2022-08-19 6:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 13:49 [Intel-gfx] [PATCH 0/3] Fixes for damage clips handling Jouni Högander
2022-07-15 13:49 ` [Intel-gfx] [PATCH 1/3] drm: Use original src rect while initializing damage iterator Jouni Högander
2022-08-11 16:23 ` Daniel Vetter
2022-08-19 6:30 ` Hogander, Jouni [this message]
2022-08-19 12:09 ` Maíra Canal
2022-08-19 13:19 ` Hogander, Jouni
2022-07-15 13:49 ` [Intel-gfx] [PATCH 2/3] drm/i915/display: Use original src in psr2 sel fetch area calculation Jouni Högander
2022-07-15 13:49 ` [Intel-gfx] [PATCH 3/3] drm/i915/display: Use drm helper instead of own loop for damage clips Jouni Högander
2022-07-16 15:11 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Fixes for damage clips handling Patchwork
2022-07-16 16:26 ` [Intel-gfx] ✗ 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=389bcc8371d4c47ac45db1a131faa67bbfb7ce75.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox