Home
last modified time | relevance | path

Searched full:receiver (Results 1 – 25 of 368) sorted by relevance

12345678910>>...15

/Zephyr-latest/drivers/modem/
Dmodem_receiver.h2 * @brief Modem receiver header file.
4 * A modem receiver driver allowing application to handle all
44 * @brief Gets receiver context by id.
46 * @param id: receiver context id.
48 * @retval Receiver context or NULL.
55 * @param ctx: receiver context.
66 * @brief Sends the data over specified receiver context.
68 * @param ctx: receiver context.
78 * @brief Registers receiver context.
82 * @param ctx: receiver context to register.
[all …]
Dmodem_receiver.c2 * @brief Modem receiver driver
4 * A modem receiver driver allowing application to handle all
31 * @brief Finds receiver context which manages provided device.
33 * @param dev: device used by the receiver context.
35 * @retval Receiver context or NULL.
51 * @brief Persists receiver context if there is a free place.
53 * @note Amount of stored receiver contexts is determined by
56 * @param ctx: receiver context to persist.
79 * @param ctx: receiver context.
96 * @brief Receiver UART interrupt handler.
[all …]
/Zephyr-latest/samples/bluetooth/tmap_bmr/
DREADME.rst2 :name: Telephone and Media Audio Profile (TMAP) Broadcast Media Receiver (BMR)
5 Implement the TMAP Broadcast Media Receiver (BMR) role.
10 Application demonstrating the TMAP Broadcast Media Receiver functionality.
/Zephyr-latest/samples/arch/smp/pktqueue/src/
Dmain.c9 /* Amount of parallel processed sender/receiver queues of packet headers */
45 /* Arrays of receiver and sender queues */
46 struct phdr_desc_queue sender[QUEUE_NUM], receiver[QUEUE_NUM]; variable
87 /* Thread takes packet from "sender" queue and puts it to "receiver" queue.
121 /* Thread that processes one pair of sender/receiver queue */
141 (void *)&receiver[queue_num], (void *)&queue_num, in queue_thread()
180 (void *)&sender[i], (void *)&receiver[i], in main()
195 * The counter of correct receiver queues */ in main()
198 /* Iterate and count amount of packages in receiver queues */ in main()
202 tmp = receiver[i].head; in main()
[all …]
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/
Dsar_cfg_cli.rst15 (SAR Transmitter and SAR Receiver) using SAR Configuration messages.
22 The SAR Receiver procedure is used to determine and configure the SAR Receiver state of a SAR
24 :c:func:`bt_mesh_sar_cfg_cli_receiver_set` are used to get and set the SAR Receiver state of the
Dsar_cfg_srv.rst15 The SAR Configuration Server model defines two states, SAR Transmitter state and SAR Receiver state.
18 The model also supports the SAR Transmitter and SAR Receiver get and set messages.
/Zephyr-latest/drivers/can/
DKconfig.loopback28 The TX thread calls the callbacks of the receiver
36 The TX thread calls the callbacks of the receiver
45 messages from this msgq and calls the respective receiver if the
/Zephyr-latest/samples/bluetooth/iso_receive/
DREADME.rst2 :name: Synchronized Receiver
5 Use Bluetooth LE Synchronized Receiver functionality.
11 Receiver functionality.
/Zephyr-latest/tests/drivers/uart/uart_errors/
DREADME.txt1 The purpose of this test is to validate UART receiver when error occurs on
3 certain bytes with parity enabled when receiver is configured without parity.
/Zephyr-latest/dts/bindings/mbox/
Dnxp,s32-mru.yaml19 In a normal use-case for IPC, the receiver core must enable and set the number
22 receiver to be able to transmit on it. There is no need to define the transmit
53 It should be set by the receiver core coupled with this MRU instance.
55 For example, if receiver A wants to Rx on channels 0 and 1, then A must
Dnxp,mbox-imx-mu.yaml18 It should be set by the receiver core coupled with this MU instance.
20 For example, if receiver A wants to Rx on channels 0 to 3, then A must
Dnxp,mbox-mailbox.yaml26 It should be set by the receiver core coupled with this Mailbox instance.
28 For example, if receiver A wants to Rx on channels 0 to 3, then A must
/Zephyr-latest/subsys/net/lib/ptp/
Dbtca.c43 diff = btca_port_id_cmp(&a->receiver, &a->sender); in btca_ds_cmp2()
54 diff = btca_port_id_cmp(&b->receiver, &b->sender); in btca_ds_cmp2()
73 if (a->receiver.port_number > b->receiver.port_number) { in btca_ds_cmp2()
76 if (a->receiver.port_number > b->receiver.port_number) { in btca_ds_cmp2()
/Zephyr-latest/kernel/
Dmailbox.c101 * @brief Check compatibility of sender's and receiver's message descriptors.
103 * Compares sender's and receiver's message descriptors to see if they are
131 /* update data size field for receiver only */ in mbox_message_match()
136 /* update data location fields for receiver only */ in mbox_message_match()
139 /* update syncing thread field for receiver only */ in mbox_message_match()
225 /* search mailbox's rx queue for a compatible receiver */ in mbox_message_put()
234 /* take receiver out of rx queue */ in mbox_message_put()
237 /* ready receiver for execution */ in mbox_message_put()
244 * if receiver has priority, otherwise let it continue in mbox_message_put()
247 * until the receiver consumes the message in mbox_message_put()
[all …]
/Zephyr-latest/tests/benchmarks/app_kernel/src/
Dreceiver.c1 /* receiver.c */
14 * _R : Is a file that contains the receiver task
18 #include "receiver.h"
/Zephyr-latest/samples/bluetooth/iso_broadcast_benchmark/
DREADME.rst14 *receiver* (multiple receivers may be used with no effect on the test)
17 The application is used as both a broadcaster and a receiver, and the mode
49 connected board in the receiver role.
53 #. Observe that the receiver synchronizes to the broadcaster.
54 #. Observe the receive statistics on the receiver(s).
58 The receiver will output statistics for overall (since boot), current sync
63 Choose device role - type r (receiver role) or b (broadcaster role), or q to quit: r
64 Receiver role
97 Choose device role - type r (receiver role) or b (broadcaster role), or q to quit: b
/Zephyr-latest/dts/bindings/misc/
Dzephyr,modbus-serial.yaml21 description: Receiver enable pin.
23 Receiver enable pin (nRE) of the RS-485 transceiver.
/Zephyr-latest/tests/bsim/bluetooth/mesh/tests_scripts/sar/
Dstress_test.sh8 # even with "stressed" transmitter and receiver configurations.
12 # 3. Configure SAR transmitter and receiver states.
Dslow_transfer_test.sh8 # even with transmitter and receiver configured with longest possible
13 # 3. Configure SAR transmitter and receiver states.
/Zephyr-latest/samples/bluetooth/peripheral_past/
DREADME.rst5 Use the Periodic Advertising Sync Transfer (PAST) feature as the receiver.
11 Transfer (PAST) functionality as the receiver.
/Zephyr-latest/tests/net/mgmt/src/
Dmgmt.c40 /* Receiver infra */
191 static int sending_event(uint32_t times, bool receiver, bool info) in sending_event() argument
193 TC_PRINT("- Sending event %u times, %s a receiver, %s info\n", in sending_event()
194 times, receiver ? "with" : "without", in sending_event()
201 if (receiver) { in sending_event()
210 if (receiver) { in sending_event()
224 static int test_sending_event(uint32_t times, bool receiver) in test_sending_event() argument
226 return sending_event(times, receiver, false); in test_sending_event()
229 static int test_sending_event_info(uint32_t times, bool receiver) in test_sending_event_info() argument
231 return sending_event(times, receiver, true); in test_sending_event_info()
/Zephyr-latest/subsys/bluetooth/controller/
DKconfig.dtm24 bool "HCI LE Receiver Test v3"
27 Enable support for the DTM Receiver test command v3.
/Zephyr-latest/dts/bindings/dai/
Dnxp,dai-sai.yaml70 2) The transmitter is in SYNC with the receiver (1)
81 for the receiver. At the moment, the only supported modes are:
82 1) The receiver is ASYNC (0)
83 2) The receiver is in SYNC with the transmitter (1)
84 If this property is not specified, the receiver will be set to ASYNC.
/Zephyr-latest/drivers/i2s/
DKconfig.sam_ssc31 an output or an input depending on whether the receiver is working
42 an output or an input depending on whether the receiver is working
/Zephyr-latest/samples/net/syslog_net/
Ddocker-test.sh15 start_docker "/usr/local/bin/syslog-receiver.py 2001:db8::2" || return $?
28 start_docker "/usr/local/bin/syslog-receiver.py 192.0.2.2" || return $?

12345678910>>...15