Hi,

I'm working on a custom board and I need to decide my MCU pin connections. I'm having this doubt regarding the gyro interrupt. In betaflight software what is the main objective of the gyro interrupt? Just wait for the data availability? Will it be very problematic if this feature is not used? 

In a working prototype I have compiled a betaflight version for my board without the code I show below, and it seems not affected by its removal.

#define USE_EXTI
#define USE_GYRO_EXTI
#define GYRO_1_EXTI_PIN         PB3
#define USE_MPU_DATA_READY_SIGNAL
#define ENSURE_MPU_DATA_READY_IS_LOW

Not sure many of us can guess what the overall impact is unless we study the Betaflight code.

I guess the best place to as is on the Betaflight slack server: https://slack.betaflight.com/

I think most of the devs have moved to the Discord:
https://discord.gg/TWHdTmtTM9

They never advertised the discord server on their github page: https://github.com/betaflight/betaflight...rs-channel