Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: ville.syrjala@linux.intel.com
To: intel-gfx@lists.freedesktop.org
Cc: dri-devel@lists.freedesktop.org
Subject: [PATCH v2 6/6] drm/i915: Relax the sprite scaling limits checks
Date: Wed, 24 Apr 2013 18:52:39 +0300	[thread overview]
Message-ID: <1366818759-8707-7-git-send-email-ville.syrjala@linux.intel.com> (raw)
In-Reply-To: <1366818759-8707-1-git-send-email-ville.syrjala@linux.intel.com>

From: Ville Syrjälä <ville.syrjala@linux.intel.com>

Reduce the size of the the src/dst viewport to keep the scalign ratios
in check.

v2: Below min size sprite handling squashed to previous patch

Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
 drivers/gpu/drm/i915/intel_sprite.c | 48 +++++++++++++++++++++----------------
 1 file changed, 28 insertions(+), 20 deletions(-)

diff --git a/drivers/gpu/drm/i915/intel_sprite.c b/drivers/gpu/drm/i915/intel_sprite.c
index 044cc263..27cb14a 100644
--- a/drivers/gpu/drm/i915/intel_sprite.c
+++ b/drivers/gpu/drm/i915/intel_sprite.c
@@ -681,26 +681,19 @@ intel_update_plane(struct drm_plane *plane, struct drm_crtc *crtc,
 			return -EINVAL;
 	}
 
+	/*
+	 * FIXME the following code does a bunch of fuzzy adjustments to the
+	 * coordinates and sizes. We probably need some way to decide whether
+	 * more strict checking should be done instead.
+	 */
 	max_scale = intel_plane->max_downscale << 16;
 	min_scale = intel_plane->can_scale ? 1 : (1 << 16);
 
-	hscale = drm_rect_calc_hscale(&src, &dst, min_scale, max_scale);
-	if (hscale < 0) {
-		DRM_DEBUG_KMS("Horizontal scaling factor out of limits\n");
-		drm_rect_debug_print(&src, true);
-		drm_rect_debug_print(&dst, false);
+	hscale = drm_rect_calc_hscale_relaxed(&src, &dst, min_scale, max_scale);
+	BUG_ON(hscale < 0);
 
-		return hscale;
-	}
-
-	vscale = drm_rect_calc_vscale(&src, &dst, min_scale, max_scale);
-	if (vscale < 0) {
-		DRM_DEBUG_KMS("Vertical scaling factor out of limits\n");
-		drm_rect_debug_print(&src, true);
-		drm_rect_debug_print(&dst, false);
-
-		return vscale;
-	}
+	vscale = drm_rect_calc_vscale_relaxed(&src, &dst, min_scale, max_scale);
+	BUG_ON(vscale < 0);
 
 	visible = drm_rect_clip_scaled(&src, &dst, &clip, hscale, vscale);
 
@@ -710,6 +703,25 @@ intel_update_plane(struct drm_plane *plane, struct drm_crtc *crtc,
 	crtc_h = drm_rect_height(&dst);
 
 	if (visible) {
+		/* check again in case clipping clamped the results */
+		hscale = drm_rect_calc_hscale(&src, &dst, min_scale, max_scale);
+		if (hscale < 0) {
+			DRM_DEBUG_KMS("Horizontal scaling factor out of limits\n");
+			drm_rect_debug_print(&src, true);
+			drm_rect_debug_print(&dst, false);
+
+			return hscale;
+		}
+
+		vscale = drm_rect_calc_vscale(&src, &dst, min_scale, max_scale);
+		if (vscale < 0) {
+			DRM_DEBUG_KMS("Vertical scaling factor out of limits\n");
+			drm_rect_debug_print(&src, true);
+			drm_rect_debug_print(&dst, false);
+
+			return vscale;
+		}
+
 		/* Make the source viewport size an exact multiple of the scaling factors. */
 		drm_rect_adjust_size(&src,
 				     drm_rect_width(&dst) * hscale - drm_rect_width(&src),
@@ -726,10 +738,6 @@ intel_update_plane(struct drm_plane *plane, struct drm_crtc *crtc,
 		 * Adjust to (macro)pixel boundary, but be careful not to
 		 * increase the source viewport size, because that could
 		 * push the downscaling factor out of bounds.
-		 *
-		 * FIXME Should we be really strict and reject the
-		 * config if it results in non (macro)pixel aligned
-		 * coords?
 		 */
 		src_x = src.x1 >> 16;
 		src_w = drm_rect_width(&src) >> 16;
-- 
1.8.1.5

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2013-04-24 15:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 15:52 [PATCH 0/6] drm: drm_rect and clipping for intel sprite planes v2 ville.syrjala
2013-04-24 15:52 ` [PATCH v5 1/6] drm: Add struct drm_rect and assorted utility functions ville.syrjala
2013-04-24 15:52 ` [PATCH v4 2/6] drm: Add drm_rect_calc_{hscale, vscale}() " ville.syrjala
2013-04-24 15:52 ` [PATCH v3 3/6] drm: Add drm_rect_debug_print() ville.syrjala
2013-04-24 15:52 ` [PATCH 4/6] drm: Add drm_rect_equals() ville.syrjala
2013-04-24 15:52 ` [PATCH v6 5/6] drm/i915: Implement proper clipping for video sprites ville.syrjala
2013-04-24 15:52 ` ville.syrjala [this message]
2013-04-30 20:18 ` [PATCH 0/6] drm: drm_rect and clipping for intel sprite planes v2 Daniel Vetter

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=1366818759-8707-7-git-send-email-ville.syrjala@linux.intel.com \
    --to=ville.syrjala@linux.intel.com \
    --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