<aeroraptor>
specifically the error: pps-gpio pps@0: failed to map GPIO to IRQ: -6
<xdarklight>
aeroraptor: I've no experience with pps-gpio but I suspect it's due to the fact that it's calling gpiod_to_irq() internally which is not supported by the meson GPIO driver
<aeroraptor>
oh wow, so GPIOs on amlogic chips just... cannot use interrupts?
<aeroraptor>
I don't know if the odroid-c2 uses (used?) a different GPIO driver, but apparently they ended up writing a kernel module
<aeroraptor>
I think the odroid example using a kernel module is prooooobably the right way to go here
<xdarklight>
looking at the odroid driver: it simply uses gpio_to_irq() instead of gpiod_to_irq() which is basically the same API just with a GPIO number (deprecated) instead of GPIO descriptor. most likely the Amlogic vendor GPIO driver support the GPIO to IRQ translation which is not supported with the mainline driver (yet)
<xdarklight>
there's been a lengthy discussion on the mailing list about supporting the GPIO to IRQ translation upstream as well, both Jerome Brunet and Heiner Kallweit worked on it but there were some issues that they could not resolve
<narmstrong>
There’s not a 1-to-1 or many-to-1 mapping from gpios to an interrupt line, this makes supporting gpiod_to_irq harder since this api has been very badly designed a long time ago, using a DT interrupt property is not the right API to use, the PPS gpio code should be modernized
jacobk has quit [Ping timeout: 252 seconds]
elastic_dog has quit [Ping timeout: 240 seconds]
elastic_dog has joined #linux-amlogic
ldevulder_ has quit [Quit: Leaving]
<aeroraptor>
interesting
<aeroraptor>
I know this sort of thing tends to fall by the wayside, since not a whole lot of folks use PPS inputs on SoCs like these (just like not many folks are using the GPIOCLK outputs)