lurchi__ has quit [Quit: Konversation terminated!]
gaston1980 has joined #linux-sunxi
Mangy_Dog has quit [Ping timeout: 240 seconds]
dev1990 has quit [Quit: Konversation terminated!]
cnxsoft1 has quit [Ping timeout: 264 seconds]
cnxsoft has joined #linux-sunxi
kaspter has joined #linux-sunxi
<wens>
swiftgeek: it was the wrong approach, got nacked, and was later replaced with the mmc pwrseq stuff
<wens>
and bt serdev
apritzel has quit [Ping timeout: 246 seconds]
gameblabla has joined #linux-sunxi
gaston1980 has quit [Quit: Konversation terminated!]
<gameblabla>
Hello ! I encountered a strange issue with GPIO on an A20 board (Retrostone 2). There are some GPIO pins (PH30,PH11, PH22, PH23) that i can't monitor with gpiomon or use with gpio_keys. However, when i do so from a uinput virtual keyboard, it works fine ? Am i missing something ?
<smaeul>
gameblabla: at least PH22 and PH23 don't support interrupts, so you would need to use gpio_keys_polled
<gameblabla>
Ah i see... What about the other ones ? I must assume that it's the same issue ?
<gameblabla>
i didn't try gpio_keys_polled with PH22 so i'll give it a shot
<smaeul>
I don't see a PH30 existing in the driver at all
<smaeul>
or in the manual
<gameblabla>
oh oops yeah that's a mistake on my part
<smaeul>
PH11 should be fine
<gameblabla>
It was PH27 and PH26 instead of PH30 & PH11, my bad
<gameblabla>
I'll try those with gpio polled
<gameblabla>
Using gpio_keys_polled for PH27, PH26, PH22 and PH23 did work thanks !
<gameblabla>
Although it doesn't seem to work for PC18 and PC22
<gameblabla>
Lemme check those further
<smaeul>
PC18 would need polling, PC22 would not -- search for "EINT" in the A20 manual
<smaeul>
ah, but PC22 will not work as an interrupt at the same time as PH15, because they're the same interrupt
<smaeul>
> If platform has specified that the button can be disabled, we don't want it to share the interrupt line.
<smaeul>
so you can use normal gpio_keys if you remove the linux,can-disable property
<smaeul>
else one of PC22 or PH15 needs to use gpio_keys_polled
<gameblabla>
So i remove the can-disable property from both PH15 and PC22 ?
NekoMay has quit [Ping timeout: 260 seconds]
<gameblabla>
Nope, that doesn't work for PC22.
<gameblabla>
I also tried to put both in gpio polled and while it didn't error out, they don't work either
<gameblabla>
No matter if they are set to GPIO_ACTIVE_HIGH or GPIO_ACTIVE_LOW
<gameblabla>
They still work from the uinput thing however
NekoEd has joined #linux-sunxi
<smaeul>
I'm out of ideas, other than 1) check the counters in /proc/interrupts to see if the (non-polled key) IRQs are triggering, and 2) re-checking that you have the right GPIOs
ldevulder_ has joined #linux-sunxi
ldevulder has quit [Ping timeout: 240 seconds]
ChriChri_ has joined #linux-sunxi
ChriChri has quit [Ping timeout: 264 seconds]
ChriChri_ is now known as ChriChri
jstein has quit [Quit: quit]
[7] has quit [Ping timeout: 268 seconds]
TheSeven has joined #linux-sunxi
<gameblabla>
Well for now, i turned my uinput executable thing into a brightness daemon (the PC18/PC22 were for the brightness buttons) by reading directly from the GPIO pins and removing all of the uinput stuff. Not perfect but will do for now. No idea why it doesn't work within gpio_keys_polled but oh well.
warpme_ has quit [Quit: Connection closed for inactivity]
<gameblabla>
oooh wait right
<gameblabla>
gpios = <&pio 3 18 GPIO_ACTIVE_LOW>;
<gameblabla>
I believe it should be gpios = <&pio 2 18 GPIO_ACTIVE_LOW>;
<gameblabla>
xox
<gameblabla>
Guess that explains now. My bad :P
reinforce has joined #linux-sunxi
damex has joined #linux-sunxi
damex has quit [Read error: Connection reset by peer]
mru has quit [Ping timeout: 260 seconds]
damex has joined #linux-sunxi
cnxsoft has quit [Remote host closed the connection]
cnxsoft has joined #linux-sunxi
kaspter has quit [Ping timeout: 256 seconds]
kaspter has joined #linux-sunxi
damex has quit [Read error: Connection reset by peer]
damex has joined #linux-sunxi
kaspter has quit [Ping timeout: 240 seconds]
camus has joined #linux-sunxi
camus is now known as kaspter
cmeerw has joined #linux-sunxi
asdf28 has joined #linux-sunxi
s_frit_ has quit [Remote host closed the connection]
s_frit has joined #linux-sunxi
cmeerw has quit [Ping timeout: 268 seconds]
kaspter has quit [Ping timeout: 264 seconds]
kaspter has joined #linux-sunxi
s_frit has quit [Remote host closed the connection]
s_frit has joined #linux-sunxi
iamfrankenstein has joined #linux-sunxi
apritzel has joined #linux-sunxi
diego_r has joined #linux-sunxi
<plaes>
gameblabla: could you start with wiki page
apritzel has quit [Ping timeout: 260 seconds]
ldevulder_ is now known as ldevulder
daregap has joined #linux-sunxi
AneoX has joined #linux-sunxi
<gameblabla>
you want me to write the wiki page for the retrostone2 plaes ?
<gameblabla>
I'm still figuring out some weird other unrelated issues with buildroot
<plaes>
gameblabla: that would be nice
cnxsoft1 has joined #linux-sunxi
cnxsoft has quit [Ping timeout: 260 seconds]
yann has joined #linux-sunxi
diego_r has quit [Ping timeout: 256 seconds]
yann has quit [Ping timeout: 260 seconds]
gameblabla has quit [Quit: Leaving]
kaspter has quit [Remote host closed the connection]
gaston1980 has quit [Quit: Konversation terminated!]
apritzel has joined #linux-sunxi
lucascastro has joined #linux-sunxi
jstein has joined #linux-sunxi
lucascastro has quit [Remote host closed the connection]
lucascastro has joined #linux-sunxi
lucascastro has quit [Remote host closed the connection]
lucascastro has joined #linux-sunxi
lucas_ has joined #linux-sunxi
lucascastro has quit [Ping timeout: 265 seconds]
lucas_ has quit [Ping timeout: 260 seconds]
apritzel has quit [Ping timeout: 256 seconds]
<Ashleee>
oh no, the patch for clock skew on the Pine64 (or all Allwinner A64) doesn't work on 5.10 properly (seems to screw up timing to uart or something? and kernel panics) so I removed it and it isn't fixed in any other way in upstream, anybody knows anything? :(
<Ashleee>
it did some wraning about reading the register with counter and then sometimes crashed with uart being in the stacktrace
<Ashleee>
the two stacktraces overlapped so it was hard to read at times
<Ashleee>
(the warning started appearing since 5.9 ONLY on SOPine and with 5.10 it appeared on both SOpine and Pine64+ and it often crashed during boot)
<plaes>
hrm.. seems like I have killed my a64 board
<Ashleee>
oh wait it is the same just diff formatting
<smaeul>
there's a bug in the shared workaround code that was fixed in 5.11: git.kernel.org/torvalds/c/d8cc3905b8073c7cfbff94af889fa8dc71f21dd5
<Ashleee>
wait are you telling me the upstream fix was not applied? :)
<smaeul>
it was applied, and then broken by other changes a couple of months later
<Ashleee>
ooh
<Ashleee>
that might explain the bug I was receiving at boot time since 5.9
<Ashleee>
now if we could fix SoPine clusterboard reboots as well I'd be sooo happy :D (basically it gets stuck on reboot and doesn't hw reboot... don't know the underlying issue since it works on the baseboard normally, however sw fix might be through wdt reset?)
<Ashleee>
thanks smaeul !
<smaeul>
if the upstream workaround + that commit works, great! otherwise we would need to do some additional data gathering