ChanServ changed the topic of #armlinux to: ARM kernel talk [Upstream kernel, find your vendor forums for questions about their kernels] | https://libera.irclog.whitequark.org/armlinux
rvalue has quit [Read error: Connection reset by peer]
rvalue has joined #armlinux
elastic_dog has joined #armlinux
headless has joined #armlinux
Stary has joined #armlinux
Fridtjof has joined #armlinux
Fridtjof has quit [Ping timeout: 268 seconds]
Stary has quit [Ping timeout: 268 seconds]
Fridtjof has joined #armlinux
Stary has joined #armlinux
<marex>
errr ... so on imx8mp, if I use GPIO as interrupt source and bootloader configured the GPIO as output (it was used to drive LED on that line there), Linux won't reconfigure the pin as input
<marex>
that's a bit odd, isn't it ?
<marex>
linusw_: shawnguo: Peng_Fan: ^
<marex>
I would expect that a pin would be reconfigured as input by gpio-mxc.c if it is supposed to be interrupt source
<jn>
you might need an explicit pinctrl node in your devicetree, for that, but i'm not completely sure
<marex>
jn: for what ? pinctrl is separate from gpio direction settings
<jn>
hm, true
rvalue has quit [Ping timeout: 272 seconds]
sudeepholla_ has quit [Ping timeout: 272 seconds]
rvalue has joined #armlinux
<marex>
it also seems other GPIO drivers do not set IRQ pin as input either
<marex>
hmmmmmm
sudeepholla_ has joined #armlinux
c1728p9 has joined #armlinux
headless has quit [Quit: Konversation terminated!]
Pali has joined #armlinux
amitk_ has joined #armlinux
amitk has quit [Ping timeout: 268 seconds]
<ukleinek>
marex: IIRC you have to care for direction_input on the driver level if you use a gpio as irq source
<ukleinek>
(not only on i.MX but as a correct user of the gpio API)
c1728p91 has joined #armlinux
c1728p9 has quit [Ping timeout: 244 seconds]
c1728p91 has quit [Quit: Leaving]
Pali has quit [Ping timeout: 268 seconds]
<marex>
ukleinek: well that is odd, if I have interrupts-extended DT property, I cannot know whether that;s a GPIO or not, can I ?