gpio_add_callback() returns -ENOSYS

[Torsten Robitzki]

Hello,

I want to use the bq274xx.c sensor library. The bq274xx battery fuel gauge has an interrupt pin, which would allow to have the CPU idle until something interesting happens. To make use of that feature, I configured the library with:

CONFIG_BQ274XX_PM=y
CONFIG_BQ274XX_TRIGGER_GLOBAL_THREAD=y

Now, from within bq274xx_trigger.c, the call to `gpio_add_callback()` fails with -ENOSYS. Looking at the documentation (https://docs.nordicsemi.com/bundle/ncs-2.3.0/page/zephyr/hardware/peripherals/gpio.html) of `gpio_add_callback()`, I can not find any hint as to under which circumstances the function would return that value or as to how to configure the system, so that `gpio_add_callback()` works as intended.

What configuration needs to be applied here?

best regards

Torsten

[Sigurd Hellesvik]

Hi Torsten,

For us to help you with this in the best possible way, please list the following information:

• SDK Version
• Which sample do you use, if any?
• Do you use custom hardware or a DK?

Regards,
Sigurd Hellesvik

[Torsten Robitzki]

Hi Sigurd Hellesvik ,

- Nrf-Connect version 2.8.0

- No sample. And the only available sample does not make use of that feature.

- Custom Hardware.

best regards

Torsten

[Jakob Ruhe]

The settings you have shared looks correct. But please share also which MCU and which pin you trying to use. Perhaps the chosen pin does not support being configured to use interrupts?

[Torsten Robitzki]

- nRF5340

- P0.25

[Sigurd Hellesvik]

Looking at gpio_add_callback, it looks like ENOSYS is returned if manage_callback is missing:

For gpio_nrfx.c, I see that manage_callback is defined if CONFIG_GPIO_NRFX_INTERRUPT. Perhaps this is what you need?

[Torsten Robitzki]

Thanks good spot! :-) Thank you!

Leaves the more philosophical question, why does this compile in the first place, if it is known at compile time that the will not run at runtime? But I guess, I would have to address that to the Zephyr team.

best regards

Torsten