<apritzel>
jernej: so PHY write training is not really working, or is not tested, that's why you remove it?
<jernej>
it is just copy from h616, which don't work here
<apritzel>
looks quite good after a first glance, really like it
digetx has joined #linux-sunxi
elias has joined #linux-sunxi
elias has quit []
eliasbakken has joined #linux-sunxi
vagrantc has joined #linux-sunxi
<eliasbakken>
Has anyone played around with the CPUS on the T527? It's not well documented, but it seems there is a OR1000-style CPU buried in there. I've tried poking around the reset register for the CPUS from a booted board, but it leads to an instant freeze.
psydroid has joined #linux-sunxi
dsimic is now known as Guest8057
dsimic has joined #linux-sunxi
Guest8057 has quit [Ping timeout: 480 seconds]
linkmauve has left #linux-sunxi [Error from remote client]
apritzel has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
sporewoh has joined #linux-sunxi
sporewoh has quit [Remote host closed the connection]
<eliasbakken>
Right, so am I right in assuming that there is an ARISC present? The user manual seems to place the ARSIC and the RISCV both in the CPUS domain, so I'm guessing they might share the same peripheral bus or something. There is also an SCP.bin file in the Orange Pi 4A Debian distro, so it seems to be loaded. Where would the code to do an AR100 reset be located? Is that in u-boot?
<loki666>
apritzel: I'm having a similar issue with GPU (G31) as I had with the CPU: unstable when running a dynamic freq governor. It seems pretty stable when running powersave or perf, but panfros does some oops when running simple_ondemand gov
<loki666>
could it be that devfreq doesn't honor the ramp delay ?
<loki666>
mmmh, no... on a second thought it can't be that as all opp use the same voltage...
Turl has quit [Ping timeout: 480 seconds]
<apritzel>
also devfreq would just use the regulator framework, which would handle the ramp delay
<apritzel>
loki666: I guess we need some reparenting and re-locking as done for the CPU PLL, see the end of sun50i_h616_ccu_probe() in the clock driver
<apritzel>
eliasbakken: we are pretty sure that there is an ARISC, since there is OpenRISC code in the BSP firmware
<apritzel>
eliasbakken: the code to release the ARISC from reset would probably be in TF-A, at least I haven't seen anything in Syterkit
<apritzel>
loki666: the manual doesn't even mention frequency scaling for GPU_PLL (in contrast to the H6, for instance), so we really need to reparent the GPU clock over frequency changes
<macromorgan>
I can give a belated tested by I suppose... I can try to review it but considering I'm 100% self taught it might be a review of dubious quality
<apritzel>
I don't think there is anyone professionally educated for display engine review anywhere ;-)