All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael Röding" <michael.roeding-Dmr80ijK6QUttERQvd4Cp4QuADTiUCJX@public.gmane.org>
To: Heiko Stuebner <heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org>,
	Robert Foss <robert.foss-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
Cc: linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
	Tom Cubie <tom-ZvE2cuBqvIQAvxtiuMwx3w@public.gmane.org>,
	Tomeu Vizoso
	<tomeu.vizoso-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
Subject: Re: rk3399: Graphical artifacts when running for-next
Date: Thu, 21 Feb 2019 16:30:02 +0100	[thread overview]
Message-ID: <6f235348-ffa8-6caa-21ab-bfe28be6ddff@ruhr-uni-bochum.de> (raw)
In-Reply-To: <2996476.nJxoliyDTa@phil>

Hi Robert and Heiko,

On 21.02.19 14:26, Heiko Stuebner wrote:
> 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).

for the record: I've seen exactly the same as Heiko on my Rock Pi 4 A
(2GB) using stock Arch Linux ARM Kernel (4.20.11) using dts from "arm64:
dts: rockchip: add ROCK Pi 4 DTS support" (v1 though).

As the dts is for 5.1, i was expecting some minor problems. But since
Heiko had the exact same artifacts i though i let you know that not him
alone.

Michael

> 
> 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.
>>
> 
> 
> 
> 
> 
> _______________________________________________
> Linux-rockchip mailing list
> Linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
> http://lists.infradead.org/mailman/listinfo/linux-rockchip
> 

  reply	other threads:[~2019-02-21 15:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 10:27 rk3399: Graphical artifacts when running for-next Robert Foss
     [not found] ` <69ddf17a-232d-fc1f-f6a7-59dbde220395-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2019-02-21 13:26   ` Heiko Stuebner
2019-02-21 15:30     ` Michael Röding [this message]
2019-02-21 15:46     ` Robert Foss
     [not found]       ` <48fe80bd-92bf-41fa-f508-941765e4354b-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2019-02-21 15:53         ` Heiko Stuebner
2019-02-21 16:38           ` Robert Foss
     [not found]             ` <ec6768e8-c6ce-b4e6-10b6-2880dbbdff4d-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2019-02-21 19:08               ` Robert Foss
     [not found]                 ` <8d5e0ce1-b1c5-1f4b-fd81-f18f376fc756-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2019-02-21 19:15                   ` Ezequiel Garcia
     [not found]                     ` <eaec0319d2a79a49a39fc29bfe2473f2cec15b52.camel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2019-02-21 19:42                       ` Robert Foss
     [not found]                         ` <905cfe71-c98d-f73d-8870-623129b5e470-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2019-02-21 20:29                           ` Jonas Karlman
     [not found]                             ` <AM3PR03MB096698953B17A52CA58EF251AC7E0-XQTXrJX/giFAc9da7WRX18eAHadYHfrlvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2019-02-22  8:41                               ` Robert Foss
     [not found]                                 ` <cc5be462-6684-f945-bee9-5b583aee6f37-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2019-02-22  8:45                                   ` Robert Foss
     [not found]                                     ` <d0d37ca1-4afb-8ee2-f648-5a42879900de-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2019-02-22  9:30                                       ` Jonas Karlman
     [not found]                                         ` <AM3PR03MB096678395D7722EDCF81E775AC7F0-XQTXrJX/giFAc9da7WRX18eAHadYHfrlvxpqHgZTriW3zl9H0oFU5g@public.gmane.org>
2019-02-22 10:56                                           ` Robert Foss
2019-02-22  9:32                                   ` Robert Foss
     [not found]                                     ` <ea326f10-51ea-f673-b3fc-8dcc403249ba-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2019-02-22  9:38                                       ` Heiko Stuebner
2019-02-22 11:02                                         ` Robert Foss
     [not found]                                           ` <9c26c9bb-19e0-9d91-8466-8a7480f1ea13-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2019-02-22 11:14                                             ` Heiko Stuebner
2019-02-22 12:24                                             ` Ezequiel Garcia
2019-02-21 21:48               ` Heiko Stuebner
2019-02-21 21:52                 ` Ezequiel Garcia
     [not found]                   ` <2aa6011a4bd85573c659fd960d0071718b73e39c.camel-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org>
2019-02-21 22:07                     ` Heiko Stuebner
2019-02-25 18:00                 ` Doug Anderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6f235348-ffa8-6caa-21ab-bfe28be6ddff@ruhr-uni-bochum.de \
    --to=michael.roeding-dmr80ijk6qutterqvd4cp4quadtiucjx@public.gmane.org \
    --cc=heiko-4mtYJXux2i+zQB+pC5nmwQ@public.gmane.org \
    --cc=linux-rockchip-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
    --cc=robert.foss-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
    --cc=tom-ZvE2cuBqvIQAvxtiuMwx3w@public.gmane.org \
    --cc=tomeu.vizoso-ZGY8ohtN/8qB+jHODAdFcQ@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.