anarsoul has quit [Remote host closed the connection]
anarsoul has joined #linux-rockchip
j45 has joined #linux-rockchip
field^Zzz3 has joined #linux-rockchip
field^Zzz2 has quit [Ping timeout: 260 seconds]
lkcl has quit [Ping timeout: 260 seconds]
lkcl has joined #linux-rockchip
vagrantc has quit [Quit: leaving]
kaspter has quit [Ping timeout: 256 seconds]
kaspter has joined #linux-rockchip
vstehle has joined #linux-rockchip
lkcl has quit [Ping timeout: 260 seconds]
lkcl has joined #linux-rockchip
gendevbot has quit [Remote host closed the connection]
lkcl has quit [Ping timeout: 260 seconds]
lopsided98 has quit [Ping timeout: 260 seconds]
lopsided98 has joined #linux-rockchip
lkcl has joined #linux-rockchip
kevery has quit [Quit: kevery]
lkcl has quit [Ping timeout: 246 seconds]
lkcl has joined #linux-rockchip
camus1 has joined #linux-rockchip
kaspter has quit [Remote host closed the connection]
camus1 is now known as kaspter
ldevulder_ is now known as ldevulder
lkcl has quit [Ping timeout: 272 seconds]
lkcl has joined #linux-rockchip
kevery has joined #linux-rockchip
camus1 has joined #linux-rockchip
kaspter has quit [Remote host closed the connection]
camus1 is now known as kaspter
vicencb has joined #linux-rockchip
matthias_bgg has joined #linux-rockchip
<paulk-leonov>
hi
<paulk-leonov>
it looks like we're having issues using vpu encode + vpu decode + VIP (camera in) + RGA at the same time (at about 30 fps for PAL dimensions)
<paulk-leonov>
does that ring a bell to anyone ?
chewitt has joined #linux-rockchip
stikonas has joined #linux-rockchip
steev has quit [Ping timeout: 244 seconds]
steev has joined #linux-rockchip
narmstrong has quit [Ping timeout: 260 seconds]
narmstrong has joined #linux-rockchip
alpernebbi has joined #linux-rockchip
<mmind00>
paulk-leonov: at least no bell here ... but I guess what are the issues that you see?
<paulk-leonov>
mmind00: it's a FIFO overflow on the VIP side
matthias_bgg has quit [Ping timeout: 264 seconds]
matthias_bgg has joined #linux-rockchip
matthias_bgg has quit [Quit: Leaving]
<robmur01>
I'd guess at interconnect QoS (and maybe interconnect/memory clocks in general)
<robmur01>
on RK3328 in its default state you can glitch the display simply by doing something memory-intensive on the CPUs :)
matthias_bgg has joined #linux-rockchip
<paulk-leonov>
ah ok so that does happen :)
<robmur01>
No idea what the default priorities are or how you change them though - AFAIK Rockchip don't use our interconnects (other than the CCI in RK3399) so I can't even point at vague suggestions :(
<mmind00>
there are the quality-of-service syscons in the dts ... though right now we're only saving and restoring them on power-domain changes
<robmur01>
yeah, it's just a question of whether the TRM tells you enough about how to actually program them
shailangsa has joined #linux-rockchip
<robmur01>
(also, why oh why oh why does the EL3 firmware that's supposed to be responsible for all power state stuff not handle that save/restore? Grrr...)
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
lkcl has quit [Ping timeout: 246 seconds]
ldevulder_ has joined #linux-rockchip
chewitt has quit [Read error: Connection reset by peer]
chewitt has joined #linux-rockchip
ldevulder has quit [Ping timeout: 256 seconds]
lkcl has joined #linux-rockchip
stikonas has joined #linux-rockchip
niceplace has quit [Ping timeout: 264 seconds]
JohnDoe_71Rus has joined #linux-rockchip
vagrantc has joined #linux-rockchip
Kwiboo has joined #linux-rockchip
<dlezcano->
mmind00, mani_s, the rock960 does no longer boot correctly, (stuck but no hang) since v5.10-rc2 (-rc1 does not compile), is the issue known ?
vicencb has quit [Quit: Leaving.]
<mmind00>
dlezcano-: not that I know of ... at which point is it stuck?
<mmind00>
dlezcano-: i.e. any kernel output?
<robmur01>
apparently something broke RK808 probing briefly, that could possibly be involved
<mmind00>
dlezcano-: "Waiting for root device /dev/mmcblk1p2..." ... I'd say ... there is a mmc change that pretty much causes all mmc hosts to reorder
<dlezcano->
mmind00, mmh :/
<mmind00>
dlezcano-: so your mmcblk1 is most likely a mmcblk0 or something now