lopsided98 has quit [Quit: No Ping reply in 180 seconds.]
lopsided98 has joined #linux-rockchip
stikonas has joined #linux-rockchip
kevery has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 256 seconds]
matthias_bgg has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 260 seconds]
kevery1 is now known as kevery
matthias_bgg has quit [Ping timeout: 256 seconds]
matthias_bgg has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 256 seconds]
nlhowell has quit [Ping timeout: 240 seconds]
field^Zzz1 has joined #linux-rockchip
mickenx has joined #linux-rockchip
<mickenx>
hoa
<mickenx>
can someone here explain what aclk do with vop0?
<mickenx>
I mean the frequency
<mickenx>
the relation
<mickenx>
on rk3399
<mickenx>
If I leave it in reset values I get half of vpll (vpll is used for pixelcklock)
<robmur01>
aclk is usually the device's AXI clock, i.e. controlling its interface to memory, and thus effectively its maximum memory bandwidth
<mickenx>
the result with that is unpredictable
<mickenx>
ah ok
<mickenx>
I get a sort of striped display , and if I cpll and set it to 400 it gets even more striped
<robmur01>
naively, that being some fraction of the pixel clock seems reasonable - you only need to be able to scan out memory fast enough to push the pixels out the other end
<mickenx>
cpll for apll
<mickenx>
ok
<mickenx>
then reset values should be ok
<robmur01>
for a "typical" resolution and BPP, I'd expect so
<mickenx>
my test case is 800x600 60Hz
<mickenx>
so pixelclock is 40Mhz
<mickenx>
but I get a random behaviour , somtimes i get perfect image and sometimes not (striped)
nlhowell has joined #linux-rockchip
nlhowell has quit [Ping timeout: 256 seconds]
matthias_bgg has joined #linux-rockchip
vagrantc has joined #linux-rockchip
jlanda_ has joined #linux-rockchip
jlanda has quit [Remote host closed the connection]
<mickenx>
robmur01: reset values make thick lines horisontal, and the usual vertical stripes
<mickenx>
if i set div to 1 , it works sometimes
<robmur01>
sounds like it's probably just too slow
<robmur01>
reset values also run the A72 cluster at 12MHz ;)
<mickenx>
yea
<mickenx>
that is fixed
<mickenx>
:)
<mickenx>
I have tried with cpll for the aclk setting, boosting it
<mickenx>
but no luck
<PPA>
Is there a fix for the RK3399's resolution capping at 1080p on mainline?
<fALSO>
from what i've tested
<fALSO>
it doesnt "get" the resolutions from the monitor
<fALSO>
it it didnt
<fALSO>
dont know if its fixed
<fALSO>
but i managed to force it with xrandr
<fALSO>
to 2560x1080
<fALSO>
i think
<robmur01>
the HDMI driver has a very limited set of exact pixel clocks that it supports, so a lot of modes that aren't standard TV resolutions get rejected
<fALSO>
EDID or something
<PPA>
I was using a 1920x1200 monitor; didn't try xrandr though, only xfce's menu settings. I'm going to try the former next time.
<robmur01>
I tried hacking in 154MHz for my 1920x1200 monitor to run at native res, which works OK on RK3399 but is glitchy as hell on RK3288
<fALSO>
its funny that 2020 linux still doesnt have a graphical standard tool
<fALSO>
to set the X resolution
<fALSO>
:-P
<robmur01>
funny that in 2020 X is still a thing :P
<fALSO>
well it works, contrary or other stuff that red hat is forcing
<PPA>
robmur01: by modifying a file in the kernel during build?