ChanServ changed the topic of #linux-rockchip to: Rockchip development discussion | IRC log http://irclog.whitequark.org/linux-rockchip | Community GH https://github.com/linux-rockchip | Rockchip GH https://github.com/rockchip-linux | ML https://groups.google.com/group/linux-rockchip
field^Mop has quit [Ping timeout: 256 seconds]
kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
kaspter has quit [Excess Flood]
kaspter has joined #linux-rockchip
vstehle has quit [Ping timeout: 256 seconds]
warpme_ has quit [Quit: Connection closed for inactivity]
kaspter has quit [Ping timeout: 246 seconds]
kaspter has joined #linux-rockchip
<wens> mmind00: could you re-review my pcie gpio changes again? # https://lore.kernel.org/linux-arm-kernel/20210106134617.391-2-wens@kernel.org/
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 264 seconds]
kevery1 is now known as kevery
kaspter has quit [Ping timeout: 264 seconds]
kaspter has joined #linux-rockchip
rtp has quit [Ping timeout: 240 seconds]
rtp has joined #linux-rockchip
vstehle has joined #linux-rockchip
s_frit has joined #linux-rockchip
camus has joined #linux-rockchip
kaspter has quit [Ping timeout: 264 seconds]
camus is now known as kaspter
kevery1 has joined #linux-rockchip
kevery has quit [Read error: Connection reset by peer]
kevery1 is now known as kevery
alpernebbi has joined #linux-rockchip
kevery1 has joined #linux-rockchip
kevery has quit [Read error: Connection reset by peer]
kevery1 is now known as kevery
paulk-leonov has quit [Ping timeout: 260 seconds]
paulk-leonov has joined #linux-rockchip
warpme_ has joined #linux-rockchip
paulk-leonov has quit [Remote host closed the connection]
paulk-leonov has joined #linux-rockchip
stikonas has joined #linux-rockchip
stikonas has quit [Remote host closed the connection]
stikonas has joined #linux-rockchip
manawyrm has joined #linux-rockchip
<paulk-leonov> hi, I'm seeing lots of freezes on the px30 with v5.11-rc, usually with this: https://paste.debian.net/1181723/
<paulk-leonov> and sometimes this as well:
<paulk-leonov> rockchip-vop ff460000.vop: [drm:vop_crtc_atomic_flush] *ERROR* VOP vblank IRQ stuck for 10 ms
matthias_bgg has joined #linux-rockchip
<paulk-leonov> I don't really have time to investigate it, but wanted to quickly report it though
kevery1 has joined #linux-rockchip
kevery has quit [Ping timeout: 272 seconds]
kevery1 is now known as kevery
_whitelogger has joined #linux-rockchip
<nergzd723> I have one question: is rk30sdk in parm mean that my tablet is based on that rk30sdk board?
<nergzd723> stock parm report rk30sdk, but I still can't boot any kernel, the bootloader refuses to build my boot.imgs
<nergzd723> * stock parm report rk30sdk, but I still can't boot any kernel, the bootloader refuses to boot my boot.imgs
hipboi has left #linux-rockchip [#linux-rockchip]
hipboi has joined #linux-rockchip
gavlee has quit [*.net *.split]
tomeu has quit [*.net *.split]
dlezcano has quit [*.net *.split]
marvs has quit [*.net *.split]
mmind00 has quit [*.net *.split]
leming has quit [*.net *.split]
leming has joined #linux-rockchip
tomeu has joined #linux-rockchip
marvs has joined #linux-rockchip
mmind00 has joined #linux-rockchip
gavlee has joined #linux-rockchip
<mmind00> paulk-leonov: strange, I'm running 5.11-rc with my rkisp tests and didn't notice any hangs so far ... did you enable some new drivers or something?
<paulk-leonov> mmind00: I just rebased my hantro h264 encoding work but that's about it
<paulk-leonov> defconfig is https://paste.debian.net/1181741/
<mmind00> paulk-leonov: while working on the isp I once caused such a stuck vop-blank irq when I caused an interrupt storm from the isp ... so maybe that is something related?
<mmind00> especially as I don't think much changed in drm-land for 5.11
<paulk-leonov> mhh ok, I'll check that
kaspter has quit [Quit: kaspter]
chewitt has joined #linux-rockchip
field^Mop has joined #linux-rockchip
Kelsar has quit [Quit: http://quassel-irc.org - Chat comfortably. Anywhere.]
Kelsar has joined #linux-rockchip
putti_ is now known as Putti
kevery has quit [Remote host closed the connection]
kevery has joined #linux-rockchip
field^Mop has quit [Ping timeout: 240 seconds]
marvs has quit [Ping timeout: 265 seconds]
alpernebbi has quit [Quit: alpernebbi]
<ukleinek> in U-Boot, I assume arch/arm/dts/rk3399-kobol-helios64-u-boot.dtsi and arch/arm/dts/rk3399-kobol-helios64.dts are merged to get the device tree for U-Boot?!
<robmur01> yes, IIRC there's some build magic to automatically inject any *-u-boot fragments that exist
Esmil has joined #linux-rockchip
ldevulder_ has joined #linux-rockchip
ldevulder has quit [Ping timeout: 256 seconds]
<ukleinek> hmm, helios64 U-Boot doesn't come up with the mainline dts :-\
* ukleinek guesses he has to add quite some regulators
<ukleinek> on the other hand, the exception seems to be a NULL pointer ...
* ukleinek looks for something like initcall_debug in U-Boot
field^Mop has joined #linux-rockchip
hexdump0815 has joined #linux-rockchip
<hexdump0815> Ashleee: just to continue at the proper channel - i saw your notes from a ew days ago ... i guess too that its simply bad or rotten memory - but maybe this way its at least useable with mem=2048M :)
<Ashleee> I mean if it boots into whole 4 gigs it seems stable enough even around 3.2GB mark... I did get the sporadical EL3 uncaught exception here and there but when I actually try to replicate it it works fine :D
<Ashleee> I did get the EL3 exception even with 2GB though so who knows
<Ashleee> I could probably try replacing the rkbin trust with upstream ATF
<Ashleee> but something something lazy :
<Ashleee> :D
<Ashleee> it survived 100% CPU load for about 15 hours so good enough for me
Net147 has quit [Quit: Quit]
Net147 has joined #linux-rockchip
<hexdump0815> Ashleee: if you are using the legacy trust i think you'll have to define a protected mem region for it in the dtb - otherwise you might get sporadic crashes i think
<Ashleee> oh!
<Ashleee> got any more info about that?
<hexdump0815> something like this: https://github.com/hexdump0815/linux-mainline-and-mali-rockchip-rk33xx-kernel/blob/master/misc.rkc/dtb/rk3318-h96max.dts#L18-L31 - there are some links to my sources back then in it
<Ashleee> thanks! :) I didn't see any reserved regions in original stock DTBs
kevery1 has joined #linux-rockchip
<hexdump0815> not sure how it is on rk3399, but i guess it might make sense to search for more info about that maybe
kevery has quit [Ping timeout: 246 seconds]
kevery1 is now known as kevery
<Ashleee> I mean the linked pages speak of rk3399 :)
<Ashleee> which is *the* chip on mine
<Ashleee> will poke it tomorrow, thanks again!
<hexdump0815> looking forward for your results - good luck!
<Ashleee> I will poke the built-in LEDs as well >:D :D
<hexdump0815> ;)
matthias_bgg has quit [Quit: Leaving]
hexdump0815 has quit [Quit: Connection closed]
field^Mop has quit [Ping timeout: 272 seconds]
Net147 has quit [Quit: Quit]
Net147 has joined #linux-rockchip
<robmur01> Ashleee: indeed the carveout for the OP-TEE secure memory isn't normally described in stock DTBs; the downstream U-Boot just removes a hard-coded region from the DT memory node before passing it to the kernel
mraynal has quit [Remote host closed the connection]
<robmur01> heh, this is where I usually go and dig up the ML thread where I debugged it, but I see hexdump has the lore link already, neat!
mraynal has joined #linux-rockchip