GPIO Input Interrupt to TASK on Zephyr 3

RE: GPIO Input Interrupt to TASK on Zephyr 3

CacO3 — Mon, 13 Jun 2022 09:44:13 GMT

Sorry for the late response.

We seem to have some priotity issues with BLE in Zephyr 3. We will need to investigate further and create a separate support ticket if needed.

RE: GPIO Input Interrupt to TASK on Zephyr 3

Håkon Alseth — Mon, 30 May 2022 15:01:23 GMT

Hi,

I'm not sure I understand. Isn't the TIMER IRQ that needs to run in the link that you posted?

The GPIOTE seems to be connected through PPI, so that should "run" (ie. trigger the task endpoint) regardless of what the CPU is up to.

Kind regards,

Håkon

RE: GPIO Input Interrupt to TASK on Zephyr 3

CacO3 — Wed, 25 May 2022 14:34:07 GMT

Dear Håkon

Thank you for your quick response!

This indeed helps solves this issue!

How ever we now experience performance issues when using Bluetooth.

We had such an issue before (see https://github.com/zephyrproject-rtos/zephyr/discussions/41401#discussioncomment-1858153 ).

The solution was to adjust the priorities. For our needs the GPIO interrupt must have a GPIO priority sitting between the Bluetooth Stacks Upper Layer and Lower Layer tasks (Needed to set CONFIG_BT_CTLR_ULL_HIGH_PRIO=2).

Do you know if something changed there as well? Else I will try to ask @cvinayak

RE: GPIO Input Interrupt to TASK on Zephyr 3

Håkon Alseth — Wed, 25 May 2022 13:54:55 GMT

Hi!

With ncs v1.9.x, the zephyr gpio driver (gpio_nrfx.c) is now fully using nrfx_gpiote as a backend, making it possible for the user to use both simultaneously in their application.

One drawback there is that the amount of event handlers must be manually set in kconfig, using this configuration:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/1.9.1/kconfig/CONFIG_NRFX_GPIOTE_NUM_OF_EVT_HANDLERS.html

Could you try setting prj.conf::CONFIG_NRFX_GPIOTE_NUM_OF_EVT_HANDLERS=2 and see if this helps?

Kind regards,

Håkon