Searched refs:nanoseconds (Results 1 – 25 of 91) sorted by relevance
1234
| /linux-6.12.1/Documentation/block/ |
| D | kyber-iosched.rst | 11 Target latency for reads (in nanoseconds).
15 Target latency for synchronous writes (in nanoseconds).
|
| /linux-6.12.1/Documentation/ABI/testing/ |
| D | sysfs-firmware-acpi | 12 of firmware image execution. In nanoseconds.
15 In nanoseconds.
18 image. In nanoseconds.
22 firmware. In nanoseconds.
26 UEFI compatible firmware. In nanoseconds.
30 nanoseconds.
33 hardware entry to S3. In nanoseconds.
39 including the most recent resume. In nanoseconds.
42 handoff to the OS waking vector. In nanoseconds.
|
| D | sysfs-ptp | 122 and nanoseconds.
131 seconds, start time nanoseconds, period seconds, and
132 period nanoseconds. To disable a periodic output, set
133 all the seconds and nanoseconds values to zero.
|
| D | sysfs-class-scsi_tape | 21 closed. This item is measured in nanoseconds.
64 Shows the total amount of time in nanoseconds waiting for
95 Shows the total amount of time in nanoseconds waiting for
|
| D | sysfs-class-pwm | 55 Sets the PWM signal period in nanoseconds.
62 Sets the PWM signal duty cycle in nanoseconds.
|
| D | sysfs-timecard | 123 Description: (RO) Specifies the signal period in nanoseconds.
128 Description: (RO) Specifies the signal phase offset in nanoseconds.
163 Period and phase are specified in nanoseconds. Duty cycle is
254 number of nanoseconds, so the computed midpoint matches the
|
| /linux-6.12.1/Documentation/devicetree/bindings/input/touchscreen/ |
| D | fsl-mx25-tcq.txt | 14 - fsl,pen-debounce-ns: Pen debounce time in nanoseconds.
20 - fsl,settling-time-ns: Settling time in nanoseconds. The settling time is before
|
| /linux-6.12.1/Documentation/driver-api/hte/ |
| D | tegra-hte.rst | 12 converts clock tick rate to nanoseconds before storing it as timestamp value.
32 returns the timestamp in nanoseconds.
|
| D | hte.rst | 43 consumers and the providers. It expresses timestamp data in nanoseconds in
49 - Converts timestamps in nanoseconds.
|
| /linux-6.12.1/Documentation/devicetree/bindings/cpufreq/ |
| D | cpufreq-spear.txt | 14 unit of nanoseconds.
|
| D | nvidia,tegra124-cpufreq.txt | 18 in unit of nanoseconds.
|
| D | cpufreq-dt.txt | 18 in unit of nanoseconds.
|
| /linux-6.12.1/Documentation/scheduler/ |
| D | sched-stats.rst | 64 7) sum of all time spent running by tasks on this processor (in nanoseconds)
66 nanoseconds)
163 1) time spent on the cpu (in nanoseconds)
164 2) time spent waiting on a runqueue (in nanoseconds)
|
| /linux-6.12.1/Documentation/devicetree/bindings/clock/ |
| D | nvidia,tegra124-dfll.txt | 56 - nvidia,pwm-period-nanoseconds: period of PWM square wave in nanoseconds.
128 nvidia,pwm-period-nanoseconds = <2500>; /* 2.5us */
|
| /linux-6.12.1/Documentation/accounting/ |
| D | taskstats-struct.rst | 106 * xxx_delay_total is the corresponding cumulative delay in nanoseconds
133 * Value is cumulative, in nanoseconds, without a corresponding count
141 * Value is cumulative, in nanoseconds, without a corresponding count
|
| /linux-6.12.1/Documentation/virt/kvm/devices/ |
| D | vcpu.rst | 228 kvmclock nanoseconds (guest_src), and host CLOCK_REALTIME nanoseconds
239 4. Invoke the KVM_SET_CLOCK ioctl, providing the source nanoseconds from
252 kvmclock nanoseconds (guest_dest).
|
| /linux-6.12.1/Documentation/virt/kvm/x86/ |
| D | msr.rst | 48 number of nanoseconds for wallclock at time of boot.
100 nanoseconds.
104 tsc-related quantity to nanoseconds
108 quantity to nanoseconds. This shift will ensure that
113 The conversion from tsc to nanoseconds involves an additional
297 nanoseconds. Time during which the vcpu is idle, will not be
|
| /linux-6.12.1/tools/perf/Documentation/ |
| D | perf-timechart.txt | 67 as number of nanoseconds. If non-numeric string is given it's
77 Merge events that are merge-dist nanoseconds apart.
|
| /linux-6.12.1/Documentation/admin-guide/cgroup-v1/ |
| D | blkio-controller.rst | 166 for the IOs done by this cgroup. This is in nanoseconds to make it
187 device). This is in nanoseconds to make it meaningful for flash
215 waiting in the scheduler queue. This is in nanoseconds. If this is
225 nanoseconds. If this is read when the cgroup is in an empty state,
233 from other queues/cgroups. This is in nanoseconds. If this is read
|
| /linux-6.12.1/drivers/iio/light/ |
| D | si1133.c | 518 static int si1133_get_int_time_index(int milliseconds, int nanoseconds) in si1133_get_int_time_index() argument
524 nanoseconds == si1133_int_time_table[i][1]) in si1133_get_int_time_index()
531 int milliseconds, int nanoseconds) in si1133_set_integration_time() argument
535 index = si1133_get_int_time_index(milliseconds, nanoseconds); in si1133_set_integration_time()
|
| /linux-6.12.1/Documentation/devicetree/bindings/net/ |
| D | cpsw.txt | 39 - cpts_clock_mult : Numerator to convert input clock ticks into nanoseconds
40 - cpts_clock_shift : Denominator to convert input clock ticks into nanoseconds
|
| /linux-6.12.1/Documentation/devicetree/bindings/pwm/ |
| D | pwm-st.txt | 8 second cell is the period in nanoseconds - fixed to 2
|
| D | pwm.txt | 44 period in nanoseconds.
|
| /linux-6.12.1/Documentation/admin-guide/device-mapper/ |
| D | statistics.rst | 24 reported times are in nanoseconds.
70 used, the resulting times are in nanoseconds instead of
78 nanoseconds. For each range, the kernel will report the
|
| /linux-6.12.1/Documentation/trace/ |
| D | events-nmi.rst | 32 to the filter is in nanoseconds! You can filter on 'delta_ns'::
|
1234