Home
last modified time | relevance | path

Searched full:messaging (Results 1 – 25 of 34) sorted by relevance

12

/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/bridge/
Dbrg_net_key_refresh.sh37 # d. Messaging is verified like in step 4b.
40 # f Messaging is verified like in step 4b.
42 # 6. Messaging is verified like in step 4b.
44 # 8. Messaging is verified like in step 4b.
46 # 10. Messaging is verified like in step 4b.
/Zephyr-latest/samples/drivers/ipm/ipm_imx/
DREADME.rst5 Implement inter-processor mailbox (IPM) on i.MX SoCs containing a Messaging Unit peripheral.
10 Messaging Unit peripheral. It reads the received data from the Messaging Unit
15 The i.MX Messaging Unit peripheral consists of four 32-bit transmit and receive
50 and write data into the Messaging Unit.
Dsample.yaml2 description: the sample reads the received data from the Messaging Unit using the
/Zephyr-latest/drivers/ipm/
DKconfig.imx17 Driver for NXP i.MX messaging unit
25 Select maximum message size for NXP i.MX messaging unit.
DKconfig24 Driver for Nordic nRF messaging unit, based
/Zephyr-latest/dts/bindings/ipc/
Dzephyr,ipc-icmsg-me-follower.yaml7 description: Multiendpoint inter core messaging backend in follower role
Dzephyr,ipc-icmsg-me-initiator.yaml7 description: Multiendpoint inter core messaging backend in initiator role
Dzephyr,ipc-icbmsg.yaml7 description: Inter-core messaging backend with dynamically allocated buffers
Dzephyr,ipc-icmsg.yaml7 description: Inter core messaging backend
/Zephyr-latest/drivers/mbox/
DKconfig.nrfx10 Driver for Nordic nRF messaging unit, based
/Zephyr-latest/dts/bindings/ipm/
Dnxp,imx-mu.yaml4 description: i.MX Messaging Unit
Dxlnx,zynqmp-ipi-mailbox.yaml5 messaging between two Xilinx Zynq UltraScale+ MPSoC IPI agents. Each IPI
/Zephyr-latest/soc/nxp/mcx/mcxw/
DKconfig.defconfig17 # Include intercore messaging component
/Zephyr-latest/samples/drivers/ipm/ipm_esp32/
DREADME.rst10 the software intercore messaging mechanism to be used in AMP applications.
16 ESP32 intercore messaging has up two four channels, the 0 and 1 are
/Zephyr-latest/doc/services/modbus/
Dindex.rst6 Modbus is an industrial messaging protocol. The protocol is specified
/Zephyr-latest/modules/
DKconfig.mcux392 bool "Include RF_IMU adapter for intercore messaging"
395 RF_IMU adapter is needed for intercore messaging.
/Zephyr-latest/subsys/usb/usb_c/
Dusbc_tc_src_states.c276 * responsibility to the Sink through USBPD VCONN_Swap messaging in tc_attached_src_run()
288 * messaging shall transition to Unattached.SRC when the in tc_attached_src_run()
Dusbc_pe_common_internal.h451 * @brief End and atomic messaging sequence
579 * @brief Return true if the PE is within an atomic messaging sequence
/Zephyr-latest/doc/connectivity/networking/api/
Dmqtt.rst15 publish/subscribe messaging transport for machine-to-machine communication.
/Zephyr-latest/doc/services/ipc/ipc_service/backends/
Dipc_service_icmsg.rst6 The inter core messaging backend (ICMsg) is a lighter alternative to the
/Zephyr-latest/samples/net/mqtt_sn_publisher/
DREADME.rst11 publish/subscribe messaging protocol optimized for small sensors and
/Zephyr-latest/subsys/net/ip/
DKconfig.ipv6172 int "Timeout of Router Solicitation messaging"
/Zephyr-latest/soc/nxp/imxrt/imxrt11xx/
Dsoc.c47 /* Dual core mode is enabled, and messaging unit is present */
741 /* Set boot flag in messaging unit to indicate boot to primary core */ in imxrt_init()
/Zephyr-latest/include/zephyr/drivers/
Dgnss.h88 /** Indoor Messaging System (IMES) */
/Zephyr-latest/doc/releases/
Drelease-notes-1.5.rst159 * ``ZEP-415`` - aaU, I want to use the NATS messaging protocol to send sensor data to the cloud

12