Searched full:billion (Results 1 – 25 of 28) sorted by relevance
12
75 adjustment. The unit is parts per billion, i.e. The number of77 clock per billion ticks. A positive value makes a day pass more
34 parts per billion.
373 * new_incval = base_incval + (base_incval * adjustment) / 1billion376 * max_incval = base_incval + (base_incval * max_adj) / billion379 * max_adj = floor(((max_incval - base_incval) * 1billion) / 1billion)
32 description: accuracy of clock in ppb (parts per billion).
32 * [NOTE: PID/TIDs are limited to 2^30 ~= 1 billion, see FUTEX_TID_MASK.]
217 * is expressed in ppb (parts per billion). The parent accuracy is380 * @fixed_accuracy: constant accuracy of clock in ppb (parts per billion)
124 * clk_get_accuracy - obtain the clock accuracy in ppb (parts per billion)
38 /* Maximum parts-per-billion adjustment that is acceptable */
199 * @scaled_ppm: Desired frequency in scaled parts per billion
1098 * rtc_read_offset - Read the amount of rtc offset in parts per billion1100 * @offset: the offset in parts per billion1129 * @offset: the offset in parts per billion
97 #define OFFSET_STEP (2170) /* Offset step in parts per billion */
247 /* Adjust the HW clock by a rate given in parts-per-billion (ppb) units.
168 * If this path is more than 2 billion steps long, this directory tree in xchk_dirpath_append()229 * If there are more than 2 billion actual parent pointers for this in xchk_dirtree_create_path()
1764 /* Nanosecond counters can't have more than 1 billion. */
173 * billion ticks per second. in sender_guest_code()
1083 * more than 2 billion grace periods (and way more on a 64-bit system!),1110 * more than 2 billion grace periods (and way more on a 64-bit system!),
3584 * more than a billion grace periods (and way more on a 64-bit system!).3644 * for more than a billion grace periods (and way more on a 64-bit3685 * more than 2 billion grace periods (and way more on a 64-bit system!),3712 * more than 2 billion grace periods (and way more on a 64-bit system!),
146 /* Maximum parts-per-billion adjustment that is acceptable */262 * @adjfreq_ppb_shift: Shift required to convert scaled parts-per-billion716 * adjustments in parts-per-billion and the fixed-point in efx_ptp_get_attributes()
145 /* Maximum parts-per-billion adjustment that is acceptable */271 * @adjfreq_ppb_shift: Shift required to convert scaled parts-per-billion703 * adjustments in parts-per-billion and the fixed-point in efx_ptp_get_attributes()
18 #define BILLION 1000000000 macro
541 * exceeds ~2 billion, we kill the connection after its in rxrpc_expose_client_call()
125 * measured in parts per billion. Calculating this value is also simple.
142 * nodes as a sanity check. Theoretically there can be over 1 Billion
265 * is half the spread value expressed in parts per billion. in eqc_pll_parse_fracg()
3382 * c) 1 second per 1 billion nanoseconds3390 * second | 1 billion ns | cycle | 66 UIs3395 * (freq * incval * 6600 LINE_UI ) / ( 100 * 1 billion)