OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/subsys/ipc/ipc_service/backends/Kconfig

64 lines
1.5 KiB
Plaintext
Raw Normal View History

ipc: ipc_service: Rework multi-instance backend. Only one single IPC service backend is currently present: multi_instance backend. This backend is heavily relying on the RPMsg multi_instance code to instanciate and manage instances and endpoints. Samples exist for both in the samples/subsys/ipc/ directory. With this patch we are "unpacking" the RPMsg multi_service code to make it more modular and reusable by different backends. In particular we are re-organizing the code into two helper libraries: an RPMsg library and a VRING / virtqueues static allocation library. At the same time we rewrite the multi_instance backend to make fully use of those new libraries and remove the old multi_instance sample. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-09-06 23:26:02 +08:00
# Copyright (c) 2021 Nordic Semiconductor (ASA)
# SPDX-License-Identifier: Apache-2.0
choice IPC_SERVICE_BACKEND
prompt "IPC service backend"
ipc_service: Add new RPMsg with static VRINGs backend Introduce a new RPMsg with static VRINGs backend. This new backend makes easy to generate and use IPC instances backed by OpenAMP using the DT. Each instance is defined in the DT as (for example): ipc: ipc { compatible = "zephyr,ipc-openamp-static-vrings"; shm = <&sram_ipc0>; mboxes = <&mbox 0>, <&mbox 1>; mbox-names = "tx", "rx"; role = "primary"; status = "okay"; }; It is then possible to register an send data through endpoints using the IPC service APIs. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-11-15 22:46:56 +08:00
config IPC_SERVICE_BACKEND_RPMSG
bool "OpenAMP RPMSG backend with static VRINGs"
depends on MBOX
select IPC_SERVICE_RPMSG
select IPC_SERVICE_STATIC_VRINGS
select OPENAMP
ipc_service: Add new backend based on custom messaging buffer This commit adds ipc backend, that relies on simple inter core messaging buffer also added by this commit. This backend is configurable with DT overlay. Each ipc instance could be defined with ipc-icmsg commpatible. Signed-off-by: Emil Obalski <emil.obalski@nordicsemi.no>
2022-03-14 22:59:04 +08:00
config IPC_SERVICE_BACKEND_ICMSG
bool "ICMSG backend with ICMsg buffer"
depends on MBOX
select IPC_SERVICE_ICMSG_BUF
help
Chosing this backend results in single endpoint implementation based
on ringbuf.
ipc: ipc_service: Add support for multiple instances The IPC service code is currently assuming that only one IPC instance does exist and the user can use the IPC service API to interface with that singleton instance. This is a huge limitation and this patch is trying to fix this assumption introducing three major changes to the IPC service API: - All the IPC instances are now supposed to be instantiated as a struct device. A new test is introduced to be used as skeleton for all the other backends. - ipc_service_register_backend() is now removed (because multiple backends are now supported at the same time). - All the other ipc_service_*() functions are now taking a struct device pointer as parameter to specify on which instance the user is going to act and operate. In this patch the documentation is also extended to better clarify the terminology used. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-10-25 23:40:28 +08:00
config IPC_SERVICE_BACKEND_ZTEST
depends on ZTEST
bool "IPC service backend test"
ipc: ipc_service: Rework multi-instance backend. Only one single IPC service backend is currently present: multi_instance backend. This backend is heavily relying on the RPMsg multi_instance code to instanciate and manage instances and endpoints. Samples exist for both in the samples/subsys/ipc/ directory. With this patch we are "unpacking" the RPMsg multi_service code to make it more modular and reusable by different backends. In particular we are re-organizing the code into two helper libraries: an RPMsg library and a VRING / virtqueues static allocation library. At the same time we rewrite the multi_instance backend to make fully use of those new libraries and remove the old multi_instance sample. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-09-06 23:26:02 +08:00
endchoice
ipc_service: Re-organize Kconfig Re-organize Kconfigs to make easier adding new backends. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-11-09 21:45:34 +08:00
config IPC_SERVICE_NUM_ENDPOINTS_PER_INSTANCE
int "Max number of registered endpoints per instance"
default 2
help
Maximal number of endpoints that can be registered for one instance.
ipc: ipc_service: Rework multi-instance backend. Only one single IPC service backend is currently present: multi_instance backend. This backend is heavily relying on the RPMsg multi_instance code to instanciate and manage instances and endpoints. Samples exist for both in the samples/subsys/ipc/ directory. With this patch we are "unpacking" the RPMsg multi_service code to make it more modular and reusable by different backends. In particular we are re-organizing the code into two helper libraries: an RPMsg library and a VRING / virtqueues static allocation library. At the same time we rewrite the multi_instance backend to make fully use of those new libraries and remove the old multi_instance sample. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-09-06 23:26:02 +08:00
ipc_service: Re-organize Kconfig Re-organize Kconfigs to make easier adding new backends. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-11-09 21:45:34 +08:00
config IPC_SERVICE_REG_BACKEND_PRIORITY
int "Initialization priority of modules registering IPC backend"
default 46
help
The backend must be registered before the endpoint register.
ipc: ipc_service: Rework multi-instance backend. Only one single IPC service backend is currently present: multi_instance backend. This backend is heavily relying on the RPMsg multi_instance code to instanciate and manage instances and endpoints. Samples exist for both in the samples/subsys/ipc/ directory. With this patch we are "unpacking" the RPMsg multi_service code to make it more modular and reusable by different backends. In particular we are re-organizing the code into two helper libraries: an RPMsg library and a VRING / virtqueues static allocation library. At the same time we rewrite the multi_instance backend to make fully use of those new libraries and remove the old multi_instance sample. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-09-06 23:26:02 +08:00
config IPC_SERVICE_RPMSG
bool "RPMsg support library"
help
"RPMsg library"
config IPC_SERVICE_STATIC_VRINGS
bool "Static VRINGs support library"
help
"Static VRINGs library"
ipc_service: Re-organize Kconfig Re-organize Kconfigs to make easier adding new backends. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-11-09 21:45:34 +08:00
ipc_service: Add new RPMsg with static VRINGs backend Introduce a new RPMsg with static VRINGs backend. This new backend makes easy to generate and use IPC instances backed by OpenAMP using the DT. Each instance is defined in the DT as (for example): ipc: ipc { compatible = "zephyr,ipc-openamp-static-vrings"; shm = <&sram_ipc0>; mboxes = <&mbox 0>, <&mbox 1>; mbox-names = "tx", "rx"; role = "primary"; status = "okay"; }; It is then possible to register an send data through endpoints using the IPC service APIs. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-11-15 22:46:56 +08:00
config IPC_SERVICE_STATIC_VRINGS_ALIGNMENT
int "VRINGs alignment"
depends on IPC_SERVICE_STATIC_VRINGS
default 4
help
Static VRINGs alignment
ipc_service: Add new backend based on custom messaging buffer This commit adds ipc backend, that relies on simple inter core messaging buffer also added by this commit. This backend is configurable with DT overlay. Each ipc instance could be defined with ipc-icmsg commpatible. Signed-off-by: Emil Obalski <emil.obalski@nordicsemi.no>
2022-03-14 22:59:04 +08:00
config IPC_SERVICE_ICMSG_BUF
bool "Inter core messaging buffer support library"
help
Inter core messaging buffer library
rsource "Kconfig.icmsg"
ipc_service: Add new RPMsg with static VRINGs backend Introduce a new RPMsg with static VRINGs backend. This new backend makes easy to generate and use IPC instances backed by OpenAMP using the DT. Each instance is defined in the DT as (for example): ipc: ipc { compatible = "zephyr,ipc-openamp-static-vrings"; shm = <&sram_ipc0>; mboxes = <&mbox 0>, <&mbox 1>; mbox-names = "tx", "rx"; role = "primary"; status = "okay"; }; It is then possible to register an send data through endpoints using the IPC service APIs. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-11-15 22:46:56 +08:00
rsource "Kconfig.rpmsg"