From mboxrd@z Thu Jan 1 00:00:00 1970 From: Robert Foss Subject: Re: rk3399: Graphical artifacts when running for-next Date: Fri, 22 Feb 2019 10:32:53 +0100 Message-ID: References: <69ddf17a-232d-fc1f-f6a7-59dbde220395@collabora.com> <2996476.nJxoliyDTa@phil> <48fe80bd-92bf-41fa-f508-941765e4354b@collabora.com> <1654246.IP1FNPqO5J@phil> <8d5e0ce1-b1c5-1f4b-fd81-f18f376fc756@collabora.com> <905cfe71-c98d-f73d-8870-623129b5e470@collabora.com> Mime-Version: 1.0 Content-Type: text/plain; charset="windows-1252"; Format="flowed" Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Language: en-US List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "Linux-rockchip" Errors-To: linux-rockchip-bounces+glpar-linux-rockchip=m.gmane.org-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org To: Jonas Karlman , Ezequiel Garcia , Heiko Stuebner Cc: "linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org" , Tom Cubie , Tomeu Vizoso List-Id: linux-rockchip.vger.kernel.org Hey again, I found the issue, and it has been solved by Ezequiel before me. A DDC I2C bus specifier is required for DDC EDID probing to work properly. https://www.spinics.net/lists/arm-kernel/msg708359.html Thanks for participating in this goose-chase with me. Rob. On 2/22/19 9:41 AM, Robert Foss wrote: > Hey Jonas, > = > On 2/21/19 9:29 PM, Jonas Karlman wrote: >> On 2019-02-21 20:42, Robert Foss wrote: >>> >>> On 2/21/19 8:15 PM, Ezequiel Garcia wrote: >>>> Folks, >>>> >>>> On Thu, 2019-02-21 at 20:08 +0100, Robert Foss wrote: >>>> [..] >>>> >>>> The clock debugging is obviously good research. >>>> >>>>>> >>>>>> Additionally I've had a look at the libdrm modetest util, and it is = reporting >>>>>> far fewer modes than what I would expect on my 4k monitor. >>>>>> >>>> That said, this is also worth looking into. >>>> I'm curious, is the EDID the kernel getting OK? >>>> >>> Given that modetest lists way too few modes, I would think >>> there could be some EDID related issues. >> >> It is more likely the issue is in dw_hdmi_rockchip_mode_valid(), it curr= ently = >> filters out >> any mode not defined in rockchip_mpll_cfg. >> That method needs some changes to allow for 4k modes and fractal refresh= rates. >> E.g. for RK3328 it should probably check the inno-hdmi-phy clock rates. > = > = > This seemed like a good suggetions, so I disabled the rockchip_mpll_cfg i= n = > dw_hdmi_rockchip_mode_valid(), and ran libdrm/modetest. I now have 5 mode= s. > But no higher resolution ones, only low resolution ones that don't seem > = > $ modetest > [..] > trying to open device 'rockchip'...done > Encoders: > id=A0=A0=A0=A0=A0 crtc=A0=A0=A0 type=A0=A0=A0 possible crtcs=A0 possible = clones > 44=A0=A0=A0=A0=A0 34=A0=A0=A0=A0=A0 TMDS=A0=A0=A0 0x00000003=A0=A0=A0=A0= =A0 0x00000000 > = > Connectors: > id=A0=A0=A0=A0=A0 encoder status=A0=A0=A0=A0=A0=A0=A0=A0=A0 name=A0=A0=A0= =A0=A0=A0=A0=A0=A0=A0=A0 size (mm)=A0=A0=A0=A0=A0=A0 modes=A0=A0 encoders > 45=A0=A0=A0=A0=A0 44=A0=A0=A0=A0=A0 connected=A0=A0=A0=A0=A0=A0 HDMI-A-1= =A0=A0=A0=A0=A0=A0=A0 0x0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 5=A0=A0=A0=A0= =A0=A0 44 > =A0 modes: > =A0=A0=A0=A0=A0=A0=A0 name refresh (Hz) hdisp hss hse htot vdisp vss vse= vtot) > =A0 1024x768 60 1024 1048 1184 1344 768 771 777 806 65000 flags: [..] > =A0 800x600 60 800 840 968 1056 600 601 605 628 40000 flags: [..] > =A0 800x600 56 800 824 896 1024 600 601 603 625 36000 flags: [..] > =A0 848x480 60 848 864 976 1088 480 486 494 517 33750 flags: [..] > =A0 640x480 60 640 656 752 800 480 490 492 525 25175 flags: [...]