mg: Lock access to setters

Magnesium APIs are not thread-safe and can take a while to execute in
some cases. Adding a mutex to setters avoids invalid states of the
hardware from API calls.

Note that the lock applies to one block at a time. With the
two-radios-per-dboard approach, two locks need to be applied and race
conditions are still possible.

Reviewed-By: Trung Tran <trung.tran@ettus.com>

1 files changed, 4 insertions, 0 deletions

diff --git a/host/lib/usrp/dboard/magnesium/magnesium_radio_ctrl_impl.hpp b/host/lib/usrp/dboard/magnesium/magnesium_radio_ctrl_impl.hpp
index aa70fa7ad..ce96eb200 100644
--- a/host/lib/usrp/dboard/magnesium/magnesium_radio_ctrl_impl.hpp
+++ b/host/lib/usrp/dboard/magnesium/magnesium_radio_ctrl_impl.hpp
@@ -28,6 +28,7 @@
 #include <uhd/types/serial.hpp>
 #include <uhd/usrp/dboard_manager.hpp>
 #include <uhd/usrp/gpio_defs.hpp>
+#include <mutex>
 
 namespace uhd {
     namespace rfnoc {
@@ -192,6 +193,9 @@ private:
     /**************************************************************************
      * Private attributes
      *************************************************************************/
+    //! Locks access to setter APIs
+    std::mutex _set_lock;
+
     //! Letter representation of the radio we're currently running
     std::string _radio_slot;