On Mon, Nov 07, 2016 at 10:20:53PM +0200, [email protected] wrote:
> From: Ville Syrjälä <[email protected]>
>
> Starting from commit b63a16f6cd89 ("drm/i915: Compute display surface
> offset in the plane check hook for SKL+") we've already rotated the src
> coordinates by 270 degrees by the time we check if a scaler is needed
> or not, so we must not account for the rotation a second time.
> Previously we did these steps in the opposite order and hence the
> scaler check had to deal with rotation itself. The double rotation
> handling causes us to enable a scaler pretty much every time 90/270
> degree plane rotation is requested, leading to fuzzier fonts and whatnot.
>
> Cc: Sivakumar Thulasimani <[email protected]>
> Cc: Tvrtko Ursulin <[email protected]>
> Cc: [email protected]
> Reported-by: Tvrtko Ursulin <[email protected]>
> Fixes: b63a16f6cd89 ("drm/i915: Compute display surface offset in the plane
> check hook for SKL+")
> Signed-off-by: Ville Syrjälä <[email protected]>
I believe
Tested-by: Tvrtko Ursulin <[email protected]>
skl_plane_downscale_amount() ?
skl_plane_relative_data_rate() ?
skl_ddb_min_alloc()
skl_compute_plane_wm()
What's the best way of keeping the reader aware of whether or not the
coordinate transform has been applied? Similar to how to let the user
know the rect is in fixed_16_16 or int32.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
_______________________________________________
Intel-gfx mailing list
[email protected]
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
