<evadot>
meh ok, my calculation were all wrong :) I got it now
<MoeIcenowy>
warpme_: strange it's the lowest 16bits of the first word of chipid
<MoeIcenowy>
maybe similar to H2+/H3, bin info is in chipid?
<warpme_>
MoeIcenowy: honestly: idk. but printk shows read value is 0. how you conclude that it is first word of chipid? Generally: my logic was quite simple (and mayby wrong): there is efuse and @00 addr. there is value saying what bin is...
<MoeIcenowy>
warpme_: well just because it's an offset
<MoeIcenowy>
and it's little endian
<warpme_>
but imho this shouldn't causing kernel trap issue i have on sun5i-cpufreq-nvmem right? In my both devices read value is 0 - so we are asked to use speebin0 from opp table - or i'm wrong? (we can investigate this later - when somebody better than me will review patches)
jakllsch has quit [Remote host closed the connection]
jakllsch has joined #linux-sunxi
jakllsch has quit [Ping timeout: 480 seconds]
jakllsch has joined #linux-sunxi
gediz0x539 has quit [Quit: Leaving]
<warpme_>
apritzel: jernej: just fyi: i measured cpu_vdd on opi-zero2 and for 1.3G opp it should be 1120mV but is 912mV. this explain why i can't get any opp over 1.3GHz. What will be your suggestion here?
<apritzel>
warpme_: is there any easily accessible test point for the voltage? at some coil, maybe?
<apritzel>
and what is your workload? Do you just switch to 1.3GHz and let it idle?
cmeerw has joined #linux-sunxi
tnovotny has quit []
<warpme_>
apritzel: yes. let me try to depict this :-)
<warpme_>
workload is idle. yes - i set higher opp to 1.3G & set governor to performance
<apritzel>
so I used pure cpufreq-dt yesterday, and ran hackbench for a few minutes (loadavg goes into the 100s), at 1.8GHz (verified) and 1.12V (programmed, but not verified)