Interrupt capture time on High and Low Accuracy using GPIO

[Ameer Usman]

So what I want to ask is what is the scan latency during high accuracy and low accuracy?

nrf_drv_gpiote_in_config_t in_1_config = GPIOTE_CONFIG_IN_SENSE_HITOLO(0);

//or

nrf_drv_gpiote_in_config_t in_1_config = GPIOTE_CONFIG_IN_SENSE_HITOLO(1);

Also if an insight regarding power consumption can be given would be great (we are really tight in regards to power constraints)

[Jørgen Holmefjord]

Hi,

The difference between high and "low accuracy" is that high accuracy use GPIOTE (p)IN event, while "low accuracy" use the GPIOTE PORT event. The PORT event can be shared between multiple GPIOs, meaning that the application/driver needs to check which pin generated the event in the interrupt handler.

The events are generated in the hardware, meaning that the latency will depend on interrupt priority, and if other higher priority tasks are blocking the handling of the interrupt. This is not a general question we can give you a definite answer to. You can use the IN event to control tasks in HW with PPI, which will have very low latency (Device startup times).

Best regards,
Jørgen

[Ameer Usman]

Is there any documented number as to which the minimum update latency is in High accuracy and Low accuracy?