No Hardware Interrupts for GPIO

[pantera]

Using either python or java, there is no way to set an interrupt on a GPIO pin. Instead, you must poll, wasting valuable CPU. In other words, the modules available to read pins as input or output do not support setting callback functions as RPi.GPIO does.

This has been available since 2013 on the Raspberry Pi, but is not supported by any of the modules on the Rock64. See:

https://raspi.tv/2013/how-to-use-interru...pio-part-3

The only modules I can find are Leapo and all callbacks are marked as "Not yet implemented." Further doc says that interrupts are not supported in the kernel. This makes the GPIO header useless for real applications.

https://github.com/Leapo/Rock64-R64.GPIO...efinitions

[fmotsch]

Due to this I use the rock64 only as database and fileserver. eMMC is more reliable.
For hardware applications there is the Rasperry Pi. Having no GPIO interrupts really sucks.
Polling is no option (for me).

[Badger]

Using either python or java, there is no way to set an interrupt on a GPIO pin. Instead, you must poll, wasting valuable CPU. In other words, the modules available to read pins as input or output do not support setting callback functions as RPi.GPIO does.

This has been available since 2013 on the Raspberry Pi, but is not supported by any of the modules on the Rock64. See:

https://raspi.tv/2013/how-to-use-interru...pio-part-3

The only modules I can find are Leapo and all callbacks are marked as "Not yet implemented." Further doc says that interrupts are not supported in the kernel. This makes the GPIO header useless for real applications.

https://github.com/Leapo/Rock64-R64.GPIO...efinitions

Thanks for posting this.

I have been doing some research (been stung before with SBC's not living up to their expectations) as I wanted to buy this board for a project, but I will need interrupts.
I've also seen that the GPIO, and SPI is slow.

Is this still true?

Thanks!