OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/drivers/mbox/CMakeLists.txt

12 lines
487 B
CMake
Raw Normal View History

drivers: mbox: Introduce MBOX driver class One limitation of the current IPM API is that it is assuming that the hardware is only exporting one single channel through which the data can be sent or signalling can happen. If the hardware supports multiple channels, the IPM device must be instantiated (possibly in the DT) several times, one for each channel to be able to send data through multiple channels using the same hw peripheral. Also in the current IPM API only one callback can be registered, that means that only one driver is controlling all the signalling happening on all the channels. This patch is introducing a new MBOX API that is supporting multi-channel signalling and data exachange leveraging and extending the previous (and outdated) IPM API. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-10-15 17:55:56 +08:00
# SPDX-License-Identifier: Apache-2.0
drivers: syscalls: use zephyr_syscall_header This adds a few line use zephyr_syscall_header() to include headers containing syscall function prototypes. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2023-05-25 06:27:04 +08:00
zephyr_syscall_header(${ZEPHYR_BASE}/include/zephyr/drivers/mbox.h)
drivers: mbox: Introduce MBOX driver class One limitation of the current IPM API is that it is assuming that the hardware is only exporting one single channel through which the data can be sent or signalling can happen. If the hardware supports multiple channels, the IPM device must be instantiated (possibly in the DT) several times, one for each channel to be able to send data through multiple channels using the same hw peripheral. Also in the current IPM API only one callback can be registered, that means that only one driver is controlling all the signalling happening on all the channels. This patch is introducing a new MBOX API that is supporting multi-channel signalling and data exachange leveraging and extending the previous (and outdated) IPM API. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-10-15 17:55:56 +08:00
zephyr_library()
zephyr_library_sources_ifdef(CONFIG_USERSPACE mbox_handlers.c)
mbox: ipc: s/_MBOX_NRFX/_MBOX_NRFX_IPC/ Use a more precise Kconfig symbol name to avoid namespace conflicts when more NRFX-dependent drivers will be added. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-10-29 18:50:30 +08:00
zephyr_library_sources_ifdef(CONFIG_MBOX_NRFX_IPC mbox_nrfx_ipc.c)
drivers: mbox: add support for NXP S32 MRU Introduce NXP S32 Message Receive Unit (MRU) driver based of Mbox API. The MRU couples with a processor and allows to receive messages from senders, which are other modules or processors. Signed-off-by: Manuel Arguelles <manuel.arguelles@nxp.com>
2022-11-29 10:51:30 +08:00
zephyr_library_sources_ifdef(CONFIG_MBOX_NXP_S32_MRU mbox_nxp_s32_mru.c)
mbox: Add NXP MU as a MBOX device Add a MBOX driver wrapper around the NXP MU, simular to the existing wrapper around the NXP S32 MRU. This allows Zephyr IPC to work based on the MU, on a number of NXP boards. Also update the SHA of NXP HAL to enable the Kconfig for this driver. Signed-off-by: Yicheng Li <yichengli@google.com>
2023-08-23 05:55:36 +08:00
zephyr_library_sources_ifdef(CONFIG_MBOX_NXP_IMX_MU mbox_nxp_imx_mu.c)
drivers: mbox: Add Andestech mailbox driver Support the Andes mailbox driver via software plic. Signed-off-by: Kevin Wang <kevinwang821020@google.com>
2023-06-29 15:38:05 +08:00
zephyr_library_sources_ifdef(CONFIG_MBOX_ANDES_PLIC_SW mbox_andes_plic_sw.c)