<kveremitz>
smaeul: have you done anything with the older allwinner A* CPUs?
<kveremitz>
long shot .. just trying to track down recentish defconfigs for an A13 olilinuxino board I've dug up . Wifi is bein useless (as it always was with the 8192cu chips..
<kveremitz>
the olimex linux images seem to use a 5.10 kernel, which is .. sane
<smaeul>
kveremitz: sorry, I don't have anything older than H3. you could try the upstream sunxi_defconfig. others here might have more specific recommendations
vpeter has quit [Remote host closed the connection]
vpeter has joined #linux-sunxi
<kveremitz>
smaeul: no worries, I do have a H3 on my opi as it happens
anarsoul has quit [Ping timeout: 245 seconds]
specing_ has joined #linux-sunxi
anarsoul has joined #linux-sunxi
specing has quit [Ping timeout: 240 seconds]
specing_ is now known as specing
mmarc__ has joined #linux-sunxi
apritzel has quit [Ping timeout: 240 seconds]
Mangy_Dog has quit [Ping timeout: 240 seconds]
lkcl has quit [Ping timeout: 240 seconds]
gaston1980 has quit [Quit: Konversation terminated!]
lkcl has joined #linux-sunxi
victhor has quit [Ping timeout: 252 seconds]
indy has quit [Ping timeout: 248 seconds]
jstein has quit [Quit: quit]
anarsoul|c has quit [Quit: Connection closed for inactivity]
cnxsoft has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
vagrantc has quit [Quit: leaving]
lurchi_ has joined #linux-sunxi
lurchi__ has quit [Ping timeout: 240 seconds]
kaspter has joined #linux-sunxi
buzzmarshall has quit [Remote host closed the connection]
kaspter has quit [Ping timeout: 258 seconds]
kaspter has joined #linux-sunxi
swiftgeek has quit [Ping timeout: 240 seconds]
swiftgeek has joined #linux-sunxi
lurchi__ has joined #linux-sunxi
lurchi_ has quit [Ping timeout: 246 seconds]
asdf28 has joined #linux-sunxi
anarsoul|c has joined #linux-sunxi
indy has joined #linux-sunxi
mmarc___ has joined #linux-sunxi
mmarc__ has quit [Ping timeout: 246 seconds]
mmarc___ has quit [Remote host closed the connection]
mmarc__ has joined #linux-sunxi
mmarc__ has quit [Ping timeout: 250 seconds]
apritzel has joined #linux-sunxi
nik123 has joined #linux-sunxi
<nik123>
sway booted on a20 lcd panel
<nik123>
yay
<nik123>
it worked for a whole five seconds
<nik123>
until the system kernel paniced
barni2000 has quit [Quit: Connection closed]
iamfrankenstein has joined #linux-sunxi
apritzel has quit [Ping timeout: 246 seconds]
<nik123>
any ideas how to get this working longer
<nik123>
gediz0x539
<nik123>
kernel log unfortunately doesn't reveal anything that interesting
lurchi__ is now known as lurchi_
nik123 has quit [Quit: Connection closed]
mmarc__ has joined #linux-sunxi
cmeerw has joined #linux-sunxi
JohnDoe_71Rus has quit [Ping timeout: 240 seconds]
<kveremitz>
oof. any insights from logs? it didn't 'overheat' the cpu or gpu?
mmarc__ has quit [Remote host closed the connection]
apritzel has joined #linux-sunxi
mmarc__ has joined #linux-sunxi
alnyan has joined #linux-sunxi
jbrown has quit [Remote host closed the connection]
jbrown has joined #linux-sunxi
victhor has joined #linux-sunxi
netlynx has joined #linux-sunxi
Mangy_Dog has joined #linux-sunxi
JohnDoe_71Rus has joined #linux-sunxi
nik123 has joined #linux-sunxi
<nik123>
kveremitz
<nik123>
mpt to worry
<nik123>
*not
<nik123>
i got it working
<nik123>
tl;dr power issue
<nik123>
the boards voltage regulator blew up because of my previous experiments
<nik123>
but
<nik123>
plugging it in a 1A adapter makes the tablet stable
<nik123>
a20 is a power-hungry mobile chip it seems
<nik123>
now got wifi, touch, bluetooth, lcd, hdmi and gpu
<nik123>
yupee
<nik123>
and ofc sd card
<apritzel>
nik123: I guess it's more those components ^^^ that draw power ...
<buZz>
1A at what voltage?
<nik123>
5v
<buZz>
lol, thats 5 watt
<nik123>
standard usb cahrger
<buZz>
thats not hungry
<nik123>
yeah
<nik123>
but id expect a mobile chip to be even lower than that
<buZz>
lol
<nik123>
idk
<nik123>
what the power rating for a tablet usually
<buZz>
you're not basing your expectations on anything matching reality
<apritzel>
nik123: and it surely is, just not with and LCD, possibly backlight, HDMI transceivers, and what not
<buZz>
a backlight alone often already takes 5 watt
<nik123>
yeah you're right
<nik123>
my bad
<nik123>
i just used a samsung tablet that runs on 0.5 A
<nik123>
and got used to it
<nik123>
but then again
<buZz>
it'll probably discharge continuously at 0.5A
<buZz>
or did you remove the battery?
<nik123>
that thing uses a oled panel with a much newer qualcomm chip
<nik123>
the battery is gone
<nik123>
it doesnt work
<nik123>
since the regulator blew up
<buZz>
but still inside?
<nik123>
yes
<buZz>
still a big capacitor then
<nik123>
not connected at all
<nik123>
checked with an ommeter
<nik123>
*ohmmeter
<nik123>
i wonder if i partially was able to fry the charge controller by abusing it at low amperages
<nik123>
or is it the dumb charge and otg at the same time
<apritzel>
nik123: did you measure the actual current to be 1A, or was your observation just that the tablet worked with that 1A power supply?
<nik123>
1A power supply vs laptop usb port
<nik123>
i know the usb is able to charge my phone and that tablet
<nik123>
so id assume its the same
<nik123>
guess these do pull in a bit more power
<buZz>
the same what?
<apritzel>
nik123: because cheaper (or lower rated) power supplies often drop the voltage too much for higher currents, and the regulators in the device cannot cope with that
<nik123>
nah not psu, just laptop usb port
<nik123>
probably didnt provide enough current
<nik123>
as for the charger i know its 1A
<buZz>
you didnt measure?
<nik123>
nah
<buZz>
then it could be 0.1A for all you know
<nik123>
cant be bothered
<nik123>
that being said
<apritzel>
also there is the question of the cable used, I've seen so many bad cables, that lead to big voltage drops at around 0.4A already
<nik123>
yeah
<nik123>
wondering the same
<buZz>
yeah, usb doctors are nice to measure such stuff
<buZz>
also adapters
<nik123>
since the tablet boots with the short cable
<buZz>
and draw of usb devices
<nik123>
but with an extender it doesnt
<apritzel>
nik123: booting required much less power
<buZz>
extenders always lower power transferred, yes
<nik123>
that being said
<apritzel>
that's an annoying issue: many devices boot with bad power supplies and/or cables, but then seemingly randomly die later on
<nik123>
i've just ordered a new mobo for that tablet
<nik123>
it should arrive in a day or two
<nik123>
so no more soldering to 5V rails just to keep the thing working
<nik123>
and that mobo would probably be recycled as some kodi machine
<nik123>
it served me well to get linux to run on it
<nik123>
it passed the torture test
<nik123>
15eu for a old tablet mobo doesnt sound bad
<buZz>
apritzel: hehe yeah. or devices that dont init the charger on booting until kernel is all the way started
<buZz>
but -are- powering on on connecting AC adapter
<nik123>
and once it arrives id probably work on the battery dts as well
<nik123>
the red thing is just a uart thing that I used while testing this
apritzel has quit [Ping timeout: 268 seconds]
<kveremitz>
nik123: good stuff :D
<nik123>
does phosh work on these
<nik123>
using sway on touch is a pain
<alnyan>
Can I somehow get I2C working for sun50i h6 in uboot? Marvell TWSI driver seems like exactly what I need, though I still get undefined references to i2c_read() when building
<alnyan>
I'm trying to extend pmic_bus.c there to also support AXP805 via R_TWI
nik123 has quit [Quit: Connection closed]
nik123 has joined #linux-sunxi
<alnyan>
I also wonder why Orange Pi 3 schematic mentions RSB sck/sda as PMIC inputs and H6 manual has no mention of RSB
<alnyan>
Would be nice if RSB could be used instead of I2C for this
specing_ has joined #linux-sunxi
specing has quit [Ping timeout: 246 seconds]
specing_ is now known as specing
<alnyan>
... and according to linux sources H6 does indeed have a RSB controller, though it's not documented at all
jbrown has quit [Ping timeout: 240 seconds]
nik123 has quit [Quit: Connection closed]
ldevulder__ has joined #linux-sunxi
ldevulder_ has quit [Ping timeout: 268 seconds]
cnxsoft has quit [Quit: cnxsoft]
barni2000 has joined #linux-sunxi
JohnDoe7 has joined #linux-sunxi
lurchi_ has quit [Ping timeout: 246 seconds]
afaerber has quit [Remote host closed the connection]
JohnDoe_71Rus has quit [Ping timeout: 240 seconds]
afaerber has joined #linux-sunxi
apritzel has joined #linux-sunxi
apritzel has quit [Ping timeout: 240 seconds]
lurchi_ has joined #linux-sunxi
pjuck has joined #linux-sunxi
<pjuck>
hi i have q question is it normal that a allwiner h3 all interupt (from eth0 gpio etc) are performed at cpu1 despite the rigth setting /proc/irq/ affinity settings so that the kernel should use all core
<pjuck>
if i change the /proc/irq/ affinity setting for eth0 to exmpale cpu2 than that works and the interupt land at cpu 2
<pjuck>
but if i set it to cpu 0-3 then only cpu1 does get interupt
<pjuck>
looks like the kernel always chose the first cpu core
<pjuck>
if i set it to 2-3 only the cpu2 get the interupt not cpu3
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-sunxi
mmarc__ has joined #linux-sunxi
lurchi_ has joined #linux-sunxi
apritzel has joined #linux-sunxi
warpme_ has quit [Quit: Connection closed for inactivity]
buzzmarshall has joined #linux-sunxi
shailangsa has joined #linux-sunxi
alnyan has joined #linux-sunxi
<alnyan>
me continuing work on orange pi 3: I've written a simple driver for AXP805 regulators to see if I can enable ALDO2 and power on ethernet PHY
<alnyan>
apparently, missing regulator/pmic driver wasn't the problem and I just confirmed my guess that the problem lies somewhere else, as BL31 prints "ALDO2 3.3V" when booting
<alnyan>
trying to read ALDO2 voltage and status gave me "3.3V" and ON
mmarc__ has quit [Remote host closed the connection]
bantu has quit [Quit: bantu]
bantu has joined #linux-sunxi
alnyan has quit [Quit: leaving]
kaspter has quit [Quit: kaspter]
mmarc__ has joined #linux-sunxi
lurchi_ is now known as lurchi__
<megi>
alnyan: you need to toggle some gpio in addition to ALDO2, and it has to be at the same time TF-A is enabling ALDO2
<megi>
otherwise phy will not work
<megi>
it's a power sequencing issue
<tuxd3v>
its a big s*t, that is what it is..
<tuxd3v>
:)
<tuxd3v>
Orange Pi 3 lite , and orange pi one plus all are with problems with network interface due to 2 diferent power supplies
<tuxd3v>
I found a way, enabling enable-ramp-delay = <100000>; on ALDO2, sometimes make the trick
<tuxd3v>
but the problem is that sometimes is not enough, I tested with a 5.10.x and it works, then tried 5.11 and the remp delay on ALDO2 doesn't seems to work.. :/
<smaeul>
alnyan: if you have a working U-Boot driver, the ideal solution is to entirely disable the regulator code in BL31, so you can turn on ALDO2 and the GPIO at the same time
<smaeul>
or else turn ALDO2 off when loading your driver
cmeerw has quit [Ping timeout: 246 seconds]
mmarc__ has quit [Remote host closed the connection]
gaston1980 has joined #linux-sunxi
<apritzel>
smaeul: so does turning ALDO2 first off, then on again, this time together with the GPIO, work?
lurchi__ is now known as lurchi_
<smaeul>
apritzel: yes. for example with unpatched TF-A, if I rmmod dwmac-sun8i and modprobe it again, Ethernet works
<smaeul>
(using the patched version of the driver that references both regulators)
<apritzel>
smaeul: so a U-Boot AXP805 driver could carry a hack (if there is both a GPIO and an AXP rail, turn the AXP rail off first), to cover unpatched TF-As?
<smaeul>
I would expect such a hack to be in the Ethernet driver (calling regulator_set_enable(false) and then regulator_set_enable(true))