| /OK3568_Linux_fs/kernel/drivers/rtc/ |
| H A D | rtc-efi.c | 61 eft->nanosecond = 0; in convert_to_efi_time()
206 eft.hour, eft.minute, eft.second, eft.nanosecond, in efi_procfs()
222 alm.hour, alm.minute, alm.second, alm.nanosecond, in efi_procfs()
|
| /OK3568_Linux_fs/kernel/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 type: ktime_t. The kernel-internal
|
| H A D | highres.rst | 54 convert the clock ticks to nanosecond based time values. All other time keeping
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/ |
| H A D | property-units.txt | 19 -ns : nanosecond
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/bindings/sound/ |
| H A D | atmel-classd.txt | 32 Set non-overlapping time, the unit is nanosecond(ns).
|
| /OK3568_Linux_fs/u-boot/include/ |
| H A D | efi.h | 215 u32 nanosecond; member
|
| /OK3568_Linux_fs/kernel/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
|
| /OK3568_Linux_fs/kernel/Documentation/core-api/ |
| H A D | timekeeping.rst | 59 nanosecond, timespec64, and second output
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/device-mapper/ |
| H A D | statistics.rst | 68 use precise timer with nanosecond resolution
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/include/c++/10.3.1/ |
| H A D | chrono | 1014 // Why nanosecond resolution as the default?
1096 * std::system_clock until higher-than-nanosecond definitions
1287 // A signed 64-bit duration with nanosecond resolution gives roughly
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/include/c++/10.3.1/ |
| H A D | chrono | 1014 // Why nanosecond resolution as the default?
1096 * std::system_clock until higher-than-nanosecond definitions
1287 // A signed 64-bit duration with nanosecond resolution gives roughly
|
| /OK3568_Linux_fs/kernel/include/linux/ |
| H A D | efi.h | 191 u32 nanosecond; member
|
| /OK3568_Linux_fs/kernel/Documentation/scheduler/ |
| H A D | sched-design-CFS.rst | 92 CFS uses nanosecond granularity accounting and does not rely on any jiffies or
|
| /OK3568_Linux_fs/kernel/Documentation/sound/designs/ |
| H A D | timestamping.rst | 115 The accuracy is reported in nanosecond units (using an unsigned 32-bit
|
| /OK3568_Linux_fs/kernel/arch/ia64/kernel/ |
| H A D | efi.c | 263 ts->tv_nsec = tm.nanosecond; in STUB_GET_TIME()
|
| /OK3568_Linux_fs/kernel/Documentation/filesystems/ext4/ |
| H A D | inodes.rst | 512 bit wide; the upper 30 bits are used to provide nanosecond timestamp
|
| /OK3568_Linux_fs/kernel/Documentation/networking/ |
| H A D | phy.rst | 97 * PHY devices may offer sub-nanosecond granularity in how they allow a
|
| /OK3568_Linux_fs/kernel/Documentation/virt/kvm/ |
| H A D | timekeeping.rst | 596 back into nanosecond resolution values.
|
| /OK3568_Linux_fs/kernel/Documentation/userspace-api/media/v4l/ |
| H A D | hist-v4l2.rst | 183 64-bit signed integers (not struct timeval's) and given in nanosecond
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/aarch64-none-linux-gnu/libc/usr/share/info/ |
| H A D | libc.info-9 | 6185 nanosecond precision, from a variety of different clocks. Clocks can be
6241 nanosecond, and may not be the same for all clocks. POSIX also provides
|
| H A D | libc.info-10 | 3902 The nanosecond value in the REQUESTED_TIME parameter contains
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/arm-none-linux-gnueabihf/libc/usr/share/info/ |
| H A D | libc.info-9 | 6185 nanosecond precision, from a variety of different clocks. Clocks can be
6241 nanosecond, and may not be the same for all clocks. POSIX also provides
|
| H A D | libc.info-10 | 3902 The nanosecond value in the REQUESTED_TIME parameter contains
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/share/info/ |
| H A D | gfortran.info | 18787 implementation, provide up to nanosecond resolution. If a
|