From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 105302] [DC] - Maximum pixel clock of dual-link DVI too low for some modes Date: Thu, 01 Mar 2018 05:34:04 +0000 Message-ID: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1774334996==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [IPv6:2610:10:20:722:a800:ff:fe98:4b55]) by gabe.freedesktop.org (Postfix) with ESMTP id 5C2E06EBE2 for ; Thu, 1 Mar 2018 05:34:04 +0000 (UTC) List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1774334996== Content-Type: multipart/alternative; boundary="15198824440.94Ae0.5850" Content-Transfer-Encoding: 7bit --15198824440.94Ae0.5850 Date: Thu, 1 Mar 2018 05:34:04 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D105302 Bug ID: 105302 Summary: [DC] - Maximum pixel clock of dual-link DVI too low for some modes Product: DRI Version: DRI git Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/AMDgpu Assignee: dri-devel@lists.freedesktop.org Reporter: asheldon55@gmail.com I have a monitor that supports 2560x1440 >60hz (up to around 110hz) through= the DVI-D interface but requires pixel clocks greater than the current dual-link limit of 330khz, with amdgpu.dc=3D1. Setting TMDS_MAX_PIXEL_CLOCK to 250000= in signal_types.h works around the problem.=20 amdgpu.dc=3D0 doesn't appear to have this limit (or the value is higher) so= the problem does not exist there. I'm using ~ag5df's drm-next-4.17-wip branch. There appears to be a discussion about setting a higher pixel clock limit in this bug: https://bugs.freedesktop.org/show_bug.cgi?id=3D93885 but focused = on HDMI and not DVI-D, and regarding the older radeon driver. --=20 You are receiving this mail because: You are the assignee for the bug.= --15198824440.94Ae0.5850 Date: Thu, 1 Mar 2018 05:34:04 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated
Bug ID 105302
Summary [DC] - Maximum pixel clock of dual-link DVI too low for some = modes
Product DRI
Version DRI git
Hardware x86-64 (AMD64)
OS Linux (All)
Status NEW
Severity normal
Priority medium
Component DRM/AMDgpu
Assignee dri-devel@lists.freedesktop.org
Reporter asheldon55@gmail.com 

I have a monitor that supports 2560x1440 >60hz (up to aroun=
d 110hz) through the
DVI-D interface but requires pixel clocks greater than the current dual-link
limit of 330khz, with amdgpu.dc=3D1. Setting TMDS_MAX_PIXEL_CLOCK to 250000=
 in
signal_types.h works around the problem.=20

amdgpu.dc=3D0 doesn't appear to have this limit (or the value is higher) so=
 the
problem does not exist there.

I'm using ~ag5df's drm-next-4.17-wip branch.

There appears to be a discussion about setting a higher pixel clock limit in
this bug: https://bugs.freedesktop.org/show_bug.c=
gi?id=3D93885 but focused on
HDMI and not DVI-D, and regarding the older radeon driver.

You are receiving this mail because:
  • You are the assignee for the bug.
= --15198824440.94Ae0.5850-- --===============1774334996== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1774334996==--