Searched refs:waits (Results 1 – 25 of 40) sorted by relevance
12
| /Zephyr-latest/samples/drivers/jesd216/ |
| D | README.rst | 40 Support 1-1-2: instr 3Bh, 0 mode clocks, 8 waits
41 Support 1-1-4: instr 6Bh, 0 mode clocks, 8 waits
42 Support 1-2-2: instr BBh, 0 mode clocks, 4 waits
43 Support 1-4-4: instr EBh, 2 mode clocks, 4 waits
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.nrf_xrtc | 22 System clock source initialization waits until clock is available. In some
33 System clock source initialization waits until clock is stable. When this
|
| /Zephyr-latest/soc/native/inf_clock/ |
| D | Kconfig.soc | 12 sleep. Therefore do not use busy waits while waiting for something to happen
|
| /Zephyr-latest/samples/bluetooth/mesh_provisioner/ |
| D | README.rst | 18 key, then waits to receive an Unprovisioned Beacon from a device. If the
20 ``sw0`` :ref:`devicetree <dt-guide>` alias, the application then waits
|
| /Zephyr-latest/samples/drivers/led/lp5569/ |
| D | README.rst | 12 LEDs until they are off again. Afterwards, it turns them all on at once, waits
|
| /Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
| D | srpl_cli.rst | 27 Configuration Client waits for a response message to arrive in milliseconds. This value can be
|
| D | od_cli.rst | 27 :kconfig:option:`CONFIG_BT_MESH_OD_PRIV_PROXY_CLI_TIMEOUT` controls how long the Client waits for a
|
| D | sar_cfg.rst | 85 discard timer tells how long the lower transport layer waits before discarding the segmented message
229 The value of this state defines the time in seconds that the lower transport layer waits after
|
| /Zephyr-latest/samples/modules/mctp/mctp_host/ |
| D | README.rst | 9 endpoint id with the message "hello". Expects and waits for a response to this
|
| /Zephyr-latest/samples/net/sockets/sntp_client/ |
| D | README.rst | 20 When the application runs, it issues an SNTP request to the host and waits
|
| /Zephyr-latest/subsys/modem/backends/ |
| D | Kconfig | 31 This defines the delay, in milliseconds, that the backend waits
|
| /Zephyr-latest/doc/kernel/services/synchronization/ |
| D | mutexes.rst | 79 lock. Each time a higher priority thread waits on a mutex, the kernel adjusts
122 The following code builds on the example above, and waits indefinitely
129 The following code waits up to 100 milliseconds for the mutex to become
|
| D | condvar.rst | 72 The following code waits on the condition variable.
|
| D | semaphores.rst | 101 The following code builds on the example above, and waits up to 50 milliseconds
|
| D | events.rst | 116 The following code builds on the example above, and waits up to 50 milliseconds
|
| /Zephyr-latest/samples/bluetooth/iso_peripheral/ |
| D | README.rst | 11 The sample starts advertising, waits for a central to connect to it and set up an isochronous chann…
|
| /Zephyr-latest/samples/userspace/prod_consumer/ |
| D | README.rst | 40 - App A monitor thread in user mode waits for data in the message queue.
44 - Application B processing thread waits on new items in the queue. It
|
| /Zephyr-latest/doc/hardware/peripherals/ |
| D | uart.rst | 19 :c:func:`uart_poll_out`, is a blocking function and the thread waits until the given
|
| /Zephyr-latest/samples/drivers/ipm/ipm_esp32/ |
| D | README.rst | 13 message to the APP using the IPM driver, and waits for the APP response
|
| /Zephyr-latest/samples/bluetooth/extended_adv/ |
| D | README.rst | 17 Once the connection is established, the advertiser waits for 5 seconds to disconnect.
|
| /Zephyr-latest/doc/services/ipc/ipc_service/backends/ |
| D | ipc_service_icbmsg.rst | 24 …If there are not enough sequential blocks, it waits using the timeout provided in the parameter th…
309 * **Follower** - It waits for a binding message.
352 #. The initiator waits for any message from the follower using this endpoint address.
364 #. The follower waits for a binding message containing its endpoint name.
|
| /Zephyr-latest/subsys/logging/backends/ |
| D | Kconfig.rtt | 15 In panic mode backend always blocks and waits until there is space
|
| /Zephyr-latest/doc/kernel/memory_management/ |
| D | slabs.rst | 104 The following code builds on the example above, and waits up to 100 milliseconds
|
| /Zephyr-latest/doc/kernel/services/data_passing/ |
| D | pipes.rst | 84 the producer thread waits for a specified amount of time.
|
| D | mailboxes.rst | 207 The waiting period only limits how long the mailbox waits
324 message descriptors. For example, if thread A waits to receive a message
325 only from thread X and then thread B waits to receive a message from
|
12
