Attachment 131279 Details for Bug 100919 – 2nd attempt at patch

[patch] 2nd attempt at patch

0001-drm-amd-display-Keep-DVI_SINGLE_LINK-signal-if-low-c.patch (text/plain), 1.41 KB, created by Harry Wentland on 2017-05-09 17:40:38 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Harry Wentland

Created: 2017-05-09 17:40:38 UTC

Size: 1.41 KB

patch

obsolete

>From c0bdede92d687b98a43455027a7e610d4419baba Mon Sep 17 00:00:00 2001
>From: Harry Wentland <harry.wentland@amd.com>
>Date: Tue, 9 May 2017 10:41:42 -0400
>Subject: [PATCH] drm/amd/display: Keep DVI_SINGLE_LINK signal if low clk
>
>If user is using DVI->HDMI dongle dual link signal might pose a
>problem. Keep single link signal type if clk is lower than
>max tmds clk.
>
>Change-Id: I6ad1009bb195e0d1ba91a9801c6125778419f739
>Signed-off-by: Harry Wentland <harry.wentland@amd.com>
>---
> drivers/gpu/drm/amd/display/dc/core/dc_resource.c | 9 ++++++---
> 1 file changed, 6 insertions(+), 3 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 2de86f8364a3..b1fce534bf69 100644
>--- a/drivers/gpu/drm/amd/display/dc/core/dc_resource.c
>+++ b/drivers/gpu/drm/amd/display/dc/core/dc_resource.c
>@@ -1264,9 +1264,12 @@ static void update_stream_signal(struct core_stream *stream)
> 		stream->signal = stream->public.output_signal;
> 	}
> 
>-	if (stream->signal == SIGNAL_TYPE_DVI_SINGLE_LINK &&
>-		stream->public.timing.pix_clk_khz > TMDS_MAX_PIXEL_CLOCK_IN_KHZ)
>-		stream->signal = SIGNAL_TYPE_DVI_DUAL_LINK;
>+	if (dc_is_dvi_signal(stream->signal)) {
>+		if (stream->public.timing.pix_clk_khz > TMDS_MAX_PIXEL_CLOCK_IN_KHZ)
>+			stream->signal = SIGNAL_TYPE_DVI_DUAL_LINK;
>+		else
>+			stream->signal = SIGNAL_TYPE_DVI_SINGLE_LINK;
>+	}
> }
> 
> bool resource_is_stream_unchanged(
>-- 
>2.11.0
>

Actions: View | Splinter Review

Attachments on bug 100919: 131274 | 131276 | 131279

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.