Searched refs:nanosecond (Results 1 – 17 of 17) sorted by relevance
| /openbmc/linux/drivers/rtc/ |
| H A D | rtc-efi.c | 61 eft->nanosecond = 0; in convert_to_efi_time()
207 eft.hour, eft.minute, eft.second, eft.nanosecond, in efi_procfs()
224 alm.hour, alm.minute, alm.second, alm.nanosecond, in efi_procfs()
|
| /openbmc/linux/Documentation/timers/ |
| H A D | timekeeping.rst | 55 into a nanosecond value as an unsigned long long (unsigned 64 bit) number.
58 possible to a nanosecond value using only the arithmetic operations
130 i.e. after 64 bits. Since this is a nanosecond value this will mean it wraps
147 counter to derive a 64-bit nanosecond value, so for example on the ARM
149 sched_clock() nanosecond base from a 16- or 32-bit counter. Sometimes the
|
| H A D | hrtimers.rst | 126 special nanosecond-resolution 64bit type: ktime_t.
|
| H A D | highres.rst | 54 convert the clock ticks to nanosecond based time values. All other time keeping
|
| /openbmc/u-boot/include/ |
| H A D | efi.h | 226 u32 nanosecond; member
|
| /openbmc/linux/Documentation/driver-api/ |
| H A D | ioctl.rst | 93 in other data structures when separate second/nanosecond values are
101 requires an expensive 64-bit division, a simple __u64 nanosecond value
|
| /openbmc/linux/Documentation/core-api/ |
| H A D | timekeeping.rst | 59 nanosecond, timespec64, and second output
|
| /openbmc/linux/Documentation/admin-guide/device-mapper/ |
| H A D | statistics.rst | 68 use precise timer with nanosecond resolution
|
| /openbmc/linux/Documentation/sound/designs/ |
| H A D | timestamping.rst | 115 The accuracy is reported in nanosecond units (using an unsigned 32-bit
|
| /openbmc/linux/Documentation/scheduler/ |
| H A D | sched-design-CFS.rst | 92 CFS uses nanosecond granularity accounting and does not rely on any jiffies or
|
| /openbmc/linux/include/linux/ |
| H A D | efi.h | 238 u32 nanosecond; member
|
| /openbmc/linux/arch/ia64/kernel/ |
| H A D | efi.c | 265 ts->tv_nsec = tm.nanosecond; in STUB_GET_TIME()
|
| /openbmc/qemu/docs/devel/ |
| H A D | replay.rst | 105 1 ns per *real time* nanosecond. This is done by setting up a timer
|
| /openbmc/linux/Documentation/filesystems/ext4/ |
| H A D | inodes.rst | 512 bit wide; the upper 30 bits are used to provide nanosecond timestamp
|
| /openbmc/linux/Documentation/networking/ |
| H A D | phy.rst | 97 * PHY devices may offer sub-nanosecond granularity in how they allow a
|
| /openbmc/linux/Documentation/virt/kvm/x86/ |
| H A D | timekeeping.rst | 596 back into nanosecond resolution values.
|
| /openbmc/linux/Documentation/userspace-api/media/v4l/ |
| H A D | hist-v4l2.rst | 183 64-bit signed integers (not struct timeval's) and given in nanosecond
|