Attachment 123022 Details for Bug 94528 – Patch to fix this HDMI no display issue

Patch to fix this HDMI no display issue

0001-Fix-VX900-HDMI-port-no-display-issue.patch (text/plain), 1.40 KB, created by HuangRan on 2016-04-18 08:25:13 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: HuangRan

Created: 2016-04-18 08:25:13 UTC

Size: 1.40 KB

patch

obsolete

>From 99bd260384f03bf5b2f5bbd2b4a0bc8cd4b14fe8 Mon Sep 17 00:00:00 2001
>From: HuangRan <huangranbj@126.com>
>Date: Mon, 18 Apr 2016 15:52:56 +0800
>Subject: [PATCH] Fix VX900 HDMI port no display issue
>
>Remove the write of bit6 for VGA/SVGA CRT Controller Register 0xFD(IGA1
>Scaling Up and Timing Control). Bit6 of CRTC 0xFD is RO bit which can
>not be written. Verfied on VX900 board for HDMI port.
>
>Signed-off-by: Hu, Yi<huyi@iscas.ac.cn>
>Signed-off-by: Huang, Ran<huangranbj@126.com>
>---
> drivers/gpu/drm/via/via_crtc.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
>diff --git a/drivers/gpu/drm/via/via_crtc.c b/drivers/gpu/drm/via/via_crtc.c
>index fa29270..a50e654 100644
>--- a/drivers/gpu/drm/via/via_crtc.c
>+++ b/drivers/gpu/drm/via/via_crtc.c
>@@ -468,7 +468,7 @@ void via_load_crtc_pixel_timing(struct drm_crtc *crtc, struct drm_display_mode *
> 		svga_wcrt_mask(VGABASE, 0x32, 0x00, BIT(2));
> 
> 	}
>-	svga_wcrt_mask(VGABASE, 0xFD, BIT(5) | BIT(6), BIT(5) | BIT(6));
>+	svga_wcrt_mask(VGABASE, 0xFD, BIT(5), BIT(5));
> }
> 
> /* Load CRTC timing registers */
>@@ -484,7 +484,7 @@ void via_load_crtc_timing(struct via_crtc *iga, struct drm_display_mode *mode)
> 			svga_wcrt_mask(VGABASE, 0x45, 0x00, BIT(0));
> 
> 			/* Disable IGA1 pixel timing */
>-			svga_wcrt_mask(VGABASE, 0xFD, 0x00, BIT(6) | BIT(5));
>+			svga_wcrt_mask(VGABASE, 0xFD, 0x00, BIT(5));
> 		}
> 
> 		reg_value = IGA1_HOR_TOTAL_FORMULA(mode->crtc_htotal);
>-- 
>1.9.1
>

Actions: View

Attachments on bug 94528: 122272 | 123022 | 123040 | 123083

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.