All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeykumar Sankaran <jsanka@codeaurora.org>
To: Sean Paul <sean@poorly.run>
Cc: Rajesh Yadav <ryadav@codeaurora.org>,
	linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org,
	Sean Paul <seanpaul@chromium.org>,
	freedreno@lists.freedesktop.org,
	Sravanthi Kollukuduru <skolluku@codeaurora.org>
Subject: Re: [PATCH v2] drm/msm: dpu: Allow planes to extend past active display
Date: Tue, 28 Aug 2018 15:04:06 -0700	[thread overview]
Message-ID: <8e057e8759588455e8a1816dd8336c33@codeaurora.org> (raw)
In-Reply-To: <20180828205106.15168-1-sean@poorly.run>

On 2018-08-28 13:50, Sean Paul wrote:
> From: Sean Paul <seanpaul@chromium.org>
> 
> The atomic_check is a bit too aggressive with respect to planes which
> leave the active area. This caused a bunch of log spew when the cursor
> got to the edge of the screen and stopped it from going all the way.
> 
> This patch removes the conservative bounds checks from atomic and clips
> the dst rect such that we properly display planes which go off the
> screen.
> 
> Changes in v2:
> - Apply the clip to src as well (taking into account scaling)
> 
> Cc: Sravanthi Kollukuduru <skolluku@codeaurora.org>
> Cc: Jeykumar Sankaran <jsanka@codeaurora.org>
> Signed-off-by: Sean Paul <seanpaul@chromium.org>
> ---
>  drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c  |  3 +--
>  drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c | 14 +++++++++++++-
>  2 files changed, 14 insertions(+), 3 deletions(-)
> 
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c
> b/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c
> index 07c2d15b45f2..f0a5e776ba32 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_crtc.c
> @@ -1551,8 +1551,7 @@ static int dpu_crtc_atomic_check(struct drm_crtc
> *crtc,
>  		cnt++;
> 
>  		dst = drm_plane_state_dest(pstate);
> -		if (!drm_rect_intersect(&clip, &dst) ||
> -		    !drm_rect_equals(&clip, &dst)) {
> +		if (!drm_rect_intersect(&clip, &dst)) {
>  			DPU_ERROR("invalid vertical/horizontal
> destination\n");
>  			DPU_ERROR("display: " DRM_RECT_FMT " plane: "
>  				  DRM_RECT_FMT "\n",
> DRM_RECT_ARG(&crtc_rect),
> diff --git a/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c
> b/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c
> index efdf9b200dd9..adfd16625188 100644
> --- a/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c
> +++ b/drivers/gpu/drm/msm/disp/dpu1/dpu_plane.c
> @@ -1254,7 +1254,8 @@ static int dpu_plane_sspp_atomic_update(struct
> drm_plane *plane,
>  	const struct dpu_format *fmt;
>  	struct drm_crtc *crtc;
>  	struct drm_framebuffer *fb;
> -	struct drm_rect src, dst;
> +	struct drm_rect clip = { 0 }, src, dst;
> +	int hscale, vscale;
> 
>  	if (!plane) {
>  		DPU_ERROR("invalid plane\n");
> @@ -1300,6 +1301,17 @@ static int dpu_plane_sspp_atomic_update(struct
> drm_plane *plane,
> 
>  	dst = drm_plane_state_dest(state);
> 
> +	hscale = drm_rect_calc_hscale(&src, &dst,
> +				      pdpu->pipe_sblk->maxupscale,
> +				      pdpu->pipe_sblk->maxdwnscale);
> +	vscale = drm_rect_calc_vscale(&src, &dst,
> +				      pdpu->pipe_sblk->maxupscale,
> +				      pdpu->pipe_sblk->maxdwnscale);
> +
> +	clip.x2 = crtc->state->adjusted_mode.hdisplay;
> +	clip.y2 = crtc->state->adjusted_mode.vdisplay;
> +	drm_rect_clip_scaled(&src, &dst, &clip, hscale, vscale);
> +
>  	DPU_DEBUG_PLANE(pdpu, "FB[%u] " DRM_RECT_FMT "->crtc%u "
> DRM_RECT_FMT
>  			", %4.4s ubwc %d\n", fb->base.id,
> DRM_RECT_ARG(&src),
>  			crtc->base.id, DRM_RECT_ARG(&dst),

Don't you have to update pdpu->pipe_cfg.src_rect and 
pdpu->pipe_cfg.dst_rect with clip?

-- 
Jeykumar S
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2018-08-28 22:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-28 20:50 [PATCH v2] drm/msm: dpu: Allow planes to extend past active display Sean Paul
2018-08-28 22:04 ` Jeykumar Sankaran [this message]
     [not found]   ` <8e057e8759588455e8a1816dd8336c33-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-08-28 22:52     ` Sean Paul
     [not found]       ` <CAMavQKLERkicusw3d4FPuxrZSzHs+-dfkUuCyhij6=-CMGfUMw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2018-08-29  0:01         ` Jeykumar Sankaran
     [not found]           ` <2c924a940e02978b470e98ee4331f33a-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2018-08-29 12:32             ` Sean Paul
     [not found] ` <20180828205106.15168-1-sean-p7yTbzM4H96eqtR555YLDQ@public.gmane.org>
2018-08-29 11:52   ` Ville Syrjälä

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=8e057e8759588455e8a1816dd8336c33@codeaurora.org \
    --to=jsanka@codeaurora.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=freedreno@lists.freedesktop.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=ryadav@codeaurora.org \
    --cc=sean@poorly.run \
    --cc=seanpaul@chromium.org \
    --cc=skolluku@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.