From mboxrd@z Thu Jan 1 00:00:00 1970 From: Heiko Stuebner Subject: Re: rk3399: Graphical artifacts when running for-next Date: Thu, 21 Feb 2019 14:26:35 +0100 Message-ID: <2996476.nJxoliyDTa@phil> References: <69ddf17a-232d-fc1f-f6a7-59dbde220395@collabora.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <69ddf17a-232d-fc1f-f6a7-59dbde220395-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org> 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: Robert Foss Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org, Tom Cubie , Tomeu Vizoso List-Id: linux-rockchip.vger.kernel.org Hi Robert, Am Donnerstag, 21. Februar 2019, 11:27:15 CET schrieb Robert Foss: > Hey Heiko, > > I've just started booting the RK3399 based Radxa Rock Pi 4 on the mainline > kernel. Specifically on linux-rockchip/for-next, with an additional patch > adding the GPU DT node[1]. > > Unfortunately I'm seeing an artifact on all display output[2]. > It, from the VT to 3D content. > > Is this an issue that has been encountered before? I haven't seen something like this before. I do test graphics on most Rockchip socs regularly (right now dw-hdmi only on non-rk3399 socs though). Did you try full linux-next as well? My for-next branch obviously only carries dt/soc-driver stuff but not things like drm-misc. One possible issue might be the generated clocks. You could check $debug/clk/clk_summary for the dclk_vopX to see if that matches the suggested clock for the mode. (For example check the requested rate in rockchip_vop.c against what it actually gets). Heiko > [1] https://patchwork.kernel.org/patch/10817637/mbox/ > [2] https://photos.app.goo.gl/ArffJ3785JSeQatW7 > > > Rob. >