client-node: split setup of transport and fds

We can initialize the transport as soon as we get async notify
from the client when setup completes. Node initialization happens
after that and then finaly the node is initialized and we can send
the transport and fds.
Small cleanups
This commit is contained in:
Wim Taymans 2017-10-25 16:47:43 +02:00
parent 4f33a37ac6
commit b25985a2b2
5 changed files with 43 additions and 60 deletions

View file

@ -137,7 +137,7 @@ struct spa_node_callbacks {
/**
* struct spa_node:
*
* A struct spa_node is a component that can comsume and produce buffers.
* A struct spa_node is a component that can consume and produce buffers.
*
*
*
@ -585,7 +585,7 @@ struct spa_node {
* output from
*
* - set the status to SPA_RESULT_OK for the port you don't want more
* buffer from.
* buffers from.
*
* Returns: #SPA_RESULT_OK on success or when the node is asynchronous
* #SPA_RESULT_NEED_BUFFER for synchronous nodes when input

View file

@ -101,7 +101,7 @@ spa_pod_builder_raw(struct spa_pod_builder *builder, const void *data, uint32_t
return ref;
}
static void spa_pod_builder_pad(struct spa_pod_builder *builder, uint32_t size)
static inline void spa_pod_builder_pad(struct spa_pod_builder *builder, uint32_t size)
{
uint64_t zeroes = 0;
size = SPA_ROUND_UP_N(size, 8) - size;