evgeny_boger has quit [Read error: Connection reset by peer]
evgeny_boger1 has joined #linux-sunxi
reasonx has joined #linux-sunxi
evgeny_boger1 has quit [Ping timeout: 480 seconds]
tnovotny has joined #linux-sunxi
pg12_ has quit []
pg12 has joined #linux-sunxi
junari_ has joined #linux-sunxi
junari__ has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
gamiee has quit [Read error: Connection reset by peer]
bauen1 has quit [Ping timeout: 480 seconds]
juri_ has joined #linux-sunxi
tnovotny has quit [Ping timeout: 480 seconds]
tnovotny has joined #linux-sunxi
bauen1 has joined #linux-sunxi
junari__ has joined #linux-sunxi
junari_ has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has quit []
tnovotny has quit [Quit: Leaving]
grming has joined #linux-sunxi
ndufresne has quit [Excess Flood]
ndufresne has joined #linux-sunxi
cnxsoft has quit []
codekipper has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
codekipper has joined #linux-sunxi
cnxsoft has joined #linux-sunxi
sunshavi_ has quit [Ping timeout: 480 seconds]
sunshavi_ has joined #linux-sunxi
cnxsoft has quit []
codekipper has quit [Ping timeout: 480 seconds]
sunshavi_ has quit [Read error: Connection reset by peer]
sunshavi_ has joined #linux-sunxi
junari__ has quit [Ping timeout: 480 seconds]
vagrantc has joined #linux-sunxi
sunshavi_ has quit [Read error: Connection reset by peer]
sunshavi_ has joined #linux-sunxi
apritzel has quit [Ping timeout: 480 seconds]
hlauer has joined #linux-sunxi
DarkNeutrino has joined #linux-sunxi
<DarkNeutrino>
@apritzel do you want me to send a V7 for the 313a with the ordering fixed ? And do we have time to make it into 6.3 ?
ftg has joined #linux-sunxi
JohnDoe_71Rus has quit []
apritzel has joined #linux-sunxi
<apritzel>
DarkNeutrino: yes, we need to resend
<apritzel>
and I don't know about 6.3, but it looks pretty tight now
<DarkNeutrino>
Im playing with HDMI. Will make it compile and will send V7
<apritzel>
thanks!
apritzel has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
<DarkNeutrino>
Well it would not be me if i didnt screw up 1 thing. Wanted to send it also to my gmail. Yea gmail.org *laugh*
apritzel has quit [Ping timeout: 480 seconds]
apritzel has joined #linux-sunxi
DarkNeutrino has quit [Quit: Quit]
DarkNeutrino has joined #linux-sunxi
<DarkNeutrino>
apritzel: So rather interesting thing just showed up.
<DarkNeutrino>
[ 0.572053] axp20x-regulator axp20x-regulator: DCDC frequency on AXP313a is fixed to 3 MHz. [ 0.572084] axp20x-regulator axp20x-regulator: Error setting dcdc frequency: -22
<DarkNeutrino>
Im checking at what its set here
<DarkNeutrino>
But im 99% sure this didnt show up with the preview
<DarkNeutrino>
Its 0 for me :|
<apritzel>
it's a dev_err() output, but not fatal, right? So the driver still works?
<DarkNeutrino>
Yea
<DarkNeutrino>
SDcard still showed up so driver still works
<apritzel>
DarkNeutrino: I see that we should also accept 0, as that's the default setting, as delivered by probe(), and also handled like this for the other PMICs
<DarkNeutrino>
I agree. I will send v8 tommorow.
<apritzel>
if (dcdcfreq == 0) dcdcfreq = def;
<apritzel>
yeah, give it at least a day, in case someone wants to comment
<DarkNeutrino>
def is not set thou. So we will need to set def to 3Mhz
<apritzel>
(I would typically wait at least two days)
<apritzel>
we don't need def, since we bail out before that's used
<DarkNeutrino>
Wait. Now im kinda lost
<apritzel>
axp20x_set_dcdc_freq() is called from parse_dt(), with the value read from the DT property
<apritzel>
if there is no property in the DT (your case, I'd guess), then it stays at 0, as initialised
<apritzel>
all other PMICs then set "def" in axp20x_set_dcdc_freq(), and use that, in case the input freq was 0
<DarkNeutrino>
Ah gotcha. So we just add || dcdcfreq != 0
<apritzel>
but we end our switch-case with a "return 0;", so never reach that code
<apritzel>
exactly
<DarkNeutrino>
OK. I mean we are already pretty tight in for 6.3 so i think we can wait the 2 days and send v8 then. Its unlikely we would make it either way.
<DarkNeutrino>
But this board is giving so many weird issues. As soon as i run init script i get a lovely [ 2.583043] Unable to handle kernel NULL pointer dereference at virtual address 0000000000000008
<apritzel>
does that happen consistently?
<DarkNeutrino>
Yep
<apritzel>
*random* NULL pointer deref's are typically DRAM issues
<apritzel>
and is that just with mainline, or does that happen with BIQU's kernel/firmware as well?
<DarkNeutrino>
BIQU image is fine
<DarkNeutrino>
I will try their uboot and see
<DarkNeutrino>
Yea thats not good. Happens with their u-boot as well
hlauer has quit [Ping timeout: 480 seconds]
ftg has quit [Read error: Connection reset by peer]