Home
last modified time | relevance | path

Searched full:message (Results 1 – 25 of 1640) sorted by relevance

12345678910>>...66

/Zephyr-latest/cmake/usage/
Dusage.cmake3 message(FATAL_ERROR "ZEPHYR_BASE not set")
13 message("Cleaning targets:")
14 message(" clean - Remove most generated files but keep configuration and backup files")
15 message(" pristine - Remove all files in the build directory")
16 message("")
17 message("Kconfig targets:")
18 message(" menuconfig - Update .config using a console-based interface")
19 message(" guiconfig - Update .config using a graphical interface")
20 message("")
21 message("Other generic targets:")
[all …]
/Zephyr-latest/samples/subsys/portability/cmsis_rtos_v1/timer_synchronization/
DREADME.rst4 Use timers and message queues from CMSIS RTOS v1 API to synchronize threads.
8 The sample project illustrates usage of timers and message queues using
11 The main thread creates a preemptive thread which writes message to message queue
12 and on timer expiry, message is read by main thread.
32 Wrote to message queue: 5
33 Read from message queue: 5
35 Wrote to message queue: 6
36 Read from message queue: 6
38 Wrote to message queue: 7
39 Read from message queue: 7
[all …]
/Zephyr-latest/samples/subsys/portability/cmsis_rtos_v2/timer_synchronization/
DREADME.rst4 Use timers and message queues from CMSIS RTOS v2 API to synchronize threads.
8 The sample project illustrates usage of timers and message queues using
11 The main thread creates a preemptive thread which writes message to message queue
12 and on timer expiry, message is read by main thread.
32 Wrote to message queue: 5
33 Read from message queue: 5
35 Wrote to message queue: 6
36 Read from message queue: 6
38 Wrote to message queue: 7
39 Read from message queue: 7
[all …]
/Zephyr-latest/doc/kernel/services/data_passing/
Dmailboxes.rst6 A :dfn:`mailbox` is a kernel object that provides enhanced message queue
7 capabilities that go beyond the capabilities of a message queue object.
25 * A **receive queue** of threads that are waiting to receive a message.
31 A thread that sends a message is known as the **sending thread**,
32 while a thread that receives the message is known as the **receiving thread**.
33 Each message may be received by only one thread (i.e. point-to-multipoint and
40 Message Format
43 A **message descriptor** is a data structure that specifies where a message's
44 data is located, and how the message is to be handled by the mailbox.
45 Both the sending thread and the receiving thread supply a message descriptor
[all …]
Dmessage_queues.rst3 Message Queues
6 A :dfn:`message queue` is a kernel object that implements a simple
7 message queue, allowing threads and ISRs to asynchronously send and receive
17 Any number of message queues can be defined (limited only by available RAM).
18 Each message queue is referenced by its memory address.
20 A message queue has the following key properties:
28 A message queue must be initialized before it can be used.
31 A data item can be **sent** to a message queue by a thread or an ISR.
33 if one exists; otherwise the item is copied to the message queue's ring buffer,
35 *must* equal the message queue's data item size.
[all …]
/Zephyr-latest/subsys/net/lib/ptp/
Dmsg.h31 /* values of the bits of the flagField array for PTP message */
37 * @brief PTP message type.
40 /* PTP event message types */
45 /* General PTP message types */
55 * @brief Common PTP message header.
58 /** PTP message type and most significant 4 bytes of SdoId. */
62 /** Number of bytes in the message. */
68 /** Array of message flags. */
78 /** unique ID number of the message. */
84 /** Logarithm base of 2 of message interval. */
[all …]
/Zephyr-latest/subsys/bluetooth/mesh/
Dmsg.h7 /** @brief Send a model message.
9 * Sends a model message with the given context. If the message context is NULL, this
10 * updates the publish message, and publishes with the configured publication parameters.
12 * @param model Model to send the message on.
13 * @param ctx Message context, or NULL to send with the configured publish parameters.
14 * @param buf Message to send.
16 * @retval 0 The message was sent successfully.
17 * @retval -ENOTSUP A message context was not provided and publishing is not supported.
18 * @retval -EADDRNOTAVAIL A message context was not provided and publishing is not configured.
25 * Message response context.
[all …]
/Zephyr-latest/samples/subsys/zbus/confirmed_channel/
Dsample.yaml2 name: Confirmed message
10 - "I: From listener -> Confirmed message payload = 0"
11 - "I: From bar_sub1 subscriber -> Confirmed message payload = 0"
12 - "I: From bar_sub2 subscriber -> Confirmed message payload = 0"
13 - "I: From bar_sub3 subscriber -> Confirmed message payload = 0"
14 - "I: From listener -> Confirmed message payload = 1"
15 - "I: From bar_sub1 subscriber -> Confirmed message payload = 1"
16 - "I: From bar_sub2 subscriber -> Confirmed message payload = 1"
17 - "I: From bar_sub3 subscriber -> Confirmed message payload = 1"
18 - "I: From listener -> Confirmed message payload = 2"
[all …]
DREADME.rst5 Use confirmed zbus channels to ensure all subscribers consume a message.
10 The confirmed channel can only be published when all the subscribers consume the message.
29 I: From listener -> Confirmed message payload = 0
30 I: From bar_sub2 subscriber -> Confirmed message payload = 0
31 I: From bar_sub1 subscriber -> Confirmed message payload = 0
32 I: From bar_sub3 subscriber -> Confirmed message payload = 0
33 I: From listener -> Confirmed message payload = 1
34 I: From bar_sub2 subscriber -> Confirmed message payload = 1
35 I: From bar_sub1 subscriber -> Confirmed message payload = 1
36 I: From bar_sub3 subscriber -> Confirmed message payload = 1
[all …]
/Zephyr-latest/include/zephyr/bluetooth/mesh/
Dmsg.h2 * @brief Message APIs.
14 * @brief Message
15 * @defgroup bt_mesh_msg Message
42 * @brief Helper for model message buffer length.
44 * Returns the length of a Mesh model message buffer, including the opcode
47 * @param _op Opcode of the message.
54 * @brief Helper for model message buffer length.
56 * Returns the length of a Mesh model message buffer, including the opcode
59 * @param _op Opcode of the message.
66 * @brief Define a Mesh model message buffer using @ref NET_BUF_SIMPLE_DEFINE.
[all …]
/Zephyr-latest/drivers/usb_c/tcpc/
Ducpd_stm32_priv.h22 * @brief The message header consists of 2-bytes
27 * @brief USB PD message buffer length.
35 * used to receive a message
44 * used to receive a message
53 * used to transmit a message
63 * used to transmit a message
123 * @brief PD message send retry count for Rev 2.0
128 * @brief PD message send retry count for Rev 3.0
136 /* Request to send a goodCRC message */
138 /* Request to send a power delivery message */
[all …]
/Zephyr-latest/lib/posix/options/
DKconfig.mqueue6 bool "POSIX message queue support"
8 This enabled POSIX message queue related APIs.
13 int "Maximum number of messages in a POSIX message queue"
16 Mention maximum number of messages in message queue in POSIX compliant
20 int "Maximum number of POSIX message priorities"
23 Maximum number of message priorities supported by the implementation.
26 int "Maximum size of a POSIX message"
29 Mention maximum size of message in bytes.
32 int "Maximum POSIX message queue name size"
36 Mention size of message queue name in number of characters.
/Zephyr-latest/soc/intel/intel_adsp/common/include/
Dintel_adsp_ipc.h17 * @brief Intel ADSP IPC Message Handler Callback.
21 * foreign/connected IPC context. The message contents of the TDR and
24 * The function should return true if processing of the message is
31 * received while an in-progress message remains incomplete!
35 * @param data Message data from other side (low bits of TDR register).
36 * @param ext_dat Extended message data (TDD register).
37 * @return true if the message is completely handled.
43 * @brief Intel ADSP IPC Message Complete Callback.
48 * previously sent message is finished processing).
60 * signalling IPC message completion and those actions should be done by
[all …]
/Zephyr-latest/include/zephyr/usb/
Dusbd_msg.h9 * @brief USB support message types and structure
30 * @brief USB device support message types
32 * The first set of message types map to event types from the UDC driver API.
35 /** VBUS ready message (optional) */
37 /** VBUS removed message (optional) */
39 /** Device resume message */
41 /** Device suspended message */
47 /** Non-correctable UDC error message */
49 /** Unrecoverable device stack error message */
55 /** Maximum number of message types */
[all …]
/Zephyr-latest/samples/modules/nanopb/src/
Dmain.c19 /* Allocate space on the stack to store the message data. in encode_message()
26 SimpleMessage message = SimpleMessage_init_zero; in encode_message() local
32 message.lucky_number = 13; in encode_message()
34 message.buffer[i] = (uint8_t)(i * 2); in encode_message()
37 message.unlucky_number = 42; in encode_message()
40 /* Now we are ready to encode the message! */ in encode_message()
41 status = pb_encode(&stream, SimpleMessage_fields, &message); in encode_message()
55 /* Allocate space for the decoded message. */ in decode_message()
56 SimpleMessage message = SimpleMessage_init_zero; in decode_message() local
61 /* Now we are ready to decode the message. */ in decode_message()
[all …]
/Zephyr-latest/soc/intel/intel_adsp/ace/
Dcomm_widget.h17 * These registers control the DSP Communication Widget for generic sideband message transmit /
23 * Attribute register for downstream message.
31 * Destination Port ID received in message.
39 * Source Port ID received in message.
47 * Opcode received in message.
55 * Byte enables received in message.
68 * Address register (lower 32 bits) for downstream message.
72 * LSB 32 address bits received in message. Bits 32:16 of the LSB address only
80 * Address register (upper 32 bits) for downstream message.
88 * MSB 16 address bits received in message. Valid only when ADDRLEN bit is set to 1.
[all …]
/Zephyr-latest/doc/services/ipc/ipc_service/backends/
Dipc_service_icbmsg.rst29 * A message containing the block index is sent over ICMsg to the receiver.
33 * When data is no longer needed, the backend sends a release message over ICMsg.
34 * When the backend receives this message, it deallocates all blocks.
104 …g uses two shared memory regions, ``rx-region`` for message receiving, and ``tx-region`` for messa…
135 …* ICMsg message size for 4 bytes of content (refer to the ICMsg specification) multiplied by ``loc…
165 Message Transfer
170 * **Binding message** - Message exchanged during endpoint binding process (described below).
171 * **Data message** - Message carrying actual data from a user.
176 #. The sender wants to send a message that contains ``K`` bytes.
178 …additional ``+ 4`` bytes are reserved for the header, which contains the exact size of the message.
[all …]
/Zephyr-latest/tests/drivers/can/host/pytest/
Dtest_can.py22 can.Message(arbitration_id=0x10,
27 can.Message(arbitration_id=0x20,
33 can.Message(arbitration_id=0x30,
39 can.Message(arbitration_id=0x40,
46 can.Message(arbitration_id=0x50,
59 def check_rx(tx: can.Message, rx: can.Message) -> None: argument
60 """Check if received message matches transmitted message."""
65 pytest.fail('no message received')
69 pytest.fail(f'rx message "{rx}" not equal to tx message "{tx}"')
72 def skip_if_unsupported(can_dut: BusABC, can_host: BusABC, msg: can.Message) -> None: argument
[all …]
/Zephyr-latest/modules/lvgl/
DKconfig.input14 int "Input pointer queue message count"
18 Size of the pointer message queue buffering input events.
27 int "Input button queue message count"
31 Size of the button message queue buffering input events.
40 int "Input encoder queue message count"
44 Size of the encoder message queue buffering input events.
53 int "Input keypad queue message count"
57 Size of the keypad message queue buffering input events.
/Zephyr-latest/include/zephyr/drivers/firmware/scmi/
Dprotocol.h21 * @brief Build an SCMI message header
23 * Builds an SCMI message header based on the
26 * @param id message ID
27 * @param type message type
29 * @param token message token
40 * @brief SCMI message type
43 /** command message */
45 /** delayed reply message */
47 /** notification message */
88 * @brief SCMI message structure
[all …]
/Zephyr-latest/samples/subsys/ipc/rpmsg_service/
DREADME.rst50 Reset the board and the following message will appear on the corresponding
59 Master core received a message: 1
60 Master core received a message: 3
61 Master core received a message: 5
63 Master core received a message: 99
73 Remote core received a message: 0
74 Remote core received a message: 2
75 Remote core received a message: 4
77 Remote core received a message: 98
111 Master core received a message: 1
[all …]
/Zephyr-latest/drivers/wifi/nrf_wifi/inc/
Dcoex_struct.h17 /* Max size of message buffer (exchanged between host and MAC). This is in "bytes" */
31 * beyond supported message buffer size for WAIT_STATE_1_TIME register
66 * struct coex_collect_sr_traffic_info - Message from CD to CM to request SR traffic info.
67 * @message_id: Indicates message ID. This is to be set to COLLECT_SR_TRAFFIC_INFO.
70 * Message from CD to CM to request SR traffic information.
78 * struct coex_ch_configuration -Message from CD to CM to configure CH.
79 * @message_id: Indicates message ID. This is to be set to HW_CONFIGURATION.
85 * Message from CD to CM to configure CH
96 * struct coex_allocate_pti_window - Message to CM to request a priority window.
97 * @message_id: Indicates message ID. This is to be set to ALLOCATE_PTI_WINDOW.
[all …]
/Zephyr-latest/drivers/gnss/
Dgnss_nmea0183.h24 * @brief Encapsulate str in NMEA0183 message format
40 * @param argv Array of arguments split by ',' including message id and checksum
43 * @retval true if message is intact
44 * @retval false if message is corrupted
102 * @brief Parses NMEA0183 RMC message
105 * from the NMEA0183 RMC message provided as an array of strings split by ','
107 * @param argv Array of arguments split by ',' including message id and checksum
109 * @param data Destination for data parsed from NMEA0183 RMC message
117 * @brief Parses NMEA0183 GGA message
120 * fix, HDOP, and altitude (geoid separation) from the NMEA0183 GGA message provided
[all …]
/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/op_agg/
Dfull_status_msg_list.sh8 # access payload message and that the status item messages are received in the correct order.
9 # Spec 3.7.2: "With a 32-bit TransMIC field, the maximum size of the Access message is 380 octets."
10 # Spec 4.4.19.2: "When an Access message or an empty item is added to the message results list,
11 # it shall be located at the same index as the corresponding Access message from
12 # the message request list."
17 # 3. The client sends X vendor model messages, making up an op agg sequence message of 380 bytes.
18 # 4. The client sends the sequence message with the previously configured context,
19 # expecting an op agg status message of 380 bytes in return.
/Zephyr-latest/samples/subsys/ipc/ipc_service/multi_endpoint/remote/src/
Dmain.c62 unsigned char message = 0; in ipc0A_entry() local
84 while (message < 99) { in ipc0A_entry()
86 message = ipc0A_received_data; in ipc0A_entry()
88 printk("REMOTE [0A]: %d\n", message); in ipc0A_entry()
90 message++; in ipc0A_entry()
92 ret = ipc_service_send(&ipc0A_ept, &message, sizeof(message)); in ipc0A_entry()
94 printk("send_message(%d) failed with ret %d\n", message, ret); in ipc0A_entry()
134 unsigned char message = 0; in ipc0B_entry() local
163 while (message < 99) { in ipc0B_entry()
165 message = ipc0B_received_data; in ipc0B_entry()
[all …]

12345678910>>...66