| /Zephyr-Core-3.5.0/cmake/usage/ |
| D | usage.cmake | 3 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-Core-3.5.0/samples/subsys/portability/cmsis_rtos_v1/timer_synchronization/ |
| D | README.rst | 4 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-Core-3.5.0/samples/subsys/portability/cmsis_rtos_v2/timer_synchronization/ |
| D | README.rst | 4 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-Core-3.5.0/doc/kernel/services/data_passing/ |
| D | mailboxes.rst | 6 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 …]
|
| D | message_queues.rst | 3 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-Core-3.5.0/subsys/bluetooth/mesh/ |
| D | msg.h | 7 /** @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-Core-3.5.0/samples/subsys/zbus/confirmed_channel/ |
| D | sample.yaml | 2 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 …]
|
| D | README.rst | 5 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-Core-3.5.0/drivers/usb_c/tcpc/ |
| D | ucpd_stm32_priv.h | 22 * @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-Core-3.5.0/include/zephyr/bluetooth/mesh/ |
| D | msg.h | 2 * @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-Core-3.5.0/soc/xtensa/intel_adsp/common/include/ |
| D | intel_adsp_ipc.h | 20 * @brief Intel ADSP IPC Message Handler Callback.
24 * foreign/connected IPC context. The message contents of the TDR and
27 * The function should return true if processing of the message is
34 * received while an in-progress message remains incomplete!
38 * @param data Message data from other side (low bits of TDR register).
39 * @param ext_dat Extended message data (TDD register).
40 * @return true if the message is completely handled.
46 * @brief Intel ADSP IPC Message Complete Callback.
51 * previously sent message is finished processing).
63 * signalling IPC message completion and those actions should be done by
[all …]
|
| /Zephyr-Core-3.5.0/soc/xtensa/intel_adsp/ace/ |
| D | comm_widget.h | 17 * 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-Core-3.5.0/samples/modules/nanopb/src/ |
| D | main.c | 19 /* 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 /* Now we are ready to encode the message! */ in encode_message()
38 status = pb_encode(&stream, SimpleMessage_fields, &message); in encode_message()
52 /* Allocate space for the decoded message. */ in decode_message()
53 SimpleMessage message = SimpleMessage_init_zero; in decode_message() local
58 /* Now we are ready to decode the message. */ in decode_message()
59 status = pb_decode(&stream, SimpleMessage_fields, &message); in decode_message()
[all …]
|
| /Zephyr-Core-3.5.0/lib/posix/ |
| D | Kconfig.mqueue | 6 bool "POSIX message queue"
9 This enabled POSIX message queue related APIs.
14 int "Maximum number of messages in message queue"
17 Mention maximum number of messages in message queue in POSIX compliant
21 int "Maximum size of a message"
24 Mention maximum size of message in bytes.
31 Mention length of message queue name in number of characters.
|
| /Zephyr-Core-3.5.0/include/zephyr/logging/ |
| D | log_msg.h | 40 * @brief Log message API
41 * @defgroup log_msg Log message API
124 /** @brief Method used for creating a log message.
134 * function for creating a message. It takes code size than
139 /* Mode calculates size of the message and allocates it and writes
140 * directly to the message space. It is the fastest method but requires
169 /* During test fill with 0's to simplify message comparison */ \
174 * fixed size arrays and take the smallest one that will fit the message.
203 /* During test fill with 0's to simplify message comparison */ \
221 * is below the active memory during message construction. As a result,
[all …]
|
| /Zephyr-Core-3.5.0/samples/subsys/logging/syst/ |
| D | README.rst | 18 Build the Sys-T Message Parser
90 [ 0.020000] <err> syst: Error message example.
91 [ 0.020000] <wrn> syst: Warning message example.
92 [ 0.020000] <inf> syst: Info message example.
93 [ 0.020000] <dbg> syst: Debug message example.
94 [ 0.020000] <dbg> syst: Debug message example, 1
95 [ 0.020000] <dbg> syst: Debug message example, 1, 2
96 [ 0.020000] <dbg> syst: Debug message example, 1, 2, 3
97 [ 0.020000] <dbg> syst: Debug message example, 1, 2, 3, 0x4
103 [ 0.030000] <dbg> syst: Debug message example, %f
[all …]
|
| /Zephyr-Core-3.5.0/samples/subsys/ipc/ipc_service/icmsg_me/remote/src/ |
| D | main.c | 62 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 …]
|
| /Zephyr-Core-3.5.0/samples/subsys/ipc/ipc_service/icmsg_me/src/ |
| D | main.c | 62 unsigned char message = 0; in ipc0A_entry() local
91 while (message < 100) { 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()
99 message = ipc0A_received_data; in ipc0A_entry()
101 printk("HOST [0A]: %d\n", message); in ipc0A_entry()
102 message++; in ipc0A_entry()
140 unsigned char message = 0; in ipc0B_entry() local
162 while (message < 100) { in ipc0B_entry()
163 ret = ipc_service_send(&ipc0B_ept, &message, sizeof(message)); in ipc0B_entry()
[all …]
|
| /Zephyr-Core-3.5.0/tests/bsim/bluetooth/mesh/src/ |
| D | test_scanner.c | 24 /* Create a valid message */
109 /** Test sending message with not supported ad type for mesh.
111 * First message send message with an ad data type not supported by mesh, and
112 * verify that the receiver is disregarding message. Then send the same message
113 * with correct ad type to verify that the message is received.
123 /* Send message with invalid ad type. */ in test_tx_invalid_ad_type()
127 /* Wait for no message receive window to end. */ in test_tx_invalid_ad_type()
130 /* Send message with valid ad type to verify message. */ in test_tx_invalid_ad_type()
137 /** Test sending message with invalid/valid ad type and wrong packet length.
140 * disregarding message. Then send the same message with correct packet length
[all …]
|
| /Zephyr-Core-3.5.0/tests/bsim/bluetooth/mesh/tests_scripts/op_agg/ |
| D | full_status_msg_list.sh | 8 # 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-Core-3.5.0/samples/subsys/ipc/rpmsg_service/ |
| D | README.rst | 48 Reset the board and the following message will appear on the corresponding
57 Master core received a message: 1
58 Master core received a message: 3
59 Master core received a message: 5
61 Master core received a message: 99
71 Remote core received a message: 0
72 Remote core received a message: 2
73 Remote core received a message: 4
75 Remote core received a message: 98
109 Master core received a message: 1
[all …]
|
| /Zephyr-Core-3.5.0/include/zephyr/drivers/usb_c/ |
| D | usbc_pd.h | 31 * @brief Maximum length of a non-Extended Message in bytes.
38 * @brief Maximum length of an Extended Message in bytes.
45 * @brief Maximum length of a Chunked Message in bytes.
115 * before initiating an AMS by sending a Message.
122 * before initiating an AMS by sending a Message.
129 * Source_Capabilities message while the following is true:
138 * Source_Capabilities message while the following is true:
148 * @brief Minimum time a sink shall wait for a Source_Capabilities message
156 * @brief Minimum time a sink shall wait for a Source_Capabilities message
263 * @brief Minimum time to wait before sending another request after receiving a Wait message
[all …]
|
| /Zephyr-Core-3.5.0/doc/connectivity/bluetooth/api/mesh/ |
| D | msg.rst | 3 Message chapter
6 The Bluetooth mesh message provides set of structures, macros and functions used
7 for preparing message buffers, managing message and acknowledged message
|
| /Zephyr-Core-3.5.0/tests/subsys/logging/log_switch_format/src/ |
| D | mock_backend.h | 22 * @brief This function validates the log message.
24 * @param type Field in message header to indicate the type of SyS-T message.
25 * @param optional_flags Optional Flags in message header.
26 * @param module_id ModuleID in a Message Header distinguish between multiple
28 * @param sub_type Enumerated types for representing the sub-type of a Message.
29 * @param payload The content of the Message.
|
| /Zephyr-Core-3.5.0/modules/lvgl/ |
| D | Kconfig.input | 16 int "Keyboard scan message queue count maximum"
19 Maximum number of items in the keyboard scan message queue.
48 int "Input pointer queue message count"
52 Size of the pointer message queue buffering input events.
61 int "Input button queue message count"
65 Size of the button message queue buffering input events.
74 int "Input encoder queue message count"
78 Size of the encoder message queue buffering input events.
|
