Searched refs:CLOCK_TAI (Results 1 – 19 of 19) sorted by relevance
26 CLOCK_TAI,47 CLOCK_TO_STR(CLOCK_TAI); in get_clock_str()59 case CLOCK_TAI: in possibly_unsupported()
38 #ifndef CLOCK_TAI39 #define CLOCK_TAI 11 macro
54 #define CLOCK_TAI 11 macro
41 int result = clock_getres(CLOCK_TAI, &ts); in clock_getres_0200()
50 ret = clock_nanosleep(CLOCK_TAI, TIMER_ABSTIME, &ts, NULL); in clock_nanosleep_0200()
82 #define CLOCK_TAI 11 macro
139 case CLOCK_TAI: in tst_clock_name()
96 #define CLOCK_TAI 11 macro
97 #define CLOCK_TAI 11 macro
108 #define CLOCK_TAI 11 macro
818 #ifdef CLOCK_TAI in clock_type_to_posix_id()819 return CLOCK_TAI; in clock_type_to_posix_id()
248 txtime_cfg.clockid = CLOCK_TAI; in gst_avtp_sink_init_socket()
1978 #ifdef CLOCK_TAI1979 if (PyModule_AddIntMacro(module, CLOCK_TAI) < 0) {
738 Add :data:`time.CLOCK_TAI` constant if the operating system support it.
806 .. data:: CLOCK_TAI
6297 systemclock: No need to check for CLOCK_TAI in the meson6299 it's safe to assume that CLOCK_TAI will also be.6307 GST_CLOCK_TYPE_TAI is GStreamer abstraction for CLOCK_TAI. Main6311 in CLOCK_TAI coordinate.6312 With GST_CLOCK_TYPE_TAI, applications can use CLOCK_TAI directly on6314 leveraging system's CLOCK_TAI, applications also don't need to keep track6315 of leap seconds - less burden for them. Just keep system's CLOCK_TAI