When using oversample mode, bladerf_set_frequency also modifies sample rate

[asazernik]

The following sequence of calls results in a sample rate of 384000000:

bladerf_enable_feature(dev, BLADERF_FEATURE_OVERSAMPLE, true);
bladerf_rational_rate actual, desired;
desired.integer = 96000000; desired.num = 0; desired.den = 1;
bladerf_set_rational_sample_rate(dev, BLADERF_TX_CHANNEL, desired, &actual);
// assert(actual.integer == desired.integer); // passes
bladerf_set_frequency(dev, BLADERF_RF_TX_CHANNEL, 122657000);
bladerf_get_rational_sample_rate(dev, BLADERF_RF_TX_CHANNEL, actual);

This also happens with regular old integral bladerf_set_sample_rate().

If I swap the order of call so that bladerf_set_frequency() comes first, everything works as expected.

[cwozny]

Are you using a specific release of libbladeRF or whatever the latest was at the time of this post?

[asazernik]

The version included in release 2023.02. Checking now, that seems to be 2.5.0.