<fraolt>
If that's also the case for the A64, that might explain why running PLL_GPU at 240MHz in order to run the GPU at 120MHz doesn't work.
<fraolt>
But, even more interesting: According to the A64 manual, PLL_GPU doesn't even support dynamic frequency scaling.
<fraolt>
Does that mean that the 3 OPPs (120, 312, 432 MHZ) in the A64 DTS should be dropped and the frequency should be set to a fixed value in ccu-sun50i-a64.c?
apritzel has joined #linux-sunxi
<Jookia>
Ok, I solved the clock issue: I was very confused. Allowins I2S2 to set the parent clock solves my issue, but I can also use fractional dividers correctly
apritzel has quit [Ping timeout: 480 seconds]
ftg has joined #linux-sunxi
jernej_ is now known as jernej
<jernej>
fraolt: no, that just mean GPU shouldn't process any task while switching frequency
<jernej>
I think
<jernej>
anyway, you can dig out BSP code for frequency setup and compare process to mainline
<jernej>
it's hidden in utgard driver, under platform dependent code
<jernej>
that's also the place where I found frequency table
stockhausen has joined #linux-sunxi
stockhausen has left #linux-sunxi [#linux-sunxi]
vistefan has joined #linux-sunxi
<fraolt>
jernej: I found the frequency table in the BSP sunxi driver. You mean there's another one for utgard?
<fraolt>
Ok, and lima takes care that a new OPP is only selected if there is no job, right?
<jernej>
where exactly did you find frequency table? under modules/ ?
<jernej>
tbh, I don't know when lima switches frequency
f_ has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
f_ has joined #linux-sunxi
machinehum has joined #linux-sunxi
ftg has quit [Ping timeout: 480 seconds]
ftg has joined #linux-sunxi
warpme has quit []
machinehum has quit [Ping timeout: 480 seconds]
machinehum has joined #linux-sunxi
warpme has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
machinehum has quit [Ping timeout: 480 seconds]
warpme has quit []
<fraolt>
PINE A64 BSP 4.9 lichee/linux-4.9/drivers/clk/sunxi/clk-sun50iw1_tbl.c