<loki666>
looks like a A527 handheld comming my way
<loki666>
hopefully, the uart pads will be predilled, and I won't make a mess like the A133P
Daanct12 has quit [Quit: WeeChat 4.6.1]
<gamiee>
loki666: is there A527 based handheld?
<loki666>
from Helegaly
ungeskriptet has quit [Read error: No route to host]
mripard has quit [Read error: Connection reset by peer]
mripard has joined #linux-sunxi
cnxsoft has quit [Ping timeout: 480 seconds]
JohnDoe_71Rus has joined #linux-sunxi
bauen1 has quit [Ping timeout: 480 seconds]
aggi has quit [Ping timeout: 480 seconds]
dsimic is now known as Guest13710
dsimic has joined #linux-sunxi
Guest13710 has quit [Ping timeout: 480 seconds]
Schimsalabim has quit [Ping timeout: 480 seconds]
Schimsalabim has joined #linux-sunxi
aggi has joined #linux-sunxi
<montjoie>
I dont see a527 in uboot, does I search badly ?
<Lightsword>
apritzel, is there any documentation or something for the i2c3 bus and what's actually required for it to come up? in Linux at least I'm not seeing any reason it shouldn't work but keep seeing "i2c i2c-1: mv64xxx: I2C bus locked, block: 1, time_left: 0" errors
<apritzel>
if all goes well, I might be able to merge it in the next two or three weeks
<apritzel>
some feedback would help, and I would need Signed-off-by:s from jernej on his patches (hint hint)
<jernej>
apritzel: I'll trade SoFs for my DT patches reviews ;)
<jernej>
well, any of my patches
<jernej>
apritzel: kidding aside, I'm actually waiting for my H6 DRAM work to be reviewed and hopefully accepted. That would allow to fix A523 DRAM driver in the process and I would also properly signed those patches.
<jernej>
I don't want DRAM patch to get in in such form
<apritzel>
jernej: ah, that's good to know. It's not like those drivers grow on trees, so I am always tempted to just take it if it works (TM)
<apritzel>
jernej: and sure, your patches are on my list for testing and review, but I am quite hopeful after a first quick glance
<jernej>
Lightsword: I remember to have working second EMAC interface on one of my H616 or T507 boards.
<montjoie>
apritzel: I will try them
<Lightsword>
jernej, I've been trying to get it working on a h616 but the i2c3 interface never comes up properly(it gets stuck with "i2c i2c-1: mv64xxx: I2C bus locked, block: 1, time_left: 0" errors), btw I rebased that branch here and fixed up some compatibility issues with latest kernel https://github.com/jameshilliard/linux-h616/commits/ac300/
<Lightsword>
jernej, yeah, not sure if that's a real issue or not, I think those warnings only showed up after I enabled some extra debug option in kconfig
<Lightsword>
jernej, think the pwm errors could be related to the i2c issue?
<loki666>
jernej: your H6 DRAM work is also for H616 detction ?
<jernej>
Lightsword: no, PWM is separate, but I can't remember if pwm-clock needs to be enabled for i2c communication or not
<jernej>
loki666: it's the other way around
<Lightsword>
jernej, am I supposed to be setting allwinner,pwm-channels in the device tree?
<loki666>
jernej: well... my question was more can I test on h616 ? I also have a a133p
<jernej>
Lightsword: that depends on the driver that you used. if you took my hacked driver, then this shouldn't do anything
<Lightsword>
jernej, yeah I used the one from your ac300-net branch, but had to apply a few fixups to get it working with latest kernel
<jernej>
loki666: H616 fixes are already merged upstream, except the first patch my new series. But if you want test this for A133 driver, take a whole
<loki666>
jernej: I quickly tried your pwm driver in that branch, because the current one I'm using seems to panic in some cases, but I couldn't make it yours works at all... but I didn't investigated what failed
<jernej>
it was hacked to support bypass - that's the only thing that matters for pwm clock for ac300
nashpa has quit [Ping timeout: 480 seconds]
<loki666>
arf... was trying to use it as a backlight pwm
<jernej>
don't trust random drivers from random repos :D
dliviu has joined #linux-sunxi
dliviu has quit [Ping timeout: 480 seconds]
<jernej>
Lightsword: it seems that driver correctly applies initial parameters (period = 42), but fails when period is 0
<jernej>
it's possible pwm behaviour changed a bit between versions
<Lightsword>
jernej, any idea why it would be applying a period of 0? does it actually need to be applying multiple times?
hazardchem has quit [Read error: Connection reset by peer]
hazardchem has joined #linux-sunxi
<montjoie>
apritzel: git http error 429 :)
<apritzel>
429? Google says that's something like rate limit, so I guess just try again? Or have you used up your 25 github accesses per day already? :-D
<montjoie>
I could access githb normaly, only command via git give that, I zill retry tomorow