| /Zephyr-latest/tests/kernel/context/src/ |
| D | main.c | 821 struct timeout_order timeouts[] = { variable
831 #define NUM_TIMEOUT_THREADS ARRAY_SIZE(timeouts)
898 struct timeout_order *timeout = &timeouts[POINTER_TO_INT(num)]; in delayed_thread()
968 K_MSEC(timeouts[i].timeout)); in ZTEST()
1004 K_MSEC(timeouts[i].timeout)); in ZTEST()
1015 timeouts[i].q_order, timeouts[i].timeout, i); in ZTEST()
1018 if (timeouts[j].timeout_order == i) { in ZTEST()
|
| /Zephyr-latest/doc/connectivity/networking/api/ |
| D | net_timeout.rst | 14 clock to track timeouts, with both deadlines and durations measured with
25 Most network timeouts are shorter than the delay rollover, but a few protocols
30 the remaining time for these extended-duration timeouts.
|
| D | lwm2m.rst | 591 … Occurs if there is socket errors or message timeouts. Client have lost connection to the server.
|
| /Zephyr-latest/subsys/net/lib/ptp/ |
| D | port.c | 371 atomic_set_bit(&port->timeouts, PTP_PORT_TIMER_ANNOUNCE_TO); in port_timer_to_handler()
373 atomic_set_bit(&port->timeouts, PTP_PORT_TIMER_SYNC_TO); in port_timer_to_handler()
375 atomic_set_bit(&port->timeouts, PTP_PORT_TIMER_DELAY_TO); in port_timer_to_handler()
377 atomic_set_bit(&port->timeouts, PTP_PORT_TIMER_QUALIFICATION_TO); in port_timer_to_handler()
914 atomic_clear(&port->timeouts); in port_disable()
1206 atomic_test_bit(&port->timeouts, PTP_PORT_TIMER_QUALIFICATION_TO)) { in ptp_port_timer_event_gen()
1208 atomic_clear_bit(&port->timeouts, PTP_PORT_TIMER_QUALIFICATION_TO); in ptp_port_timer_event_gen()
1217 atomic_test_bit(&port->timeouts, PTP_PORT_TIMER_SYNC_TO)) { in ptp_port_timer_event_gen()
1222 atomic_clear_bit(&port->timeouts, PTP_PORT_TIMER_SYNC_TO); in ptp_port_timer_event_gen()
1229 atomic_test_bit(&port->timeouts, PTP_PORT_TIMER_ANNOUNCE_TO)) { in ptp_port_timer_event_gen()
[all …]
|
| D | port.h | 59 atomic_t timeouts; member
|
| D | ptp.c | 58 if (!atomic_test_bit(&port->timeouts, timeout_bit[i])) { in ptp_thread()
|
| D | Kconfig | 42 timers, depending on received PTP messages or timeouts actions defined
|
| /Zephyr-latest/doc/kernel/services/timing/ |
| D | clocks.rst | 41 timeouts) are expected to be in the range of 10 kHz, with software
106 What is meant by "current time" for relative timeouts depends on the context:
132 Finally, it is possible to specify timeouts as absolute times since
160 managing large numbers of timeouts is quadratic in the number of
161 active timeouts. The API design of the timeout queue was intended to
183 kernel must receive an announce call to trigger registered timeouts.
196 arriving timeouts for expiration.
273 likes, and then converted into kernel timeouts using
279 timeouts. But for many subsystems with simple needs, this may be
354 and :c:macro:`K_NO_WAIT`, and works identically for absolute timeouts as well
[all …]
|
| /Zephyr-latest/drivers/watchdog/ |
| D | Kconfig | 31 bool "Multistage timeouts"
34 Enable multistage operation of watchdog timeouts.
|
| /Zephyr-latest/lib/posix/options/ |
| D | Kconfig.timer | 76 bool "Support timeouts for some blocking POSIX services"
78 Enable mandatory timeouts for some blocking operations.
|
| /Zephyr-latest/drivers/timer/ |
| D | Kconfig.nrf_xrtc | 16 on kernel API is executed. Requested timeouts will be prolonged by the
|
| /Zephyr-latest/tests/drivers/watchdog/wdt_error_cases/ |
| D | README.txt | 56 3. These tests assume that watchdog driver supports multiple timeouts. Set
59 4. When all watchdog timeouts must have exactly the same watchdog timeout value
|
| /Zephyr-latest/drivers/flash/ |
| D | Kconfig.nrf_rram | 62 int "Multiplier for flash operation timeouts [x0.1]"
|
| D | Kconfig.nrf | 72 int "Multiplier for flash operation timeouts [x0.1]"
|
| /Zephyr-latest/subsys/task_wdt/ |
| D | Kconfig | 21 The timeouts for each channel are stored in an array. Allocate only
|
| /Zephyr-latest/scripts/coccinelle/ |
| D | int_ms_to_timeout.cocci | 4 // Convert legacy integer timeouts to timeout API
19 // ** Handle timeouts at the last position of kernel API arguments
|
| D | ms_timeout.cocci | 5 // timeouts be specified as integral milliseconds.
|
| /Zephyr-latest/doc/connectivity/networking/conn_mgr/ |
| D | implementation.rst | 196 …_timeout_persistence` for a detailed technical discussion on implementing timeouts and persistence.
405 Implementing timeouts and persistence
408 …stence_timeouts` for a high-level description of the expected behavior of timeouts and persistence.
|
| D | main.rst | 287 * :ref:`Connection timeouts <conn_mgr_control_timeouts>`
|
| /Zephyr-latest/boards/acrn/acrn/doc/ |
| D | index.rst | 264 with GRUB plugins or menus or timeouts:
|
| /Zephyr-latest/doc/connectivity/bluetooth/ |
| D | bluetooth-le-host.rst | 282 special cases for ATT timeouts.
|
| /Zephyr-latest/doc/develop/test/ |
| D | twister.rst | 224 Multiply each test scenario timeout by specified ratio. This option allows to tune timeouts only
924 Managing tests timeouts
927 There are several parameters which control tests timeouts on various levels:
933 * ``--timeout-multiplier`` twister option which can be used to adjust timeouts in exact twister run.
|
| /Zephyr-latest/kernel/ |
| D | Kconfig | 798 platforms (ones that support setting arbitrary interrupt timeouts) are
827 bool "Store kernel timeouts in 64 bit precision"
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-2.1.rst | 485 * :github:`20939` - long duration timeouts can cause loss of time
526 * :github:`20715` - rtc driver may interrupt in a short time for large timeouts on cc13x2/cc26x2
|
| D | release-notes-2.5.rst | 967 * :github:`19655` - Milestones toward generalized representation of timeouts
1028 …les/scheduler/metairq_dispatch: Regression after 30916 (sched: timeout: Do not miss slice timeouts)
1580 * :github:`29066` - kernel: k_sleep doesn't handle relative or absolute timeouts >INT_MAX
|
