ChanServ changed the topic of #linux-sunxi to: Allwinner/sunxi development - Did you try looking at our wiki? https://linux-sunxi.org - Don't ask to ask. Just ask and wait for an answer! - This channel is logged at https://oftc.irclog.whitequark.org/linux-sunxi
<MoeIcenowy> apritzel: does H616 come with different bins?
<apritzel> MoeIcenowy: I don't know, but warpme_ seems to build on this assumption ...
<apritzel> I just wanted to test that setting the PLL_CPUX to 1.8GHz works, and it does
<apritzel> some OPPs are twice in the BSP DT, so I think there is something to pick the right one at runtime
ftg has quit [Read error: Connection reset by peer]
vagrantc has quit [Quit: leaving]
apritzel has quit [Ping timeout: 480 seconds]
Mangy_Dog has quit [Ping timeout: 480 seconds]
hexdump01 has joined #linux-sunxi
hexdump0815 has quit [Ping timeout: 480 seconds]
gediz0x539 has joined #linux-sunxi
apritzel has joined #linux-sunxi
hlauer has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
tnovotny has joined #linux-sunxi
cmeerw has joined #linux-sunxi
cmeerw has quit [Ping timeout: 480 seconds]
indy has quit [Read error: Connection reset by peer]
indy has joined #linux-sunxi
apritzel has joined #linux-sunxi
<evadot> mhm, anyone familiar with the a64 thermal ?
<evadot> with a 24mhz clock and a thermal_per of 244 I get an data interrupt at ~1sec rate
<evadot> so does the thermal generate an interrupts every 4 samples and not for each one ?
Mangy_Dog has joined #linux-sunxi
<evadot> mhm, the filter was set to 8, so that doesn't explain the behavior I'm seeing ...
<evadot> setting it to 4 gives me an interrupts at a ~500ms rate
choozy has joined #linux-sunxi
<warpme_> MoeIcenowy: apritzel: re: q about "does H616 come with different bins?" - yes. i'm assuming that as bsp read sid for bin (https://github.com/orangepi-xunlong/linux-orangepi/blob/06f40bef0d9a08c233b4b2ed6f9064c3abe3ecb6/arch/arm64/boot/dts/sunxi/sun50i-h616-orangepi-zero2.dts#L5421)
<warpme_> apritzel: re:" your q about "did you see this of_device_is_compatible() call in sun50i-cpufreq-nvmem.c?" - yes. i added compatible: https://github.com/warpme/minimyth2/blob/7898f5b61979fd63e346bd10d0dd72903fdd9dc7/script/kernel/linux-5.13/files/0571-drivers-thermal-allwinner-add-h616-ths-support.patch#L20
<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)
<warpme_> hmm: interesting (re aw859a wifi):
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)
libv has joined #linux-sunxi
<apritzel> warpme_: cool, thanks, looks good
<warpme_> oh - i see i choose wrong profession.....
libv_ has quit [Ping timeout: 480 seconds]
hlauer has quit [Ping timeout: 480 seconds]
<apritzel> warpme_: I measure 1.13V (with my lousy equipment) when in the 1,5GHz@1.12V pstate
<apritzel> warpme_: did you adjust the dcdca max voltage and also referenced dcdca as the "cpu-supply"?
ftg has joined #linux-sunxi
<warpme_> apritzel: i think so: https://github.com/warpme/minimyth2/blob/7898f5b61979fd63e346bd10d0dd72903fdd9dc7/script/kernel/linux-5.13/files/0597-arm64-dts-allwinner-h616-enable-ths-support.patch#L295 But it looks i lost dcdca as the "cpu-supply" in my patches. After disabling sun5i-cpufreq-nvmem and adjusting cpu-supply in dt it started to work :-) (so far tested 1.5G opp but it should be ok also with higher opps i think). many
<warpme_> many thanx for great help!
<warpme_> 1.8G opp also work nice!
sunshavi has quit [Ping timeout: 480 seconds]
vagrantc has joined #linux-sunxi
choozy has quit [Quit: https://quassel-irc.org - Chat comfortably. Anywhere.]
cmeerw has quit [Ping timeout: 480 seconds]
sunshavi has joined #linux-sunxi
libv has quit [Ping timeout: 480 seconds]
libv has joined #linux-sunxi