diff options
author | Martin Braun <martin.braun@ettus.com> | 2022-01-07 14:16:42 +0100 |
---|---|---|
committer | Aaron Rossetto <aaron.rossetto@ni.com> | 2022-01-10 08:02:41 -0600 |
commit | 6666f36c267fc9ca908032fb719ec318c142636f (patch) | |
tree | ddfaf98d398e0f51d6cea1da4c61306c680a49f5 /fpga/CONTRIBUTING.md | |
parent | edf16b3a85507064d42da2021d5eaea4002f7912 (diff) | |
download | uhd-6666f36c267fc9ca908032fb719ec318c142636f.tar.gz uhd-6666f36c267fc9ca908032fb719ec318c142636f.tar.bz2 uhd-6666f36c267fc9ca908032fb719ec318c142636f.zip |
mpm: e320/e31x: Fix lo-lock sensors
The LO-locked sensors on these devices were getting routed to the MPM
API call get_lo_lock_sensor(), which takes a 'which' argument (rx or
tx). However, UHD wants to pass a 'chan' argument (0 or 1). The way the
code was structured, it would always return 'False' (LO not locked) when
the argument was neither 'rx' or 'tx'.
The solution is to add get_rx_lo_lock_sensor() and
get_tx_lo_lock_sensor(), which generate the appropriate 'which'
argument, but discard the 'chan' argument (there is only one LO per Tx
and Rx, respectively).
Diffstat (limited to 'fpga/CONTRIBUTING.md')
0 files changed, 0 insertions, 0 deletions