From: "Hogander, Jouni" <jouni.hogander@intel.com>
To: "intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"Souza, Jose" <jose.souza@intel.com>
Cc: "markpearson@lenovo.com" <markpearson@lenovo.com>
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/i915: Ensure damage clip area is within pipe area
Date: Mon, 9 May 2022 07:25:15 +0000 [thread overview]
Message-ID: <fcbffc3da3fe381ceacaaff6a002a324d2798617.camel@intel.com> (raw)
In-Reply-To: <c79692eb687ba3ebfa0470f07d381607b2825fbf.camel@intel.com>
On Fri, 2022-05-06 at 15:43 +0000, Souza, Jose wrote:
> On Fri, 2022-05-06 at 08:48 +0300, Jouni Högander wrote:
> > Current update area calculation is not handling situation where
> > e.g. cursor plane is fully or partially outside pipe area.
> >
> > Fix this by checking damage area against pipe_src area using
> > drm_rect_intersect.
> >
> > Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/5440
> > Cc: José Roberto de Souza <jose.souza@intel.com>
> > Cc: Mika Kahola <mika.kahola@intel.com>
> > Tested-by: Mark Pearson <markpearson@lenovo.com>
> > Signed-off-by: Jouni Högander <jouni.hogander@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_psr.c | 17 +++++++++++++----
> > 1 file changed, 13 insertions(+), 4 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_psr.c
> > b/drivers/gpu/drm/i915/display/intel_psr.c
> > index 8c099d24de86..5229ba89a079 100644
> > --- a/drivers/gpu/drm/i915/display/intel_psr.c
> > +++ b/drivers/gpu/drm/i915/display/intel_psr.c
> > @@ -1724,6 +1724,10 @@ int intel_psr2_sel_fetch_update(struct
> > intel_atomic_state *state,
> > break;
> > }
> >
> > +/* Set x1 and x2 for drm_rect_intersect usage */
> > +damaged_area.x1 = 0;
> > +damaged_area.x2 = INT_MAX;
>
> Move the above to the variable definition and initialization.
>
Fixed, please check new version.
> > +
> > /*
> > * If visibility or plane moved, mark the whole plane area as
> > * damaged as it needs to be complete redraw in the new and old
> > @@ -1735,20 +1739,23 @@ int intel_psr2_sel_fetch_update(struct
> > intel_atomic_state *state,
> > if (old_plane_state->uapi.visible) {
> > damaged_area.y1 = old_plane_state->uapi.dst.y1;
> > damaged_area.y2 = old_plane_state->uapi.dst.y2;
> > -clip_area_update(&pipe_clip, &damaged_area);
> > +if (drm_rect_intersect(&damaged_area, &crtc_state->pipe_src))
> > +clip_area_update(&pipe_clip, &damaged_area);
> > }
> >
> > if (new_plane_state->uapi.visible) {
> > damaged_area.y1 = new_plane_state->uapi.dst.y1;
> > damaged_area.y2 = new_plane_state->uapi.dst.y2;
> > -clip_area_update(&pipe_clip, &damaged_area);
> > +if (drm_rect_intersect(&damaged_area, &crtc_state->pipe_src))
> > +clip_area_update(&pipe_clip, &damaged_area);
> > }
> > continue;
> > } else if (new_plane_state->uapi.alpha != old_plane_state-
> > >uapi.alpha) {
> > /* If alpha changed mark the whole plane area as damaged */
> > damaged_area.y1 = new_plane_state->uapi.dst.y1;
> > damaged_area.y2 = new_plane_state->uapi.dst.y2;
> > -clip_area_update(&pipe_clip, &damaged_area);
> > +if (drm_rect_intersect(&damaged_area, &crtc_state->pipe_src))
> > +clip_area_update(&pipe_clip, &damaged_area);
> > continue;
> > }
> >
> > @@ -1767,7 +1774,9 @@ int intel_psr2_sel_fetch_update(struct
> > intel_atomic_state *state,
> >
> > damaged_area.y1 += new_plane_state->uapi.dst.y1 - src.y1;
> > damaged_area.y2 += new_plane_state->uapi.dst.y1 - src.y1;
> > -clip_area_update(&pipe_clip, &damaged_area);
> > +
> > +if (drm_rect_intersect(&damaged_area, &crtc_state->pipe_src))
> > +clip_area_update(&pipe_clip, &damaged_area);
>
> As it is repeating move the drm_rect_intersect() call to
> clip_area_update(), adding a crtc_state parameter or pipe_src, your
> call.
>
> Also please include a Fixes tag to some commit that makes sense so
> this patch is backported to older kernels with selective fetch
> enabled.
>
> > }
> >
> > if (pipe_clip.y1 == -1)
next prev parent reply other threads:[~2022-05-09 7:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-06 5:48 [Intel-gfx] [PATCH 0/2] Fixes for selective fetch area calculation Jouni Högander
2022-05-06 5:48 ` [Intel-gfx] [PATCH 1/2] drm/i915/psr: Use full update In case of area calculation fails Jouni Högander
2022-05-06 15:29 ` Souza, Jose
2022-05-06 18:28 ` Hogander, Jouni
2022-05-06 18:40 ` Souza, Jose
2022-05-09 7:30 ` Hogander, Jouni
2022-05-06 5:48 ` [Intel-gfx] [PATCH 2/2] drm/i915: Ensure damage clip area is within pipe area Jouni Högander
2022-05-06 15:43 ` Souza, Jose
2022-05-09 7:25 ` Hogander, Jouni [this message]
2022-05-06 10:42 ` [Intel-gfx] ✓ Fi.CI.BAT: success for Fixes for selective fetch area calculation Patchwork
2022-05-06 13:37 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=fcbffc3da3fe381ceacaaff6a002a324d2798617.camel@intel.com \
--to=jouni.hogander@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=markpearson@lenovo.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