remote-node: don't set activation state and signal_time twice

This is already set by resume_node.
This commit is contained in:
Wim Taymans 2022-08-11 12:35:51 +02:00
parent 1bc1d96f88
commit 27dcbfc1ee

View file

@ -857,14 +857,8 @@ static int link_signal_func(void *user_data)
{
struct link *link = user_data;
struct spa_system *data_system = link->data->context->data_system;
struct timespec ts = { 0, 0 };
pw_log_trace_fp("link %p: signal", link);
spa_system_clock_gettime(data_system, CLOCK_MONOTONIC, &ts);
link->target.activation->status = PW_NODE_ACTIVATION_TRIGGERED;
link->target.activation->signal_time = SPA_TIMESPEC_TO_NSEC(&ts);
pw_log_trace_fp("link %p: signal %p", link, link->target.activation);
if (SPA_UNLIKELY(spa_system_eventfd_write(data_system, link->signalfd, 1) < 0))
pw_log_warn("link %p: write failed %m", link);