| /kernel/linux/linux-5.10/fs/ntfs/ |
| D | time.h | 26 * and a long tv_nsec where tv_sec is the number of 1-second intervals since
28 * intervals since the value of tv_sec.
31 * measured as the number of 100-nano-second intervals since 1st January 1601,
37 * Convert the seconds to 100ns intervals, add the nano-seconds in utc2ntfs()
38 * converted to 100ns intervals, and then add the NTFS time offset. in utc2ntfs()
66 * and a long tv_nsec where tv_sec is the number of 1-second intervals since
68 * intervals since the value of tv_sec.
71 * measured as the number of 100 nano-second intervals since 1st January 1601,
81 * Convert the time to 1-second intervals and the remainder to in ntfs2utc()
82 * 1-nano-second intervals. in ntfs2utc()
|
| /kernel/linux/linux-4.19/fs/ntfs/ |
| D | time.h | 40 * and a long tv_nsec where tv_sec is the number of 1-second intervals since
42 * intervals since the value of tv_sec.
45 * measured as the number of 100-nano-second intervals since 1st January 1601,
51 * Convert the seconds to 100ns intervals, add the nano-seconds in utc2ntfs()
52 * converted to 100ns intervals, and then add the NTFS time offset. in utc2ntfs()
80 * and a long tv_nsec where tv_sec is the number of 1-second intervals since
82 * intervals since the value of tv_sec.
85 * measured as the number of 100 nano-second intervals since 1st January 1601,
95 * Convert the time to 1-second intervals and the remainder to in ntfs2utc()
96 * 1-nano-second intervals. in ntfs2utc()
|
| /kernel/linux/linux-4.19/Documentation/media/uapi/v4l/ |
| D | vidioc-enum-frameintervals.rst | 12 VIDIOC_ENUM_FRAMEINTERVALS - Enumerate frame intervals
36 This ioctl allows applications to enumerate all frame intervals that the
44 depend on the type of frame intervals the device supports. Here are the
71 intervals.
75 The order in which the frame intervals are returned has no
77 default frame intervals.
86 **Frame intervals and frame rates:** The V4L2 API uses frame
87 intervals instead of frame rates. Given the frame interval the frame
139 - IN: Pixel format for which the frame intervals are enumerated.
143 - IN: Frame width for which the frame intervals are enumerated.
[all …]
|
| D | vidioc-subdev-enum-frame-interval.rst | 12 VIDIOC_SUBDEV_ENUM_FRAME_INTERVAL - Enumerate frame intervals
35 This ioctl lets applications enumerate available frame intervals on a
36 given sub-device pad. Frame intervals only makes sense for sub-devices
40 For the common use case of image sensors, the frame intervals available
43 when enumerating frame intervals.
45 To enumerate frame intervals applications initialize the ``index``,
51 intervals are enumerable by beginning at index zero and incrementing by
54 Available frame intervals may depend on the current 'try' formats at
93 - Frame intervals to be enumerated, from enum
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/v4l/ |
| D | vidioc-subdev-enum-frame-interval.rst | 13 VIDIOC_SUBDEV_ENUM_FRAME_INTERVAL - Enumerate frame intervals
34 This ioctl lets applications enumerate available frame intervals on a
35 given sub-device pad. Frame intervals only makes sense for sub-devices
39 For the common use case of image sensors, the frame intervals available
42 when enumerating frame intervals.
44 To enumerate frame intervals applications initialize the ``index``,
50 intervals are enumerable by beginning at index zero and incrementing by
53 Available frame intervals may depend on the current 'try' formats at
92 - Frame intervals to be enumerated, from enum
|
| D | vidioc-enum-frameintervals.rst | 13 VIDIOC_ENUM_FRAMEINTERVALS - Enumerate frame intervals
35 This ioctl allows applications to enumerate all frame intervals that the
43 depend on the type of frame intervals the device supports. Here are the
70 intervals.
74 The order in which the frame intervals are returned has no
76 default frame intervals.
85 **Frame intervals and frame rates:** The V4L2 API uses frame
86 intervals instead of frame rates. Given the frame interval the frame
133 - IN: Pixel format for which the frame intervals are enumerated.
136 - IN: Frame width for which the frame intervals are enumerated.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/userspace-api/media/drivers/ |
| D | imx-uapi.rst | 42 intervals (elapsed time between two EOF's) drop below the nominal
47 line mechanism should show an increase in the intervals by 1 line
72 If the averaged intervals fall outside nominal by this amount, in
77 If any intervals are higher than this value, those samples are
85 FIM begins to average intervals.
90 for measuring frame intervals. This is superior to the default method
91 of measuring frame intervals via EOF interrupt, since it is not subject
106 When input capture is disabled, frame intervals will be measured via
|
| /kernel/linux/linux-5.10/drivers/cpuidle/governors/ |
| D | menu.c | 24 #define INTERVALS (1UL << INTERVAL_SHIFT) macro
75 * intervals and if the stand deviation of these 8 intervals is below a
76 * threshold value, we use the average of these intervals as prediction.
116 unsigned int intervals[INTERVALS]; member
165 * intervals, and checking if the standard deviation of that set
180 /* First calculate the average of past intervals */ in get_typical_interval()
185 for (i = 0; i < INTERVALS; i++) { in get_typical_interval()
186 unsigned int value = data->intervals[i]; in get_typical_interval()
205 if (divisor == INTERVALS) in get_typical_interval()
212 for (i = 0; i < INTERVALS; i++) { in get_typical_interval()
[all …]
|
| D | teo.c | 18 * they can be covered by taking a few most recent idle time intervals of the
65 #define INTERVALS 8 macro
100 * @intervals: Saved idle duration values.
107 u64 intervals[INTERVALS]; member
200 cpu_data->intervals[cpu_data->interval_idx++] = measured_ns; in teo_update()
201 if (cpu_data->interval_idx >= INTERVALS) in teo_update()
387 for (i = 0; i < INTERVALS; i++) { in teo_select()
388 u64 val = cpu_data->intervals[i]; in teo_select()
401 if (count > INTERVALS / 2) { in teo_select()
475 for (i = 0; i < INTERVALS; i++) in teo_enable_device()
[all …]
|
| /kernel/linux/linux-4.19/drivers/cpuidle/governors/ |
| D | menu.c | 35 #define INTERVALS (1UL << INTERVAL_SHIFT) macro
87 * intervals and if the stand deviation of these 8 intervals is below a
88 * threshold value, we use the average of these intervals as prediction.
130 unsigned int intervals[INTERVALS]; member
196 * intervals, and checking if the standard deviation of that set
210 /* First calculate the average of past intervals */ in get_typical_interval()
214 for (i = 0; i < INTERVALS; i++) { in get_typical_interval()
215 unsigned int value = data->intervals[i]; in get_typical_interval()
223 if (divisor == INTERVALS) in get_typical_interval()
230 for (i = 0; i < INTERVALS; i++) { in get_typical_interval()
[all …]
|
| /kernel/linux/linux-5.10/drivers/hid/ |
| D | hid-holtekff.c | 44 * 2: periodic rumble, short intervals
46 * 4: periodic rumble, long intervals
47 * 5: weak periodic rumble, long intervals
48 * 6: weak periodic rumble, short intervals
49 * 7: periodic rumble, short intervals
50 * 8: strong periodic rumble, short intervals
53 * b: very strong periodic rumble, very short intervals
|
| /kernel/linux/linux-4.19/drivers/hid/ |
| D | hid-holtekff.c | 56 * 2: periodic rumble, short intervals
58 * 4: periodic rumble, long intervals
59 * 5: weak periodic rumble, long intervals
60 * 6: weak periodic rumble, short intervals
61 * 7: periodic rumble, short intervals
62 * 8: strong periodic rumble, short intervals
65 * b: very strong periodic rumble, very short intervals
|
| /kernel/linux/linux-5.10/kernel/irq/ |
| D | timings.c | 47 * interrupt and we end up with a suite of intervals. The experience
79 * The suffix array will build a suite of intervals of different
331 * The buffer contains the suite of intervals, in a ilog2 in irq_timings_next_event_index()
393 * number of intervals greater or equal to three times the in __irq_timings_next_event()
638 u64 *intervals; member
643 * Intervals are given in nanosecond base
730 index = irq_timings_interval_index(ti->intervals[i]); in irq_timings_test_next_index()
746 i = irq_timings_interval_index(ti->intervals[ti->count - 1]); in irq_timings_test_next_index()
763 pr_info("---> Injecting intervals number #%d (count=%zd)\n", in irq_timings_next_index_selftest()
796 index = irq_timings_interval_index(ti->intervals[i]); in irq_timings_test_irqs()
[all …]
|
| /kernel/linux/linux-4.19/tools/perf/pmu-events/arch/x86/ivytown/ |
| D | other.json | 13 … "PublicDescription": "Number of intervals between processor halts while thread is in ring 0.",
20 "BriefDescription": "Number of intervals between processor halts while thread is in ring 0",
|
| /kernel/linux/linux-4.19/tools/perf/pmu-events/arch/x86/ivybridge/ |
| D | other.json | 13 … "PublicDescription": "Number of intervals between processor halts while thread is in ring 0.",
20 "BriefDescription": "Number of intervals between processor halts while thread is in ring 0",
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/ivytown/ |
| D | other.json | 13 … "PublicDescription": "Number of intervals between processor halts while thread is in ring 0.",
20 "BriefDescription": "Number of intervals between processor halts while thread is in ring 0",
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/ivybridge/ |
| D | other.json | 13 … "PublicDescription": "Number of intervals between processor halts while thread is in ring 0.",
20 "BriefDescription": "Number of intervals between processor halts while thread is in ring 0",
|
| /kernel/linux/linux-4.19/Documentation/hwmon/ |
| D | lm93 | 82 The monitoring intervals for the two #PROCHOT signals is also configurable.
83 These intervals can be found in the sysfs files prochot1_interval and
84 prochot2_interval. The values in these files specify the intervals for
87 intervals are (in seconds):
89 #PROCHOT intervals: 0.73, 1.46, 2.9, 5.8, 11.7, 23.3, 46.6, 93.2, 186, 372
240 Ramp Times: 0 (disabled, h/w default) to 0.75 in 0.05 second intervals
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | t10-pi.h | 59 unsigned int intervals);
62 unsigned int intervals) in t10_pi_complete() argument
|
| /kernel/linux/linux-4.19/block/ |
| D | t10-pi.c | 248 * @intervals: total elements to prepare
260 unsigned int intervals) in t10_pi_complete() argument
281 for (j = 0; j < iv.bv_len && intervals; j += tuple_sz) { in t10_pi_complete()
288 intervals--; in t10_pi_complete()
|
| /kernel/linux/linux-4.19/Documentation/ABI/stable/ |
| D | sysfs-fs-orangefs | 23 Length of perf counter intervals in
40 other N-1 intervals remain available.
|
| /kernel/linux/linux-5.10/Documentation/ABI/stable/ |
| D | sysfs-fs-orangefs | 23 Length of perf counter intervals in
40 other N-1 intervals remain available.
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | lm93.rst | 92 The monitoring intervals for the two #PROCHOT signals is also configurable.
93 These intervals can be found in the sysfs files prochot1_interval and
94 prochot2_interval. The values in these files specify the intervals for
97 intervals are (in seconds):
99 #PROCHOT intervals:
262 0 (disabled, h/w default) to 0.75 in 0.05 second intervals
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/watchdog/ |
| D | snps,dw-wdt.yaml | 45 DW APB Watchdog custom timer intervals - Timeout Period ranges (TOPs).
49 the timer expiration intervals supported by the DW APB Watchdog. Note
|
| /kernel/linux/linux-4.19/Documentation/media/v4l-drivers/ |
| D | imx.rst | 226 rate decimation is specified by setting the frame intervals at
252 intervals (elapsed time between two EOF's) drop below the nominal
257 line mechanism should show an increase in the intervals by 1 line
282 If the averaged intervals fall outside nominal by this amount, in
287 If any intervals are higher than this value, those samples are
295 FIM begins to average intervals.
301 for measuring frame intervals. This is superior to the default method
302 of measuring frame intervals via EOF interrupt, since it is not subject
317 When input capture is disabled, frame intervals will be measured via
|