dc9d479dea
The icmsg backend for ipc_service has a limitation of supporting only on endpoint. This limitation is acceptable for many IPC instances. However, some require to use multiple endpoints sharing a single instance. To preserve the simple and the most efficient single-instance backend, a separated backend is introduced implementing a wrapper around icmsg core which adds multiple endpoints support. There are two multi-endpoint ipc_service icmsg backends: one in the initiator role, and the other one in the follower role. In a IPC configuration one end of communication must be in the follower role while the other one is in the initiator. The initiator initiates an endpoint discovery handshake to establish enpoint identifiers for requested endpoint names. The follower responds to requests sent by the initiator. Signed-off-by: Hubert Miś <hubert.mis@nordicsemi.no> |
||
|---|---|---|
| .. | ||
| ipc_service | ||
| rpmsg_service | ||
| CMakeLists.txt | ||
| Kconfig | ||