diff options
Diffstat (limited to 'meta-amd-bsp/recipes-kernel/linux/linux-yocto-4.14.71/2588-drm-amd-display-Correct-timings-in-build-scaling-par.patch')
| -rw-r--r-- | meta-amd-bsp/recipes-kernel/linux/linux-yocto-4.14.71/2588-drm-amd-display-Correct-timings-in-build-scaling-par.patch | 53 |
1 files changed, 53 insertions, 0 deletions
diff --git a/meta-amd-bsp/recipes-kernel/linux/linux-yocto-4.14.71/2588-drm-amd-display-Correct-timings-in-build-scaling-par.patch b/meta-amd-bsp/recipes-kernel/linux/linux-yocto-4.14.71/2588-drm-amd-display-Correct-timings-in-build-scaling-par.patch new file mode 100644 index 00000000..ddbd6cfc --- /dev/null +++ b/meta-amd-bsp/recipes-kernel/linux/linux-yocto-4.14.71/2588-drm-amd-display-Correct-timings-in-build-scaling-par.patch @@ -0,0 +1,53 @@ +From 576e50bcf58410331419d06391546d2fed183f13 Mon Sep 17 00:00:00 2001 +From: Andrew Jiang <Andrew.Jiang@amd.com> +Date: Tue, 10 Oct 2017 14:36:39 -0400 +Subject: [PATCH 2588/4131] drm/amd/display: Correct timings in build scaling + params + +A previous patch set the addressable timing as active + border, +when in fact, the VESA standard specifies active as equal to +addressable + border. + +This patch makes the fix more correct and in line with the standard. + +Signed-off-by: Andrew Jiang <Andrew.Jiang@amd.com> +Reviewed-by: Andrew Jiang <Andrew.Jiang@amd.com> +Reviewed-by: Tony Cheng <Tony.Cheng@amd.com> +Acked-by: Harry Wentland <Harry.Wentland@amd.com> +--- + drivers/gpu/drm/amd/display/dc/core/dc_resource.c | 17 +++-------------- + 1 file changed, 3 insertions(+), 14 deletions(-) + +diff --git a/drivers/gpu/drm/amd/display/dc/core/dc_resource.c b/drivers/gpu/drm/amd/display/dc/core/dc_resource.c +index 55feb16..0aca7a3 100644 +--- a/drivers/gpu/drm/amd/display/dc/core/dc_resource.c ++++ b/drivers/gpu/drm/amd/display/dc/core/dc_resource.c +@@ -850,22 +850,11 @@ bool resource_build_scaling_params(struct pipe_ctx *pipe_ctx) + */ + pipe_ctx->plane_res.scl_data.lb_params.depth = LB_PIXEL_DEPTH_30BPP; + +- /** +- * KMD sends us h and v_addressable without the borders, which causes us sometimes to draw +- * the blank region on-screen. Correct for this by adding the borders back to their +- * respective addressable values, and by shifting recout. +- */ +- timing->h_addressable += timing->h_border_left + timing->h_border_right; +- timing->v_addressable += timing->v_border_top + timing->v_border_bottom; +- pipe_ctx->plane_res.scl_data.recout.y += timing->v_border_top; + pipe_ctx->plane_res.scl_data.recout.x += timing->h_border_left; +- timing->v_border_top = 0; +- timing->v_border_bottom = 0; +- timing->h_border_left = 0; +- timing->h_border_right = 0; ++ pipe_ctx->plane_res.scl_data.recout.y += timing->v_border_top; + +- pipe_ctx->plane_res.scl_data.h_active = timing->h_addressable; +- pipe_ctx->plane_res.scl_data.v_active = timing->v_addressable; ++ pipe_ctx->plane_res.scl_data.h_active = timing->h_addressable + timing->h_border_left + timing->h_border_right; ++ pipe_ctx->plane_res.scl_data.v_active = timing->v_addressable + timing->v_border_top + timing->v_border_bottom; + + /* Taps calculations */ + if (pipe_ctx->plane_res.xfm != NULL) +-- +2.7.4 + |