narmstrong changed the topic of #linux-amlogic to: Amlogic mainline kernel development discussion - our wiki http://linux-meson.com/ - ml linux-amlogic@lists.infradead.org - official channel moved from Freenode - publicly logged on https://libera.irclog.whitequark.org/linux-amlogic
jelly has quit [Ping timeout: 246 seconds]
narmstrong has quit [Ping timeout: 245 seconds]
khilman has quit [Read error: Connection reset by peer]
jelly has joined #linux-amlogic
khilman has joined #linux-amlogic
narmstrong has joined #linux-amlogic
camus has joined #linux-amlogic
sputnik__ has quit [*.net *.split]
Lyude has quit [*.net *.split]
dlan has quit [*.net *.split]
Lyude has joined #linux-amlogic
sputnik__ has joined #linux-amlogic
dlan has joined #linux-amlogic
sputnik__ has quit [Ping timeout: 252 seconds]
f11f12 has joined #linux-amlogic
tolszak has joined #linux-amlogic
warpme__ has joined #linux-amlogic
<tolszak> narmstrong: Hello, Any idea how odroid n2 handles gpio interrupts after power off? It works alright with hardkernel kernel and gpiopower=gpio_pin_id. With amlogic meson I was only able to power off using gpio
<tolszak> with small change to dts
<narmstrong> tolszak: you mean to power on after power off ? Or to go into power off ?
<tolszak> I'm able to poweroff (with this patch https://github.com/agners/operating-system/commit/5073d6ac50aeffedf4cece534e6b1e05320e6937) but can't wake it up
<tolszak> Downloding hardkernel kernel sources to look what they do
<tolszak> But perhaps it is something with 5.X kernel...
<tolszak> narmstrong: I can't power on after power off
<narmstrong> Perhaps hardkernel has changed how they interact with this piec of code
<narmstrong> On amlogic réf board all of this is hardcoded
<tolszak> Hmm Is it safe to just try to apply this patch to 5.14?
<tolszak> narmstrong: On rpi 4it is part of their firmware. I mean the configuration
<tolszak> narmstrong: Found some information finally: https://forum.odroid.com/viewtopic.php?p=330159#p330159
<tolszak> Leaving this one here in case someone else will google and find this conversation: https://github.com/tassadar777/gpio-wakeup, I will let know if it works
Darkmatt- has quit [Ping timeout: 265 seconds]
Darkmatter66 has joined #linux-amlogic
f11f12 has quit [Remote host closed the connection]
f11f12 has joined #linux-amlogic
camus has quit [Quit: camus]
<tolszak> narmstrong: Everything works as expected, so it is possible to have wakeup on odroid-n2 wih mainline kernel and some 3rd party module
camus has joined #linux-amlogic
f11f12 has quit [Quit: Leaving]
<tolszak> narmstrong: Ah so it actually is handled by u-boot right?
<narmstrong> tolszak: no, by the BL301 FW which is built with u-boot
<tolszak> Ah I see,
<tolszak> That's the firmware, and kernel need to write to some kind of register before shut down to enable it
<narmstrong> yep
<tolszak> I don't know if it has some side effects, but I suppose shouldn't
<narmstrong> there's no, but no sure this could go upstream
<tolszak> narmstrong: And it seems to work instantly, no need to ground pin for 2 seconds
<tolszak> narmstrong: For me it is OK to maintain such simple module
<tolszak> for my purpose
<tolszak> narmstrong: with youcto it is somewhat enjoyable
jernej has joined #linux-amlogic
cmeerw has joined #linux-amlogic
tolszak has quit [Read error: Connection reset by peer]
camus has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
vagrantc has joined #linux-amlogic
anessen97 has joined #linux-amlogic
jernej has quit [Ping timeout: 260 seconds]
cmeerw has quit [Ping timeout: 265 seconds]
sputnik_ has quit [Ping timeout: 245 seconds]