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/Kconfig

38 lines
1.1 KiB
Plaintext
Raw Permalink 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
# Copyright (c) 2021 Carlo Caione <ccaione@baylibre.com>
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
# Copyright 2024 NXP
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
menuconfig MBOX
drivers: kconfig: unify menuconfig title strings Unify the drivers/*/Kconfig menuconfig title strings to the format "<class> [(acronym)] [bus] drivers". Including both the full name of the driver class and an acronym makes menuconfig more user friendly as some of the acronyms are less well-known than others. It also improves Kconfig search, both via menuconfig and via the generated Kconfig documentation. Signed-off-by: Henrik Brix Andersen <hebad@vestas.com>
2023-03-27 20:55:23 +08:00
bool "Multi-Channel Inter-Processor Mailbox (MBOX) drivers"
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
help
Include multi-channel interrupt-based inter-processor mailboxes
drivers in system configuration
mbox: Introduce MBOX NRFX IPC driver Rewrite the NRFX IPC driver to properly support multi-channel addressing leveraging the newly introduced MBOX APIs. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-10-15 17:56:21 +08:00
if MBOX
drivers: mbox: separate NRFx specific Kconfig Separate NRFx Mbox driver Kconfig to make place for other drivers. Signed-off-by: Manuel Arguelles <manuel.arguelles@nxp.com>
2022-11-29 10:51:29 +08:00
# Include these first so that any properties (e.g. defaults) below can be
# overridden (by defining symbols in multiple locations)
source "drivers/mbox/Kconfig.nrfx"
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
source "drivers/mbox/Kconfig.nxp_s32"
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
source "drivers/mbox/Kconfig.nxp_imx"
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
source "drivers/mbox/Kconfig.nxp_mailbox"
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
source "drivers/mbox/Kconfig.andes"
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
source "drivers/mbox/Kconfig.nrf_vevif_task"
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
source "drivers/mbox/Kconfig.nrf_vevif_event"
drivers: mbox: nrf_bellboard: add initial driver Add a new driver for nRF BELLBOARD peripheral, in both local and remote modes. Signed-off-by: Gerard Marull-Paretas <gerard@teslabs.com>
2024-02-22 23:26:00 +08:00
source "drivers/mbox/Kconfig.nrf_bellboard"
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
source "drivers/mbox/Kconfig.stm32_hsem"
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
source "drivers/mbox/Kconfig.esp32"
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
source "drivers/mbox/Kconfig.ivshmem"
drivers: mbox: separate NRFx specific Kconfig Separate NRFx Mbox driver Kconfig to make place for other drivers. Signed-off-by: Manuel Arguelles <manuel.arguelles@nxp.com>
2022-11-29 10:51:29 +08:00
drivers: mbox: Add configurable init priority Add configurable initialization priority. Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no>
2022-03-01 21:30:19 +08:00
config MBOX_INIT_PRIORITY
int "MBOX init priority"
drivers: mbox: initialize before ipc Change the default mbox initialization priority so that it initializes before ipc, as some ipc drivers depends on it. Found with: $ west build -p -b nrf5340dk_nrf5340_cpuapp \ samples/subsys/ipc/ipc_service/icmsg_me \ -DCONFIG_CHECK_INIT_PRIORITIES=y ... ERROR: /ipc/ipc1 POST_KERNEL 46 < /soc/peripheral@50000000/mbox@2a000 POST_KERNEL 50 ERROR: /ipc/ipc0 POST_KERNEL 46 < /soc/peripheral@50000000/mbox@2a000 POST_KERNEL 50 Signed-off-by: Fabio Baltieri <fabiobaltieri@google.com>
2023-07-11 00:19:25 +08:00
default 40
drivers: mbox: Add configurable init priority Add configurable initialization priority. Signed-off-by: Krzysztof Chruscinski <krzysztof.chruscinski@nordicsemi.no>
2022-03-01 21:30:19 +08:00
help
MBOX driver device initialization priority.
mbox: Introduce MBOX NRFX IPC driver Rewrite the NRFX IPC driver to properly support multi-channel addressing leveraging the newly introduced MBOX APIs. Signed-off-by: Carlo Caione <ccaione@baylibre.com>
2021-10-15 17:56:21 +08:00
module = MBOX
module-str = mbox
source "subsys/logging/Kconfig.template.log_config"
endif # MBOX