Hardcoded IRQ priority on GPIOTE library

[planas]

Hi, I'm using the GPIOTE library to detect an interrupt from a sensor, query the sensor and update the gatts value. The problem I've found is that the IRQ priority is hardcoded on app_gpiote_init to APP_IRQ_PRIORITY_HIGH so this prevents me to use the event handler to directly update the gatts value, just because the interrupt priority level is higher than the SVC. A workaround is to queue an event to the scheduler, but I think it's an unnecessary overhead.

So my question is, there's any reason for hardcoding the IRQ priority to high? As I can see nrf_drv_gpiote uses the GPIOTE_CONFIG_IRQ_PRIORITY macro defined on nrf_drv_config.h instead, which IMHO is a better solution.

As a side note, I'm using the NRF52 SDK, but it is the same on the NRF51 SDK.

Thanks

[Susheel Nuguru]

you can change it to APP_IRQ_PRIORITY_LOW and it should work the same. I think it has a raised priority for serialization which i am guessing you are not using.

[planas]

@Aryan, no, I'm not using serialization. What I've done is include nrf_drv_config.h and replace APP_IRQ_PRIORITY_LOW with GPIOTE_CONFIG_IRQ_PRIORITY which is set to APP_IRQ_PRIORITY_LOW, just to keep things tidy. So well, I suggest to make this change on the next SDK revision, the current implementation is quite confusing because you expect the sdk to use the configuration on nrf_drv_config.h

[Susheel Nuguru]

The next release will have it in a different way. For now the way you have set it seems tidy.

[planas]

Yeah, that sounds good. Thanks @Aryan.