rfnoc: async message: Include timestamp in async message handling

Async messages (like, e.g., overrun messages) can include a timestamp.
This change enables access to the timestamp in the async message
handler. It is up to the FPGA block implementation to include the
timestamp, if desired/necessary. The definition of the timestamp may
also depend on the block, for example, the overrun async message will
include the time when the overrun occurred.

1 files changed, 2 insertions, 1 deletions

diff --git a/host/lib/rfnoc/ctrlport_endpoint.cpp b/host/lib/rfnoc/ctrlport_endpoint.cpp
index 267ff5d71..5c0deca1d 100644
--- a/host/lib/rfnoc/ctrlport_endpoint.cpp
+++ b/host/lib/rfnoc/ctrlport_endpoint.cpp
@@ -275,7 +275,8 @@ public:
                     "CTRLEP", "Malformed async message request: Invalid num_data");
             } else {
                 try {
-                    _handle_async_msg(rx_ctrl.address, rx_ctrl.data_vtr);
+                    _handle_async_msg(
+                        rx_ctrl.address, rx_ctrl.data_vtr, rx_ctrl.timestamp);
                     status = CMD_OKAY;
                 } catch (...) {
                     UHD_LOG_ERROR("CTRLEP", "Async message handler threw an exception");