Home
last modified time | relevance | path

Searched full:sending (Results 1 – 25 of 641) sorted by relevance

12345678910>>...26

/Zephyr-latest/samples/drivers/ipm/ipm_esp32/
DREADME.rst43 PRO_CPU is sending a request, waiting remote response...
45 PRO_CPU is sending a request, waiting remote response...
47 PRO_CPU is sending a request, waiting remote response...
49 PRO_CPU is sending a request, waiting remote response...
51 PRO_CPU is sending a request, waiting remote response...
53 PRO_CPU is sending a request, waiting remote response...
55 PRO_CPU is sending a request, waiting remote response...
57 PRO_CPU is sending a request, waiting remote response...
/Zephyr-latest/doc/kernel/services/data_passing/
Dmailboxes.rst31 A thread that sends a message is known as the **sending thread**,
45 Both the sending thread and the receiving thread supply a message descriptor
47 a message exchange between compatible sending and receiving threads.
69 it is given to a mailbox by the sending thread. The message is then owned
78 A sending thread can specify the address of the thread to which the message
83 A message is exchanged only when the requirements of both the sending thread
97 In a synchronous exchange, the sending thread blocks until the message
99 the sending thread does not wait until the message has been received
100 by another thread before continuing; this allows the sending thread to do
104 by the sending thread.
[all …]
/Zephyr-latest/samples/subsys/zbus/uart_bridge/
Dsample.yaml10 - "D: Core sending start measurement with status 0"
11 - "D: Peripheral sending sensor data"
15 - "D: Core sending start measurement with status 1"
DREADME.rst34 D: Core sending start measurement with status 0
37 D: Peripheral sending sensor data
47 D: Core sending start measurement with status 1
53 D: Peripheral sending sensor data
/Zephyr-latest/doc/connectivity/networking/api/
Dnet_core.rst13 The network subsystem contains two functions for sending and receiving
19 For sending, the ``net_send_data()`` can be used. Typically applications do not
21 for sending and receiving network data.
/Zephyr-latest/samples/net/mqtt_publisher/
DREADME.rst328 1485663797: Sending CONNACK to zephyr_publisher (0)
330 1485663798: Sending PINGRESP to zephyr_publisher
333 1485663799: Sending PUBACK to zephyr_publisher (Mid: 1888)
335 1485663799: Sending PUBREC to zephyr_publisher (Mid: 16356)
337 1485663799: Sending PUBCOMP to zephyr_publisher (Mid: 16356)
339 1485663800: Sending PINGRESP to zephyr_publisher
342 1485663801: Sending PUBACK to zephyr_publisher (Mid: 45861)
344 1485663801: Sending PUBREC to zephyr_publisher (Mid: 53870)
346 1485663801: Sending PUBCOMP to zephyr_publisher (Mid: 53870)
348 1485663802: Sending PINGRESP to zephyr_publisher
[all …]
/Zephyr-latest/subsys/sd/
DKconfig84 int "Number of times to retry sending command to card"
87 Number of times to retry sending command to SD card in case of failure
90 int "Number of times to retry sending data to card"
93 Number of times to retry sending data to SD card in case of failure
/Zephyr-latest/subsys/canbus/isotp/
DKconfig37 int "Ar and As timeout [ms] (sending and receiving timeout)"
56 (for classic CAN) and unused bytes must be padded by the sending
104 int "Number of data buffers for sending data"
116 for sending are allocated from.
124 This option enables buffered sending contexts. This makes send and
128 int "Amount of context buffers for sending data"
/Zephyr-latest/dts/bindings/auxdisplay/
Dhit,hd44780.yaml70 Delay time (in ns) to wait after enable line falls before sending
78 sending another command. Default is as per Hitachi HD44780 specification.
84 Delay time (in us) to wait after issuing a clear command before sending
91 Delay time (in ms) to wait at boot time before sending a command (note:
/Zephyr-latest/tests/bsim/bluetooth/mesh/src/
Dtest_transport.c23 * This file contains tests for sending and receiving messages end-to-end in
135 /** Test sending of unicast messages using the test vector.
146 ASSERT_OK_MSG(err, "Failed sending vector %d", i); in test_tx_unicast()
152 /** Test sending of group messages using the test vector.
163 ASSERT_OK_MSG(err, "Failed sending vector %d", i); in test_tx_group()
169 /** Test sending to a fixed group address. */
190 /** Test sending of virtual address messages using the test vector.
208 ASSERT_OK_MSG(err, "Failed sending vector %d", i); in test_tx_va()
214 /** Test sending the test vector using virtual addresses with collision.
234 LOG_INF("Sending msg #%d to %s addr", i, (j == 0 ? "first" : "second")); in test_tx_va_collision()
[all …]
/Zephyr-latest/subsys/ipc/ipc_service/backends/
DKconfig.icmsg_me7 int "Size of sending buffer size"
11 Size of a static buffer used for preparring data to send in sending
/Zephyr-latest/subsys/net/lib/mqtt_sn/
DKconfig63 Keep alive time for MQTT-SN (in seconds). Sending of Ping Requests to
81 int "Max time (seconds) to wait before sending SEARCHGW"
86 int "Max time (seconds) to wait before sending GWINFO"
/Zephyr-latest/doc/connectivity/networking/
Dnetwork_tracing.rst14 are enabled. The system will start to collect the receiving and sending call
16 It will also collect packet sending or receiving timings i.e., how long
/Zephyr-latest/include/zephyr/bluetooth/mesh/
Dcfg_cli.h512 * immediately after sending the command.
530 * return immediately after sending the command.
546 * return immediately after sending the command.
563 * return immediately after sending the command.
582 * return immediately after sending the command.
600 * return immediately after sending the command.
614 * return immediately after sending the command.
629 * return immediately after sending the command.
645 * return immediately after sending the command.
664 * return immediately after sending the command.
[all …]
Dblob_cli.h38 * while sending chunks to the Target node.
57 * Needs to be initialized when sending a BLOB in Pull mode.
65 acked:1, /* Message has been acknowledged. Not used when sending. */
168 /** Sending transfer start. */
170 /** Sending block start. */
172 /** Sending block chunks. */
285 /* Defines a time in ms by which the broadcast API postpones sending the message to a next
309 uint8_t sending : 1, member
349 * Starts sending the transfer to the Target nodes. Only Target nodes with a
427 /** @brief Set chunk sending interval in ms
[all …]
Dhealth_cli.h104 * This callback is called before sending the periodic publication message.
110 * @param cli Health client that is sending the periodic publication message.
136 * sending the command.
162 * sending the command.
201 * for response and will return immediately after sending the command.
245 * return immediately after sending the command.
272 * return immediately after sending the command.
306 * return immediately after sending the command.
325 * return immediately after sending the command.
/Zephyr-latest/samples/bluetooth/iso_broadcast_benchmark/
DREADME.rst109 [00:00:09.196,472] <inf> iso_broadcast_broadcaster: Sending value 100
110 [00:00:09.587,036] <inf> iso_broadcast_broadcaster: Sending value 200
111 [00:00:09.977,722] <inf> iso_broadcast_broadcaster: Sending value 300
112 [00:00:10.368,347] <inf> iso_broadcast_broadcaster: Sending value 400
113 [00:00:10.758,972] <inf> iso_broadcast_broadcaster: Sending value 500
114 [00:00:11.149,597] <inf> iso_broadcast_broadcaster: Sending value 600
115 [00:00:11.540,222] <inf> iso_broadcast_broadcaster: Sending value 700
/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/op_agg/
Dmodel_coex.sh16 # 2. The Tester device immediately starts sending the sequence.
18 # Then it starts sending its own aggregated sequence.
/Zephyr-latest/subsys/mgmt/ec_host_cmd/backends/
Dec_host_cmd_backend_uart.c53 * moved to sending state.
65 * host is sending extra bytes which indicates data overrun.
162 LOG_ERR("UART HOST CMD ERROR: Received data while processing or sending"); in uart_callback()
220 LOG_ERR("UART HOST CMD ERROR: unexpected end of sending"); in uart_callback()
276 LOG_ERR("UART HOST CMD ERROR: unexpected state while sending"); in ec_host_cmd_uart_send()
283 * Enable receiving to be ready to get a new command right after sending the response. in ec_host_cmd_uart_send()
293 /* If sending fails, reset the state */ in ec_host_cmd_uart_send()
296 LOG_ERR("UART HOST CMD ERROR: sending failed"); in ec_host_cmd_uart_send()
/Zephyr-latest/dts/bindings/fpga/
Dlattice,ice40-fpga-base.yaml42 Prior to sending the bitstream, issue this number of leading clocks with SPI_CS pulled high.
48 After sending the bitstream, issue this number of trailing clocks with SPI_CS pulled high.
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dbrg_cfg.rst71 feature on a node by sending a **Subnet Bridge Set** message to the Bridge Configuration
77 The Bridge Configuration Client can add or remove an entry from the Bridging Table by sending a
91 The Bridge Configuration Client can retrieve this information by sending a **Subnet Bridge Get**
95 entries from a Bridging Table by sending a **Bridging Table Get** message to the target node using
98 The Client can get a list of subnets currently bridged by a Subnet Bridge by sending a
103 store. The Client can retrieve this information by sending a **Bridging Table Size Get** message
/Zephyr-latest/dts/bindings/mipi-dbi/
Dzephyr,mipi-dbi-bitbang.yaml19 Data/command GPIO pin. Set to low when sending a command, or high when sending data.
Dzephyr,mipi-dbi-spi.yaml23 Set to low when sending a command, or high when sending data.
/Zephyr-latest/tests/bsim/bluetooth/host/att/eatt/src/
Dmain_collision.c27 FAIL("Sending credit based connection request failed (err %d)\n", err); in test_peripheral_main()
55 FAIL("Sending credit based connection request failed (err %d)\n", err); in test_central_main()
/Zephyr-latest/subsys/bluetooth/host/
DKconfig.gatt22 These buffers are only used for sending anything over ATT.
95 bt_conn_set_security() to re-establish security prior to sending any
173 When enabled, this option will make the server block sending
208 This option if enabled allows automatically sending request for ATT
216 This option if enabled allows automatically sending request for connection

12345678910>>...26