nighty- has quit [Quit: Disappears in a puff of smoke]
aalm has quit [Ping timeout: 268 seconds]
BenG83_ has joined #linux-rockchip
afaerber has quit [Ping timeout: 260 seconds]
afaerber has joined #linux-rockchip
aalm has joined #linux-rockchip
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
perr has quit [Ping timeout: 240 seconds]
LargePrime has joined #linux-rockchip
kloczek has quit [Remote host closed the connection]
aaaa^ has joined #linux-rockchip
kloczek has joined #linux-rockchip
matthias_bgg has quit [Read error: Connection reset by peer]
matthias_bgg has joined #linux-rockchip
LargePrime has quit [Read error: Connection reset by peer]
perr has joined #linux-rockchip
perr has joined #linux-rockchip
aalm has quit [Ping timeout: 260 seconds]
alexneudatchin has quit [Ping timeout: 260 seconds]
matthias_bgg has quit [Ping timeout: 248 seconds]
cnxsoft has quit [Quit: cnxsoft]
kaspter has quit [Remote host closed the connection]
kaspter has joined #linux-rockchip
ganbold has joined #linux-rockchip
tllim has joined #linux-rockchip
aalm has joined #linux-rockchip
xerpi has joined #linux-rockchip
xerpi has quit [Quit: Leaving]
perr has quit [Quit: Leaving]
matthias_bgg has joined #linux-rockchip
matthias_bgg has quit [Ping timeout: 256 seconds]
Omegamoon has left #linux-rockchip [#linux-rockchip]
tl_lim has joined #linux-rockchip
tllim has quit [Ping timeout: 240 seconds]
tl_lim has quit [Ping timeout: 245 seconds]
tl_lim has joined #linux-rockchip
Easyfab has joined #linux-rockchip
vagrantc has joined #linux-rockchip
anarsoul|2 has joined #linux-rockchip
<vagrantc>
hverkuil1: simply blacklisting the fan53555 module made the firefly-rk3399 boot on my system
<vagrantc>
of course, then the A72 cores don't get working cpufreq...
<vagrantc>
so obviously this needs fixing in some other way
<hverkuil1>
vagrantc: ah, so that explains why the firefly is so slow?
<hverkuil1>
it's running at a slow frequency?
<vagrantc>
yeah, i believe the A72 cores are running at a default frequency (even slower than their normal slowest frequency.
<vagrantc>
i've found it to speed up by disabling the A72 cores in /sys
<vagrantc>
which is rather ironic, the A72 cores being the workhorses :)
* vagrantc
wonders if the scheduler is also scheduling the A72 cores with more work than the A53 cores ...
<maz>
the fun part is that even with the A72 at full speed, the scheduler doesn't know about the throughput difference.
<maz>
so you end-up with a completely erratic scheduling, and nothing works as it should.
<maz>
the joys of big.little
<vagrantc>
i guess there's a big.LITTLE scheduler to target that?
afaerber has quit [Quit: Leaving]
<hverkuil1>
after setting fcs,suspend-voltage-selector = <1>; in vdd_cpu_b in rk3399-firefly.dts I can enable fan53555 and boot.
<hverkuil1>
Everyone else had this set to 1, so I just tried it. I've no idea what it does, though :-)
<hverkuil1>
Hmm, it's a lot quicker now :-)
<hverkuil1>
fcs,suspend-voltage-selector: declare which of the two available voltage selector registers should be used for the suspend voltage. The other one is used for the runtime voltage setting
<vagrantc>
rtp: and look, maybe even a viable workaround/fix ^^
<hverkuil1>
I think it was set to the suspend voltage. That could explain a few things...
<hverkuil1>
but why did that end up in the dts?
<rtp>
vagrantc: yeah, and from what Hans pasted here I guess it's rather a fix than a workaround :)
* vagrantc
will test
<rtp>
hverkuil1: maybe platform specific in theory but due to cut&paste between rk3399 schematics, most of the board are needing to set it to 1 ?
<vagrantc>
if that's really a correct fix, would love to see it upstream
<hverkuil1>
No one else that uses fan53555 ever sets this to 0. rk3399-firefly was the only one that did this.