mg: Always set MCR on both daughterboards

The N310 cannot set the MCR for its daughterboards separately. This
patch modifies the radio block controller such that any block
controller, when requested to change the master clock rate, will first
change Radio 0, and then Radio 1.

This fixes the following issues:
- In multi_usrp, calling set_master_clock_rate() will not necessarily
  call set_rate() on the radios in any particular order, which will
  break when calling Radio 1 first
- In RFNoC apps, it wasn't possible to run off of slot B alone without
  this change.

Note: When calling set_rate() on one radio, the other radio is in an
invalid state until its set_rate() is also called.

1 files changed, 0 insertions, 2 deletions

diff --git a/host/lib/usrp/dboard/magnesium/magnesium_ad9371_iface.hpp b/host/lib/usrp/dboard/magnesium/magnesium_ad9371_iface.hpp
index 63972a54c..2374a4503 100644
--- a/host/lib/usrp/dboard/magnesium/magnesium_ad9371_iface.hpp
+++ b/host/lib/usrp/dboard/magnesium/magnesium_ad9371_iface.hpp
@@ -28,8 +28,6 @@ public:
 
     double get_gain(const size_t chan, const uhd::direction_t dir);
 
-    double set_master_clock_rate(const double freq);
-
     double set_bandwidth(
         const double bandwidth, const size_t chan, const uhd::direction_t dir);