Home
last modified time | relevance | path

Searched refs:expire (Results 1 – 14 of 14) sorted by relevance

/Zephyr-Core-3.7.0/drivers/ethernet/
DKconfig.enc28j6039 of the driver will wait for the OST to expire, indicated
/Zephyr-Core-3.7.0/subsys/net/lib/dhcpv6/
Ddhcpv6.c135 if (iface->config.dhcpv6.expire < expire_abs) { in dhcvp6_update_deadlines()
136 iface->config.dhcpv6.expire = expire_abs; in dhcvp6_update_deadlines()
1668 iface->config.dhcpv6.expire = now; in dhcpv6_handle_reply()
1911 if ((have_addr || have_prefix) && now < iface->config.dhcpv6.expire) { in dhcpv6_manage_timers()
1916 iface->config.dhcpv6.expire = now + DHCPV6_CNF_MAX_RD; in dhcpv6_manage_timers()
1963 if (now >= iface->config.dhcpv6.expire) { in dhcpv6_manage_timers()
1977 if (iface->config.dhcpv6.timeout > iface->config.dhcpv6.expire) { in dhcpv6_manage_timers()
1978 iface->config.dhcpv6.timeout = iface->config.dhcpv6.expire; in dhcpv6_manage_timers()
2003 if (now >= iface->config.dhcpv6.expire) { in dhcpv6_manage_timers()
2017 if (iface->config.dhcpv6.timeout > iface->config.dhcpv6.expire) { in dhcpv6_manage_timers()
[all …]
/Zephyr-Core-3.7.0/tests/drivers/watchdog/wdt_error_cases/
DREADME.txt17 Therefore, in all test cases watchdog shall NOT expire.
/Zephyr-Core-3.7.0/subsys/net/ip/
DKconfig.ipv6179 generated from it will expire. This requires that applications are
180 prepared to use new IPv6 addresses when old ones will expire.
/Zephyr-Core-3.7.0/subsys/bluetooth/controller/ll_sw/
Dull_llcp.c472 static int prt_elapse(uint16_t *expire, uint16_t elapsed_event) in prt_elapse() argument
474 if (*expire != 0U) { in prt_elapse()
475 if (*expire > elapsed_event) { in prt_elapse()
476 *expire -= elapsed_event; in prt_elapse()
/Zephyr-Core-3.7.0/subsys/pm/
DKconfig20 timer is due to expire.
/Zephyr-Core-3.7.0/doc/kernel/services/timing/
Dclocks.rst123 :c:macro:`K_CYC()` specify timeout values that will expire after specified
134 indicates a timeout that will expire after the system uptime reaches
330 an uptime tick at which it will expire. So such a loop might look like:
Dtimers.rst33 with a duration of 200 and a period of 75, it will first expire
/Zephyr-Core-3.7.0/subsys/bluetooth/controller/
DKconfig.ll_sw_split1063 'must expire' features.
1074 first expire timeout.
1089 ticker nodes, returning tick to expire.
1098 ticker nodes, returning tick to expire and remainder from a reference
1107 ticker nodes, returning tick to expire and lazy count from a reference
1139 bool "Ticker timeout with other ticker's expire information"
/Zephyr-Core-3.7.0/include/zephyr/net/
Dnet_if.h393 uint64_t expire; member
/Zephyr-Core-3.7.0/doc/security/
Dsensor-threat.rst66 provider. Because the root certificates can expire, and possibly be
/Zephyr-Core-3.7.0/doc/connectivity/networking/api/
Dlwm2m.rst717 is the earliest when any of these values expire. This allows setting long lifetime for the
/Zephyr-Core-3.7.0/subsys/bluetooth/shell/
Dbt.c4749 SHELL_CMD_ARG(adv-rpa-expire, NULL, HELP_ONOFF, cmd_adv_rpa_expire, 2, 0),
/Zephyr-Core-3.7.0/doc/releases/
Drelease-notes-2.2.rst752 * :github:`23015` - Ongoing LL control procedures fails with must-expire latency (BT_CTLR_CONN_META)