diff options
| author | David Raeman <david@synopticengineering.com> | 2022-02-16 17:51:57 +0000 |
|---|---|---|
| committer | Aaron Rossetto <aaron.rossetto@ni.com> | 2022-03-03 14:02:30 -0600 |
| commit | 7599789f83bcf9f9e9bdef3432c37e460bddc1e4 (patch) | |
| tree | bf05fd15759619fcfbd76357046c3f0ee4dfe0a8 /mpm/cmake | |
| parent | cd4b9cb96c00497d3121c59bd97c60e9fcf7e7bc (diff) | |
| download | uhd-7599789f83bcf9f9e9bdef3432c37e460bddc1e4.tar.gz uhd-7599789f83bcf9f9e9bdef3432c37e460bddc1e4.tar.bz2 uhd-7599789f83bcf9f9e9bdef3432c37e460bddc1e4.zip | |
mpm: fix ref_locked sensor on n320
The ref_locked mboard sensor on the n320 always returned true without
querying hardware. On this device family, mboard sensor callback in
n3xx.py returns the "and" of its daughterboard LMK PLLs by querying the
get_ref_lock() function on each dboard manager. However, that function
only existed for the Magnesium daughterbaord. For the Rhodium
daughterboard, the function didn't exist and so a true value was
automatically returned.
This commit adds the get_ref_lock() implementations for Rhodium and
EISCAT daughterboards, which are identical to the implementation
already present for Magnesium.
Co-authored-by: Martin Braun <martin.braun@ettus.com>
Diffstat (limited to 'mpm/cmake')
0 files changed, 0 insertions, 0 deletions