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

22 lines
1.2 KiB
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 NXP Mailbox driver for mbox This adds new NXP mailbox driver for MBOX device. NXP mailbox IP driver supports sending data between cores. It uses 32 bit register to trigger irq to other core. This driver implementation uses 4 bits for channel selection of triggering mode, 4 bits for channel selection of data transfer and rest 24 bits for data. NXP mailbox IP Reference Manual UM11126, Chapter 52. https://www.nxp.com/webapp/Download?colCode=UM11126 Signed-off-by: Tomas Galbicka <tomas.galbicka@nxp.com>
2024-01-31 00:00:00 +08:00
zephyr_library_sources_ifdef(CONFIG_MBOX_NXP_MAILBOX mbox_nxp_mailbox.c)
drivers: mbox: mbox_esp32: add support for esp32 MBOX driver as an alternative for IPM driver. Signed-off-by: Felipe Neves <ryukokki.felipe@gmail.com>
2024-07-31 22:38:08 +08:00
zephyr_library_sources_ifdef(CONFIG_MBOX_ESP32 mbox_esp32.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)
drivers: mbox: nrf: Change VEVIFs and BELLBOARD nomenclature Renaming 'LOCAL' to 'RX' and 'REMOTE' to 'TX'. This seems more descriptive and intuitive to use. Signed-off-by: Jakub Zymelka <jakub.zymelka@nordicsemi.no>
2024-05-22 19:26:25 +08:00
zephyr_library_sources_ifdef(CONFIG_MBOX_NRF_VEVIF_TASK_RX mbox_nrf_vevif_task_rx.c)
zephyr_library_sources_ifdef(CONFIG_MBOX_NRF_VEVIF_TASK_TX mbox_nrf_vevif_task_tx.c)
drivers: mbox: add initial driver for nRF VEVIF event Add a mailbox driver for VEVIF events (VPR irq). The driver can be built in either 'rx' or 'tx' configuration. The VPR sends the event, so it uses the 'tx' configuration, while the master core uses the 'rx' configuration of the driver to receive the VPR events. Signed-off-by: Jakub Zymelka <jakub.zymelka@nordicsemi.no>
2024-05-20 19:21:30 +08:00
zephyr_library_sources_ifdef(CONFIG_MBOX_NRF_VEVIF_EVENT_RX mbox_nrf_vevif_event_rx.c)
zephyr_library_sources_ifdef(CONFIG_MBOX_NRF_VEVIF_EVENT_TX mbox_nrf_vevif_event_tx.c)
drivers: mbox: nrf: Change VEVIFs and BELLBOARD nomenclature Renaming 'LOCAL' to 'RX' and 'REMOTE' to 'TX'. This seems more descriptive and intuitive to use. Signed-off-by: Jakub Zymelka <jakub.zymelka@nordicsemi.no>
2024-05-22 19:26:25 +08:00
zephyr_library_sources_ifdef(CONFIG_MBOX_NRF_BELLBOARD_RX mbox_nrf_bellboard_rx.c)
zephyr_library_sources_ifdef(CONFIG_MBOX_NRF_BELLBOARD_TX mbox_nrf_bellboard_tx.c)
drivers: mbox: Add driver for STM32 HSEM This driver implements a simple MBOX device which supports a single instance, two channels (one for each direction), and only signalling mode with no data transfer. Signalling to another core is achieved by taking and giving two hardware semaphores, similar to the STM32 HSEM IPM driver. Signed-off-by: Celina Sophie Kalus <hello@celinakalus.de>
2024-03-01 18:06:22 +08:00
zephyr_library_sources_ifdef(CONFIG_MBOX_STM32_HSEM mbox_stm32_hsem.c)
drivers: mbox: add IVSHMEM based mbox driver Add initial support of the mailbox driver based on the inter VM shared memory mechanism similar as the existing IPM driver. Signed-off-by: Felipe Neves <ryukokki.felipe@gmail.com>
2024-09-17 07:05:01 +08:00
zephyr_library_sources_ifdef(CONFIG_MBOX_IVSHMEM mbox_ivshmem.c)