sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
_whitelogger has joined #linux-amlogic
JerryXiao has quit [Quit: Bye]
JerryXiao has joined #linux-amlogic
_whitelogger has joined #linux-amlogic
sputnik_ has joined #linux-amlogic
memeka has quit [Quit: Connection closed for inactivity]
Barada has joined #linux-amlogic
memeka has joined #linux-amlogic
ldevulder_ has joined #linux-amlogic
ldevulder has quit [Ping timeout: 250 seconds]
ldevulder_ is now known as ldevulder
nsaenz has joined #linux-amlogic
Barada has quit [Quit: Barada]
gartyciuks has joined #linux-amlogic
sputnik_ has quit [Remote host closed the connection]
sputnik_ has joined #linux-amlogic
afaerber has quit [Quit: Leaving]
nemunaire has joined #linux-amlogic
afaerber has joined #linux-amlogic
<gartyciuks>
the full error I was getting was "[ 327.277011] irq: type mismatch, failed to map hwirq-109 for interrupt-controller@9880!"
<gartyciuks>
but looks like it only occurs if I change the flags in the device tree of the interrupt and dynamically reload the new overlay
<gartyciuks>
rebooting and loading the overlay on 'clean slate' does not give this error, so its' fine
<gartyciuks>
however, the rising edge interrupt does not get fired when the pin state changes to high... The pin value is read correctly manually
chewitt has quit [Quit: Adios!]
sputnik_ has quit [Remote host closed the connection]
afaerber has quit [Quit: Leaving]
afaerber has joined #linux-amlogic
<gartyciuks>
ok, finally got it working, turns out my module was cleanly unloading due to some unrelated error further a bit later within the probe, silently freeing the irq
gartyciuks has quit [Quit: Page closed]
sheepman has joined #linux-amlogic
memeka has quit [Quit: Connection closed for inactivity]