diff options
author | Martin Braun <martin.braun@ettus.com> | 2019-11-12 10:28:31 -0800 |
---|---|---|
committer | Martin Braun <martin.braun@ettus.com> | 2019-11-26 12:21:33 -0800 |
commit | 59fae330b0345c4a587862322b16379e563e673b (patch) | |
tree | 4b686e3239d0811f98ab1a63bc321812f0baef52 /host/lib/rfnoc/rfnoc_graph.cpp | |
parent | 59a436038445613b6552c804601297405d736fce (diff) | |
download | uhd-59fae330b0345c4a587862322b16379e563e673b.tar.gz uhd-59fae330b0345c4a587862322b16379e563e673b.tar.bz2 uhd-59fae330b0345c4a587862322b16379e563e673b.zip |
detail::graph: Add shutdown capability
In the existing graph, when the shutdown was simply a release. However,
any outstanding actions would trigger warnings (because released graphs
aren't supposed to still have actions being passed around), which would
sometimes be visible at the end of an application.
This is a safer solution than simply releasing, because it explicitly
sets a shutdown flag that all graph-affecting functions (property
propagation and action handling) respect. Once the flag is set, the
graph can no longer be booted up again.
Diffstat (limited to 'host/lib/rfnoc/rfnoc_graph.cpp')
-rw-r--r-- | host/lib/rfnoc/rfnoc_graph.cpp | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/host/lib/rfnoc/rfnoc_graph.cpp b/host/lib/rfnoc/rfnoc_graph.cpp index 6ebfe8612..32a9b0071 100644 --- a/host/lib/rfnoc/rfnoc_graph.cpp +++ b/host/lib/rfnoc/rfnoc_graph.cpp @@ -82,8 +82,8 @@ public: ~rfnoc_graph_impl() { - UHD_LOG_TRACE(LOG_ID, "Releasing detail::graph..."); - _graph->release(); + UHD_LOG_TRACE(LOG_ID, "Shutting down detail::graph..."); + _graph->shutdown(); UHD_LOG_TRACE(LOG_ID, "Shutting down all blocks ..."); _block_registry->shutdown(); _graph.reset(); |