stikonas has quit [Remote host closed the connection]
matthias_bgg has quit [Quit: Leaving]
vstehle has quit [Ping timeout: 246 seconds]
camus1 has joined #linux-rockchip
kaspter has quit [Ping timeout: 246 seconds]
camus1 is now known as kaspter
kevery has quit [Ping timeout: 256 seconds]
kevery has joined #linux-rockchip
robmur01 has joined #linux-rockchip
robmur01 has quit [Ping timeout: 258 seconds]
kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
nlhowell has joined #linux-rockchip
lerc has joined #linux-rockchip
_whitelogger has joined #linux-rockchip
vstehle has joined #linux-rockchip
adjtm has quit [Remote host closed the connection]
JohnDoe_71Rus has joined #linux-rockchip
adjtm has joined #linux-rockchip
vicencb has joined #linux-rockchip
jaganteki has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
<obbardc>
nomis, robmur01: i've got issues with rk3328 flickering display at 1080p. have you seen that?
robmur01 has joined #linux-rockchip
robmur01_ has joined #linux-rockchip
robmur01 has quit [Ping timeout: 256 seconds]
robmur01_ is now known as robmur01
lkcl_ has joined #linux-rockchip
lkcl__ has quit [Ping timeout: 265 seconds]
kevery1 has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 260 seconds]
kevery has quit [Ping timeout: 256 seconds]
kevery1 is now known as kevery
matthias_bgg has joined #linux-rockchip
<obbardc>
robmur01: following rk3328 discussion, i've got issues with rk3328 flickering display over HDMI 1080p at 60Hz when the system is loaded with mainline (but not vendor kernel)
<robmur01>
obbardc: not something I've ever noticed - in fact to confirm I just kicked mine off flat-out on all 4 CPUs (rebuilding mesa) while running kmscube on my 1080p60 TV, and everything's just fine
<obbardc>
hm, mine flickers while running weston on wayland and openbox on xorg
<obbardc>
on both rock64 and a SOM i've ported
stikonas has joined #linux-rockchip
<obbardc>
armbian image for rock64 also shows the same flickering
<robmur01>
have you tried different displays? Some can be pickier than others about clock rates
<robmur01>
urjaman: aw yeah! `perf bench mem` really makes it spaz out
<robmur01>
so it does look like scanout starvation rather than sync going marginal
<obbardc>
fwiw i was using `stress --vm 10`
<urjaman>
obbardc: yeah i'd check if the vendor kernel does something like that
<robmur01>
downstream certainly has a bunch of DVFS stuff for the VDD_LOGIC domain and memory, wouldn't be surprised if it's poking QoS from the kernel as well
<Kwiboo>
obbardc: you may need to use higher VOP clk rate like https://patchwork.kernel.org/patch/11324807/, I have not seen an issue with 1080p60hz earlier but a similar issue can be seen with 4k resolutions
<obbardc>
Kwiboo: I've tried your patch series
<obbardc>
it improves things but not that much
<Kwiboo>
ahh, I have not tried to use dvfs on mainline yet, but I can remember trying to have vdd_logic below 1.1v have caused stability issues for me in the past
<Kwiboo>
also I have mainly used vendor u-boot + atf on my rk3328 boards and have not really touched any of them for the last few months
<obbardc>
will have a look, with dvfs vdd_logic is 0.71v-1.45v
<Kwiboo>
on vendor kernel there is gpu, dmc, vdec and possible some other node providing opp table and all sharing vdd_logic, so lowest voltage is usually higher then for any single table
<Kwiboo>
at least that was my experiance when I first tried to bring in gpu opp table from vendor to mainline long time ago, ended up with just using default vdd_logic and force 500mhz gpu clk rate instead
<Kwiboo>
obbardc: the safe range on rk3328 for vdd_logic is 0.9-1.15v and for vdd_arm 0.95-1.35v according to datasheet and replies from RK engineers on mailinglist
<obbardc>
fwiw i have just tested vendor kernelvdd_logic is fixed at 1.1v, vdd_arm is 0.95-1.307v from 600-1300MHz
<obbardc>
and on mainline vdd_logic is 1.097v and vdd_arm is fixed to 1.317v
<Kwiboo>
I think there is a vop hw bug that shows up with similar symptoms as in your video, but that is related to scaling down 4k frame buffers to 1080p, you do not happen to use a framebuffer that is 3840w
<obbardc>
xrandr says Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 4096 x 4096
_whitelogger has joined #linux-rockchip
leah2 has quit [Ping timeout: 265 seconds]
leah2 has joined #linux-rockchip
kevery has joined #linux-rockchip
nlhowell has quit [Ping timeout: 265 seconds]
midnight has quit [Ping timeout: 272 seconds]
anarsoul has quit [Ping timeout: 264 seconds]
anarsoul has joined #linux-rockchip
kevery has quit [Remote host closed the connection]