warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Stat_headcrabbed has joined #linux-rockchip
stikonas has joined #linux-rockchip
naoki has quit [Quit: naoki]
warpme has joined #linux-rockchip
stikonas has quit [Quit: Konversation terminated!]
naoki has joined #linux-rockchip
naoki has quit [Client Quit]
Stat_headcrabbed has quit [Remote host closed the connection]
Stat_headcrabbed has joined #linux-rockchip
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
xha has quit [Quit: WeeChat 4.4.4]
xha has joined #linux-rockchip
Stat_headcrabbed has joined #linux-rockchip
Stat_headcrabbed has quit [Client Quit]
Stat_headcrabbed has joined #linux-rockchip
raster has joined #linux-rockchip
raster has quit [Quit: Gettin' stinky!]
warpme has joined #linux-rockchip
vagrantc has joined #linux-rockchip
vagrantc has quit [Ping timeout: 252 seconds]
stikonas has joined #linux-rockchip
Stat_headcrabbed has quit [Remote host closed the connection]
Stat_headcrabbed has joined #linux-rockchip
Stat_headcrabbed has quit [Client Quit]
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
LordKalma has quit [Quit: Server has probably crashed]
LordKalma has joined #linux-rockchip
LordKalma has quit [Client Quit]
LordKalma has joined #linux-rockchip
LordKalma has quit [Client Quit]
LordKalma has joined #linux-rockchip
<Kwiboo>
look like scmi clocks are broken for rk3576, linux and tf-a seem to use use different clock indices :-S, e.g. ARMCLK_L in linux = 7 and in tf-a = 10, so linux will request change cpu rate and tf-a change and report rate for gpll instead..., similar for gpu clock 448 vs 456
<CounterPillow>
RK3588 had similar troubles I think
<Kwiboo>
yeah, I was supprised to see <&scmi_clk CLK_GPU> and not a <&scmi_clk SCMI_CLK_GPU> in linux DT for rk3576, was wondering if it was typo, now look like SCMI clock specific indices never was used for rk3576 and instead regular cru clock id is being used
warpme has joined #linux-rockchip
warpme has quit [Client Quit]
raster has joined #linux-rockchip
LordKalma has quit [Quit: Ping timeout (120 seconds)]
LordKalma has joined #linux-rockchip
Stat_headcrabbed has joined #linux-rockchip
krei-se has quit [Excess Flood]
krei-se has joined #linux-rockchip
Stat_headcrabbed has quit [Quit: Stat_headcrabbed]
MyNetAz has quit [Remote host closed the connection]
<diederik>
The commit description mentions "Same as RK3568 ... ", but in rk356x-base.dtsi only cpu0 has ``clocks = <&scmi_clk 0>``, but none of the other cpu nodes
<diederik>
Is that an error/omission in rk356x-base.dtsi or is it 'entirely' different?
Jookia has left #linux-rockchip [#linux-rockchip]
warpme has joined #linux-rockchip
warpme has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
franoosh has joined #linux-rockchip
warpme has joined #linux-rockchip
warpme has quit [Client Quit]
raster has quit [Quit: Gettin' stinky!]
vagrantc has joined #linux-rockchip
<Kwiboo>
diederik: all cores will run at the same speed on those socs, at least for runtime it does not seem to matter that much if only one of all cores have clocks and cpu-supply, for proper hw description I think all cores should have a clocks/cpu-supply props, who knows :-)
<CounterPillow>
Kwiboo: wrt RK3576 SCMI clocks, I'll look into this tomorrow. sre is busy with EW so I'll probably just be bold and send a patch myself. This would explain why the GPU was so slow for me though lol
<Kwiboo>
CounterPillow: great!, hehe, yeah I can imagine there currently being some unexpected behaviors :-D
<Kwiboo>
diederik: just at a first glance I think it is strange that the npu_pvtpll_table is missing e.g. the 100MHz rate that is listed in rk3568_gpu_rates, also look like the code will select 100MHz for gpu and npu when going to suspend, not sure it is related but suspicious
<Kwiboo>
above applies to both gpu/npu
<diederik>
thanks for the hint :)
<Kwiboo>
diederik: also look like at resume it will restore rate that has been set, and npu clock may not have been set at all, so could be worth seeing if the rates is initialized propertly
<Kwiboo>
look like it should not harm if rate = 0 so probably not an issue
<diederik>
One thing Shengfei Xu (xsf) suggested was to add regulator-always-on and -boot-on to the DT. But apart from me not liking that (which is not a real argument), the thing that bothers me is that it does work with rkbin components
<diederik>
So he thinks the problem is with the kernel, but I suspect it's probably (also) with the TF-A patch itself
franoosh has quit [Remote host closed the connection]