dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	Benjamin Gaignard <benjamin.gaignard@st.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/rect: Keep the clipped dst rectangle in place
Date: Wed, 20 Nov 2019 17:43:40 +0100	[thread overview]
Message-ID: <20191120164340.GS30416@phenom.ffwll.local> (raw)
In-Reply-To: <20191120162512.12484-2-ville.syrjala@linux.intel.com>

On Wed, Nov 20, 2019 at 06:25:12PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> Now that we've constrained the clipped source rectangle such
> that it can't have negative dimensions doing the same for the
> dst rectangle seems appropriate. Should at least result in
> the clipped src and dst rectangles being a bit more consistent
> with each other.
> 
> Cc: Benjamin Gaignard <benjamin.gaignard@st.com>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

selftests for this stuff? Looks like the prime example, write testcase
proving code is busted, fix it, everyone celebrate?
-Daniel

> ---
>  drivers/gpu/drm/drm_rect.c | 22 +++++++++++-----------
>  1 file changed, 11 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/gpu/drm/drm_rect.c b/drivers/gpu/drm/drm_rect.c
> index 7762b6e9278d..229325fcf333 100644
> --- a/drivers/gpu/drm/drm_rect.c
> +++ b/drivers/gpu/drm/drm_rect.c
> @@ -52,14 +52,14 @@ bool drm_rect_intersect(struct drm_rect *r1, const struct drm_rect *r2)
>  }
>  EXPORT_SYMBOL(drm_rect_intersect);
>  
> -static u32 clip_scaled(u32 src, u32 dst, u32 clip)
> +static u32 clip_scaled(int src, int dst, int *clip)
>  {
>  	u64 tmp;
>  
>  	/* Only clip what we have. Keeps the result bounded as well. */
> -	clip = min(clip, dst);
> +	*clip = min(*clip, dst);
>  
> -	tmp = mul_u32_u32(src, dst - clip);
> +	tmp = mul_u32_u32(src, dst - *clip);
>  
>  	/*
>  	 * Round toward 1.0 when clipping so that we don't accidentally
> @@ -92,34 +92,34 @@ bool drm_rect_clip_scaled(struct drm_rect *src, struct drm_rect *dst,
>  	diff = clip->x1 - dst->x1;
>  	if (diff > 0) {
>  		u32 new_src_w = clip_scaled(drm_rect_width(src),
> -					    drm_rect_width(dst), diff);
> +					    drm_rect_width(dst), &diff);
>  
>  		src->x1 = src->x2 - new_src_w;
> -		dst->x1 = clip->x1;
> +		dst->x1 += diff;
>  	}
>  	diff = clip->y1 - dst->y1;
>  	if (diff > 0) {
>  		u32 new_src_h = clip_scaled(drm_rect_height(src),
> -					    drm_rect_height(dst), diff);
> +					    drm_rect_height(dst), &diff);
>  
>  		src->y1 = src->y2 - new_src_h;
> -		dst->y1 = clip->y1;
> +		dst->y1 += diff;
>  	}
>  	diff = dst->x2 - clip->x2;
>  	if (diff > 0) {
>  		u32 new_src_w = clip_scaled(drm_rect_width(src),
> -					    drm_rect_width(dst), diff);
> +					    drm_rect_width(dst), &diff);
>  
>  		src->x2 = src->x1 + new_src_w;
> -		dst->x2 = clip->x2;
> +		dst->x2 -= diff;
>  	}
>  	diff = dst->y2 - clip->y2;
>  	if (diff > 0) {
>  		u32 new_src_h = clip_scaled(drm_rect_height(src),
> -					    drm_rect_height(dst), diff);
> +					    drm_rect_height(dst), &diff);
>  
>  		src->y2 = src->y1 + new_src_h;
> -		dst->y2 = clip->y2;
> +		dst->y2 -= diff;
>  	}
>  
>  	return drm_rect_visible(dst);
> -- 
> 2.23.0
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch>
To: Ville Syrjala <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	Benjamin Gaignard <benjamin.gaignard@st.com>,
	dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 2/2] drm/rect: Keep the clipped dst rectangle in place
Date: Wed, 20 Nov 2019 17:43:40 +0100	[thread overview]
Message-ID: <20191120164340.GS30416@phenom.ffwll.local> (raw)
Message-ID: <20191120164340.giJo_AuoqhATSwPWyH1sM3Bu6ZrGjO1QN3EjILHoIQw@z> (raw)
In-Reply-To: <20191120162512.12484-2-ville.syrjala@linux.intel.com>

On Wed, Nov 20, 2019 at 06:25:12PM +0200, Ville Syrjala wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> 
> Now that we've constrained the clipped source rectangle such
> that it can't have negative dimensions doing the same for the
> dst rectangle seems appropriate. Should at least result in
> the clipped src and dst rectangles being a bit more consistent
> with each other.
> 
> Cc: Benjamin Gaignard <benjamin.gaignard@st.com>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

selftests for this stuff? Looks like the prime example, write testcase
proving code is busted, fix it, everyone celebrate?
-Daniel

> ---
>  drivers/gpu/drm/drm_rect.c | 22 +++++++++++-----------
>  1 file changed, 11 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/gpu/drm/drm_rect.c b/drivers/gpu/drm/drm_rect.c
> index 7762b6e9278d..229325fcf333 100644
> --- a/drivers/gpu/drm/drm_rect.c
> +++ b/drivers/gpu/drm/drm_rect.c
> @@ -52,14 +52,14 @@ bool drm_rect_intersect(struct drm_rect *r1, const struct drm_rect *r2)
>  }
>  EXPORT_SYMBOL(drm_rect_intersect);
>  
> -static u32 clip_scaled(u32 src, u32 dst, u32 clip)
> +static u32 clip_scaled(int src, int dst, int *clip)
>  {
>  	u64 tmp;
>  
>  	/* Only clip what we have. Keeps the result bounded as well. */
> -	clip = min(clip, dst);
> +	*clip = min(*clip, dst);
>  
> -	tmp = mul_u32_u32(src, dst - clip);
> +	tmp = mul_u32_u32(src, dst - *clip);
>  
>  	/*
>  	 * Round toward 1.0 when clipping so that we don't accidentally
> @@ -92,34 +92,34 @@ bool drm_rect_clip_scaled(struct drm_rect *src, struct drm_rect *dst,
>  	diff = clip->x1 - dst->x1;
>  	if (diff > 0) {
>  		u32 new_src_w = clip_scaled(drm_rect_width(src),
> -					    drm_rect_width(dst), diff);
> +					    drm_rect_width(dst), &diff);
>  
>  		src->x1 = src->x2 - new_src_w;
> -		dst->x1 = clip->x1;
> +		dst->x1 += diff;
>  	}
>  	diff = clip->y1 - dst->y1;
>  	if (diff > 0) {
>  		u32 new_src_h = clip_scaled(drm_rect_height(src),
> -					    drm_rect_height(dst), diff);
> +					    drm_rect_height(dst), &diff);
>  
>  		src->y1 = src->y2 - new_src_h;
> -		dst->y1 = clip->y1;
> +		dst->y1 += diff;
>  	}
>  	diff = dst->x2 - clip->x2;
>  	if (diff > 0) {
>  		u32 new_src_w = clip_scaled(drm_rect_width(src),
> -					    drm_rect_width(dst), diff);
> +					    drm_rect_width(dst), &diff);
>  
>  		src->x2 = src->x1 + new_src_w;
> -		dst->x2 = clip->x2;
> +		dst->x2 -= diff;
>  	}
>  	diff = dst->y2 - clip->y2;
>  	if (diff > 0) {
>  		u32 new_src_h = clip_scaled(drm_rect_height(src),
> -					    drm_rect_height(dst), diff);
> +					    drm_rect_height(dst), &diff);
>  
>  		src->y2 = src->y1 + new_src_h;
> -		dst->y2 = clip->y2;
> +		dst->y2 -= diff;
>  	}
>  
>  	return drm_rect_visible(dst);
> -- 
> 2.23.0
> 
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/intel-gfx

-- 
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2019-11-20 16:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-20 16:25 [PATCH 1/2] drm/rect: Keep the scaled clip bounded Ville Syrjala
2019-11-20 16:25 ` Ville Syrjala
2019-11-20 16:25 ` [PATCH 2/2] drm/rect: Keep the clipped dst rectangle in place Ville Syrjala
2019-11-20 16:43   ` Daniel Vetter [this message]
2019-11-20 16:43     ` [Intel-gfx] " Daniel Vetter
2019-11-20 17:11     ` Ville Syrjälä
2019-11-20 19:55       ` Benjamin GAIGNARD
2019-11-20 19:55         ` [Intel-gfx] " Benjamin GAIGNARD
2019-11-22 17:25       ` Ville Syrjälä
2019-11-22 17:25         ` [Intel-gfx] " 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=20191120164340.GS30416@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=benjamin.gaignard@st.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=ville.syrjala@linux.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