High accuracy GPIO interrupts in NCS possible?

[Bruno Randolf]

In the old Nordic SDK we had the option of using "high accuracy" interrupts with GPIOTE by using something like NRFX_GPIOTE_CONFIG_IN_SENSE_LOTOHI(true);

Is there a similar option for NCS? I am asking because in my specific use case I measure ~160us from interrupt to handler with the old SDK and ~450us with NCS and I would like to improve that.

CONFIG_ZERO_LATENCY_IRQS is on and i configure my interrupts like this:

gpio_pin_configure_dt(&conf.gpio_irq, GPIO_INPUT);

gpio_init_callback(&gpio_cb, dw3000_hw_isr, BIT(conf.gpio_irq.pin));

gpio_add_callback(conf.gpio_irq.port, &gpio_cb);

gpio_pin_interrupt_configure_dt(&conf.gpio_irq, GPIO_INT_EDGE_RISING);

Thank you

[Bruno Randolf]

As far as I am concerned, it's okay. I need to optimize in another area, probably SPI.

It could be worth to investigate why GPIO interrupts in NCS take about twice the time from trigger to callback function, when compared to the old SDK. It's 8us with old SDK vs 14us with NCS. I could share example projects for both if you are interrested.

[Sigurd Hellesvik]

Bruno Randolf said:

It could be worth to investigate why GPIO interrupts in NCS take about twice the time from trigger to callback function, when compared to the old SDK. It's 8us with old SDK vs 14us with NCS. I could share example projects for both if you are interrested.

If you could upload them, that would be nice. Then we can try to have a look, but I cannot promise anything. If you still have the sample with NCS and nrfx drivers mentioned earlier, that could also be interesting to see.