/openbmc/libmctp/ |
H A D | core-internal.h | 35 /* Tag expiry timeout, in milliseconds */ 87 /* time of tag expiry */ 88 uint64_t expiry; member
|
H A D | core.c | 971 r->expiry = 0; in mctp_dealloc_tag() 988 if (r->local == 0 || r->expiry < now) { in mctp_alloc_tag() 1008 spare->expiry = now + MCTP_TAG_TIMEOUT; in mctp_alloc_tag()
|
/openbmc/qemu/hw/timer/ |
H A D | sse-timer.c | 139 uint64_t expiry = sse_counter_tick_to_time(s->counter, nexttick); in sse_set_timer() local 141 if (expiry <= INT64_MAX) { in sse_set_timer() 142 timer_mod_ns(&s->timer, expiry); in sse_set_timer() 147 * expiry times are absolute, not relative, we are never going in sse_set_timer() 152 * which is signalled by expiry == UINT64_MAX. in sse_set_timer() 178 * that it is not representable as a timer_mod() expiry, so in in sse_recalc_timer()
|
/openbmc/u-boot/arch/xtensa/lib/ |
H A D | time.c | 27 unsigned expiry = get_ccount() + cycles; in delay_cycles() local 28 while ((signed)(expiry - get_ccount()) > 0) in delay_cycles()
|
/openbmc/openpower-vpd-parser/vpd-manager/include/ |
H A D | gpio_monitor.hpp | 71 * @brief API to handle timer expiry. 73 * This API handles timer expiry and checks on the GPIO presence state,
|
/openbmc/pldm/requester/ |
H A D | handler.hpp | 160 "Instance ID expiry for EID '{EID}' using InstanceID '{INSTANCEID}'", in instanceIdExpiryCallBack() 169 "Failed to stop the instance ID expiry timer, response code '{RC}'", in instanceIdExpiryCallBack() 187 // before the instance ID expiry, then the response handler in instanceIdExpiryCallBack() 237 "Failed to start the instance ID expiry timer, error - {ERROR}", in pollEndpointQueue() 325 "Failed to stop the instance ID expiry timer, response code '{RC}'", in unregisterRequest() 390 "Failed to stop the instance ID expiry timer, response code '{RC}'", in handleResponse()
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema/ |
H A D | Settings.v1_4_0.json | 47 "description": "The expiry time of maintenance window in seconds.", 90 "description": "The expiry time of maintenance window in seconds.", 156 "description": "The expiry time of maintenance window in seconds.",
|
H A D | CertificateEnrollment.v1_0_0.json | 418 …"description": "The number of days before certificate expiry to begin automatic renewal of the cer… 419 …ion": "This property shall contain the number of days before certificate expiry to begin automatic…
|
/openbmc/bmcweb/redfish-core/schema/dmtf/json-schema-installed/ |
H A D | Settings.v1_4_0.json | 47 "description": "The expiry time of maintenance window in seconds.", 90 "description": "The expiry time of maintenance window in seconds.", 156 "description": "The expiry time of maintenance window in seconds.",
|
/openbmc/qemu/include/hw/ |
H A D | ptimer.h | 102 * @callback: function to call on ptimer expiry 125 * the ptimer state such that another ptimer expiry is triggered, then 157 * ptimer state now means that we should trigger the timer expiry
|
H A D | clock.h | 255 * expiry deadlines, rather than attempting to obtain a "period 264 * an expiry later than that is in the "will never happen" category
|
/openbmc/openbmc/meta-openembedded/meta-webserver/recipes-webadmin/webmin/files/ |
H A D | disable-version-check.patch | 48 # Password close to expiry
|
/openbmc/qemu/target/ppc/ |
H A D | trace-events | 28 kvm_handle_watchdog_expiry(void) "handle watchdog expiry"
|
/openbmc/qemu/include/qemu/ |
H A D | timer.h | 189 * Returns: time until expiry in nanoseconds or -1 645 * @expire_time: the expiry time in nanoseconds 657 * @expire_time: the expiry time in nanoseconds 672 * Modify a timer to expiry at @expire_time, taking into 719 * Determine the expiry time of a timer 721 * Returns: the expiry time in nanoseconds
|
/openbmc/qemu/docs/devel/ |
H A D | clocks.rst | 332 be more convenient; see the section below on expiry deadlines.) 367 Calculating expiry deadlines 372 to set a timer expiry deadline. Use the function ``clock_ticks_to_ns()``, 376 It is important not to try to calculate expiry deadlines using a 387 300 years, anything with an expiry later than that is in the "will
|
H A D | tcg-icount.rst | 55 expiry we cannot do the same for MMIO. Every load/store we execute
|
/openbmc/qemu/hw/watchdog/ |
H A D | wdt_diag288.c | 52 * expiry. watchdog_perform_action() may temporarily relinquish in diag288_timer_expired()
|
H A D | wdt_i6300esb.c | 72 int reboot_enabled; /* "Reboot" on timer expiry. The real action 85 int free_run; /* If true, reload timer on expiry. */ 172 * the hardware has two timers, and so expiry happens in two stages.
|
H A D | sbsa_gwdt.c | 206 * expiry. watchdog_perform_action() may temporarily relinquish in sbsa_gwdt_timer_sysinterrupt()
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Certs/ |
H A D | Certificate.interface.yaml | 89 The certificate expiry date and time, in epoch time, in milliseconds
|
/openbmc/qemu/include/block/ |
H A D | aio.h | 527 * @cb: the callback to call on timer expiry 551 * @cb: the callback to call on timer expiry 574 * @cb: the callback to call on timer expiry 594 * @cb: the callback to call on timer expiry
|
/openbmc/qemu/tests/unit/ |
H A D | test-aio.c | 708 int64_t expiry; in test_source_timer_schedule() local 719 expiry = qemu_clock_get_ns(data.clock_type) + in test_source_timer_schedule() 721 timer_mod(&data.timer, expiry); in test_source_timer_schedule() 730 expiry += data.ns; in test_source_timer_schedule() 737 g_assert(qemu_clock_get_ns(data.clock_type) > expiry); in test_source_timer_schedule()
|
/openbmc/docs/designs/ |
H A D | bmc-service-failure-debug-and-recovery.md | 338 5. If `IBF` clears before expiry, restart the escalation timer 341 before expiry, restart the escalation timer 343 7. If `Ready` becomes set before expiry, disarm the escalation timer. Recovery
|
/openbmc/phosphor-pid-control/pid/ |
H A D | pidloop.cpp | 73 nextTime = timer->expiry(); in pidControlLoop()
|
/openbmc/qemu/hw/rtc/ |
H A D | goldfish_rtc.c | 81 * We should be setting timer expiry to: in goldfish_rtc_set_alarm()
|