-
Notifications
You must be signed in to change notification settings - Fork 1.4k
nrf_rpc: unify nRF RPC initialization #25874
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
CI InformationTo view the history of this post, click the 'edited' button above Inputs:Sources:sdk-nrf: PR head: 8db1988f6cb1df0f801c2d7e8a5c82e7e51b956e more detailssdk-nrf:
Github labels
List of changed files detected by CI (10)Outputs:ToolchainVersion: 43683a87ea Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
|
You can find the documentation preview for this PR here. |
c6c4e37 to
5735c82
Compare
5735c82 to
093a652
Compare
|
@nordicjm Please review |
Currently, almost each component implementing RPC function encoders and decoders, provides an option to automatically start nRF RPC during the system startup. Reduce the code duplication by introducing CONFIG_NRF_RPC_INIT that handles starting nRF RPC regardless of the enabled RPC serialization libraries. Signed-off-by: Damian Krolik <damian.krolik@nordicsemi.no>
093a652 to
8db1988
Compare
Currently, almost each component implementing RPC function encoders and decoders, provides an option to automatically start nRF RPC during the system startup. Reduce the code duplication by introducing CONFIG_NRF_RPC_INIT that handles starting nRF RPC regardless of the enabled RPC serialization libraries.