I had this fixed on the original pull request but only a few hours AFTER the branch was merged. Sorry about that.
The problem we are fixing here is that we are powering down the ADF4350 from the "main" thread, while the "ADC" thread actually "owns" the ADF4350; aka there is change the ADC thread interrupts the powerdown sequence. and thus leaving the ADF4350 in a unknown state.
It probably does not cause any trouble since the sweep is not using the ADF4350 anymore. When ADF4350 is used again the device is properly configured again.
I had this fixed on the original pull request but only a few hours AFTER the branch was merged. Sorry about that. The problem we are fixing here is that we are powering down the ADF4350 from the "main" thread, while the "ADC" thread actually "owns" the ADF4350; aka there is change the ADC thread interrupts the powerdown sequence. and thus leaving the ADF4350 in a unknown state. It probably does not cause any trouble since the sweep is not using the ADF4350 anymore. When ADF4350 is used again the device is properly configured again.