<loki666>
Also Anbernic had multiple revision of their it would seems
<loki666>
1.5ghz was enabled in firsts FW and recently disabled
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
apritzel has quit [Quit: Leaving]
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
ftg has quit [Read error: Connection reset by peer]
warpme has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
<tokyovigilante>
wow, great news? Do you just want me to test this new patch?
<tokyovigilante>
sorry I didn't have a chance to look at your built images on the weekend
warpme has quit [Ping timeout: 480 seconds]
ity has quit [Ping timeout: 480 seconds]
ity has joined #linux-sunxi
flyback has quit [Ping timeout: 480 seconds]
<macromorgan>
I haven't figured out *how* yet, but it looks like commit e37ec3218870 ("mfd: axp20x: Allow multiple regulators") breaks CONFIG_AXP20X_ADC... at least according to git bisect
<macromorgan>
very simple digging into the iio framework I'm thinking it's more a matter of "it used to work, but it shouldn't have and now it's doing what it should"
flyback has joined #linux-sunxi
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
theslowcoder has quit [Ping timeout: 480 seconds]
theslowcoder has joined #linux-sunxi
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
parthiban has quit [Remote host closed the connection]
parthiban has joined #linux-sunxi
hexdump01 has joined #linux-sunxi
hexdump0815 has quit [Ping timeout: 480 seconds]
warpme has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
ity has quit [Remote host closed the connection]
ity has joined #linux-sunxi
warpme has quit [Read error: Connection timed out]
<loki666>
Yes please if you could both test the patch it would be great
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
<loki666>
Tokyovigilante the voltage values currently in mainline, how did you find them ?
<loki666>
Well voltage an freqs, I see that on the last Anbernic FW the 1.3ghz opp is enabled
<loki666>
But another in the range 900-1000Mhz (don't remember which one) is enabled in mainline but on Anbernic FW
<loki666>
^but not on
<loki666>
Do we know why Anbernic disabled 1.5Ghz? Heat concerns or instability? Instability could be due to their regulator-ramp-delay too low
<tokyovigilante>
ta, will do. Erm, mainly just from the anbernic FW, I just enabled a few extras and the 1.5GHz, which has always worked for me
<tokyovigilante>
maybe I just got lucky with my chip?
<tokyovigilante>
Do you want me to try the reparenting fix as well? Unless that made it to 6.13rc1. Which governors?
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme is now known as Guest2037
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
<loki666>
I don't think it as made it to 6.13rc1... I think it helps but is not required
<loki666>
So Anbernic never enabled 1.5Ghz ? It seems to also works fine on my devices, but maybe I'll flag it as turbo in ROCKNIX
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
<tokyovigilante>
The older FW had it enabled at release, which is where I took the 1.16v voltage from
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
immibis has joined #linux-sunxi
warpme has joined #linux-sunxi
tokyovigilante_ has joined #linux-sunxi
<loki666>
Ok thanks
tokyovigilante has quit [Ping timeout: 480 seconds]
<loki666>
Should we drop the 1032 opp (it's only for H700) and very close to 1008 opp (already enabled for H700)?
<loki666>
And I'd like to enable the 1320 opp for H700, using 1.1v
aggi has quit [Remote host closed the connection]
aggi has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Read error: Connection reset by peer]
<Soupborsh>
Hello, can you share some boot1.header binary? I want to find it on my emmc dump by comparing it.
<Soupborsh>
I found script.fex by searching in hexdump manually.
bauen1 has joined #linux-sunxi
ity has quit [Quit: WeeChat 4.4.4]
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
<macromorgan>
loki666: My money's on heat... I caused a thermal reboot multiple times (at least according to dmesg) when doing `stress-ng -c 4`
<loki666>
Ok so maybe it should also be flagged as turbo in mainline
<loki666>
turbo is for opp that can be enabled for a "short" period of time
<loki666>
Bah I'll post a patch and we'll see how it goes
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
Schimsalabim has quit [Read error: Connection reset by peer]
Schimsalabim has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
Guest2059 has quit []
warpme has joined #linux-sunxi
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
vagrantc has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit [Ping timeout: 480 seconds]
warpme has joined #linux-sunxi
warpme has quit []
warpme has joined #linux-sunxi
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
<macromorgan>
okay I think I know why that commit broke the battery/usb charger driver when in ADC mode... looking at the MFD code it looks like the device ID is set as the same as the parent if you don't tell it PLATFORM_DEVID_AUTO, which is exactly what that commit did.
<macromorgan>
so now it can no longer find the ADC channel and dies
<macromorgan>
what I need to do to fix it is add some sort of helper to find the ADC child when looking at the parent node and direct it there
ftg has joined #linux-sunxi
Hypfer is now known as Guest2078
Hypfer has joined #linux-sunxi
Guest2078 has quit [Read error: Connection reset by peer]
warpme has quit [Quit: My MacBook Air has gone to sleep. ZZZzzz…]