nrf_rpc: add nrf_rpc_setup, nrf_rpc_bind and nrf_rpc_unbind #1888
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.



nrf_rpc: add Kconfig to configure default group flags
By default, groups defined with NRF_RPC_GROUP_DEFINE()
are initiators (send an init packet to the peer) and wait
for initialization (until they receive an init packet from
the peer).
Make it possible to override these settings with Kconfig
so that one can decide which device is an initiator and
which is a responder.
--
nrf_rpc: add nrf_rpc_setup, nrf_rpc_bind and nrf_rpc_unbind
that behave together like existing nrf_rpc_init().
calling nrf_rpc_bind().
These are needed to support re-connecting to the peer, for
example after noticing that a peer has been reset, and the
peer is not a group initiator (thus, it does not send an nRF
RPC initialization packet automatically at startup).