Attachment 142347 Details for Bug 108577 – possible fix 1/2

[patch] possible fix 1/2

0001-drm-amdgpu-display-check-if-fbc-is-available-in-set_.patch (text/plain), 1.35 KB, created by Alex Deucher on 2018-11-02 15:56:15 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Alex Deucher

Created: 2018-11-02 15:56:15 UTC

Size: 1.35 KB

patch

obsolete

>From ca2f6ad754d82bc5a44c206d98da439bf3f6d3e0 Mon Sep 17 00:00:00 2001
>From: Alex Deucher <alexander.deucher@amd.com>
>Date: Fri, 2 Nov 2018 10:51:50 -0500
>Subject: [PATCH 1/2] drm/amdgpu/display: check if fbc is available in
> set_static_screen_control
>
>The value is dependent on whether fbc is available.
>
>Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
>---
> drivers/gpu/drm/amd/display/dc/dce110/dce110_hw_sequencer.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
>diff --git a/drivers/gpu/drm/amd/display/dc/dce110/dce110_hw_sequencer.c b/drivers/gpu/drm/amd/display/dc/dce110/dce110_hw_sequencer.c
>index 4789270c29d9..6c9299e33f34 100644
>--- a/drivers/gpu/drm/amd/display/dc/dce110/dce110_hw_sequencer.c
>+++ b/drivers/gpu/drm/amd/display/dc/dce110/dce110_hw_sequencer.c
>@@ -1738,6 +1738,7 @@ static void get_position(struct pipe_ctx **pipe_ctx,
> static void set_static_screen_control(struct pipe_ctx **pipe_ctx,
> 		int num_pipes, const struct dc_static_screen_events *events)
> {
>+	struct dc *dc = pipe_ctx[0]->stream->ctx->dc;
> 	unsigned int i;
> 	unsigned int value = 0;
> 
>@@ -1750,7 +1751,8 @@ static void set_static_screen_control(struct pipe_ctx **pipe_ctx,
> 	if (events->force_trigger)
> 		value |= 0x1;
> 
>-	value |= 0x84;
>+	if (dc->fbc_compressor)
>+		value |= 0x84;
> 
> 	for (i = 0; i < num_pipes; i++)
> 		pipe_ctx[i]->stream_res.tg->funcs->
>-- 
>2.13.6
>

Actions: View | Splinter Review

Attachments on bug 108577: 142239 | 142250 | 142286 | 142292 | 142293 | 142334 | 142347 | 142348 | 142350 | 142351 | 142374 | 142382 | 142384 | 142396 | 143006

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.