Searched full:duration (Results 1 – 25 of 124) sorted by relevance
12345
| /Documentation/leds/ |
| D | ledtrig-transient.rst | 68 This trigger exports three properties, activate, state, and duration. When
71 - duration allows setting timer value in msecs. The initial value is 0.
73 duration as needed. The initial and default value is 0. This will allow
74 duration to be set after trigger activation.
76 duration.
82 to allow duration to be set.
85 duration running.
89 duration
90 - one shot timer value. When activate is set, duration value
93 echo new_value > duration
[all …]
|
| D | leds-sc27xx.rst | 20 - Min stage duration: 125 ms
21 - Max stage duration: 31875 ms
23 Since the stage duration step is 125 ms, the duration should be
|
| /Documentation/devicetree/bindings/memory-controllers/ |
| D | st,stm32-fmc2-ebi-props.yaml | 89 description: This property defines the duration of the address setup
93 description: This property defines the duration of the address hold
98 description: This property defines the duration of the data setup phase
106 description: This property defines the duration of the data hold phase
118 description: This property defines the duration of the address setup
122 description: This property defines the duration of the address hold
127 description: This property defines the duration of the data setup
135 description: This property defines the duration of the data hold phase
140 duration in nanoseconds for synchronous transactions. When this timing
|
| /Documentation/driver-api/thermal/ |
| D | cpu-idle-cooling.rst | 36 duration in a controlled period, the SoC temperature will
37 decrease. Acting on the idle state duration or the idle cycle
48 belong to the same cluster, with a duration greater than the cluster
69 We use a fixed duration of idle injection that gives an acceptable
94 starting state is selected. With a fixed idle duration and the duty
95 cycle (aka the cooling device state), the running duration can be
130 The idle injection duration value must comply with the constraints:
173 injection duration, we can compute the running duration with::
192 * The injected idle duration must be greater than the idle state
|
| /Documentation/trace/ |
| D | osnoise-tracer.rst | 142 - osnoise:nmi_noise: noise from NMI, including the duration.
143 - osnoise:irq_noise: noise from an IRQ, including the duration.
145 duration.
146 - osnoise:thread_noise: noise from a thread, including the duration.
150 thread_noise duration at the start. Then, an IRQ takes place, preempting
152 it will compute its duration, and this duration will be subtracted from
158 …8-961 [008] d.h. 5789.857532: irq_noise: local_timer:236 start 5789.857529929 duration 1845 ns
159 …8-961 [008] dNh. 5789.858408: irq_noise: local_timer:236 start 5789.858404871 duration 2848 ns
160 …54 [008] d... 5789.858413: thread_noise: migration/8:54 start 5789.858409300 duration 3068 ns
161 …osnoise/8-961 [008] .... 5789.858413: sample_threshold: start 5789.858404555 duration 8812 ns…
[all …]
|
| D | timerlat-tracer.rst | 93 …87882 [005] dNLh1.. 548.771082: irq_noise: local_timer:236 start 548.771077442 duration 7597 ns
94 … cc1-87882 [005] dNLh2.. 548.771099: irq_noise: qxl:21 start 548.771085017 duration 7139 ns
95 …882 [005] d...3.. 548.771102: thread_noise: cc1:87882 start 548.771078243 duration 9909 ns
107 It is worth mentioning that the *duration* values reported
109 thread_noise does not include the duration of the overhead caused
148 …1026 [007] dN.h1.. 200.201948: irq_noise: local_timer:236 start 200.201939376 duration 7872 ns
150 …026 [007] dN.h2.. 200.202598: irq_noise: local_timer:236 start 200.202586162 duration 11855 ns
151 …1026 [007] dN.h3.. 200.202947: irq_noise: local_timer:236 start 200.202939174 duration 7318 ns
152 …6 [007] d...3.. 200.203444: thread_noise: insmod:1026 start 200.202586933 duration 838681 ns
|
| /Documentation/devicetree/bindings/watchdog/ |
| D | zii,rave-wdt.yaml | 22 reset-duration-ms:
24 Duration of the pulse generated when the watchdog times
46 reset-duration-ms = <30>;
|
| D | realtek,otto-wdt.yaml | 13 The timer has two timeout phases. Both phases have a maximum duration of 32
15 minimum duration of each phase is one tick. Each phase can trigger an
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-trigger-pattern.txt | 3 The pattern is given by a series of tuples, of brightness and duration (ms).
5 specified duration. Duration of 0 means brightness should immediately change to
9 the tuple with duration less than dimming interval (50ms) is treated as a step
|
| /Documentation/devicetree/bindings/net/dsa/ |
| D | lan9303.txt | 14 - reset-duration: reset duration in milliseconds, defaults to 200 ms
41 reset-duration = <200>;
77 reset-duration = <100>;
|
| /Documentation/ABI/testing/ |
| D | sysfs-bus-papr-pmem | 55 * "HostSDur" : Host Store Duration
56 * "HostLDur" : Host Load Duration
59 * "MedRDur " : Media Read Duration
60 * "MedWDur " : Media Write Duration
|
| D | sysfs-class-led-trigger-pattern | 6 the brightness for the specified duration with one software
10 duration (ms).
19 the brightness for the specified duration with one software
|
| D | sysfs-block-device | 105 (RO) Indicates if the device supports the command duration
114 (RW) For a device supporting the command duration limits
117 Writing "1" to this file enables the use of command duration
|
| D | debugfs-cros-ec | 74 the duration after a sleep command was received but before the
75 hardware line changed, as well as the duration between when the
|
| /Documentation/tools/rtla/ |
| D | common_options.rst | 9 **-d**, **--duration** *time[s|m|h|d]*
11 Set the duration of the session.
30 …nd> <mode> -t -e osnoise:irq_noise --trigger="hist:key=desc,duration/1000:sort=desc,duration/1000:…
|
| /Documentation/devicetree/bindings/thermal/ |
| D | thermal-idle.yaml | 34 duration-us:
36 The idle duration in microsecond the device should cool down.
77 duration-us = <10000>;
93 duration-us = <10000>;
|
| /Documentation/devicetree/bindings/phy/ |
| D | qcom,usb-snps-femto-v2.yaml | 90 qcom,pre-emphasis-duration-bp:
92 This signal controls the duration for which the
94 The HS Transmitter pre-emphasis duration is defined in terms of
95 unit amounts. One unit of pre-emphasis duration is approximately
96 650 ps and is defined as 1X pre-emphasis duration.
|
| /Documentation/devicetree/bindings/input/ |
| D | ti,palmas-pwrbutton.txt | 16 - ti,palmas-long-press-seconds: Duration in seconds which the power
20 - ti,palmas-pwron-debounce-milli-seconds: Duration in milliseconds
|
| D | input.yaml | 51 Duration in seconds which the key should be kept pressed for device to
57 Duration in seconds which the key should be kept pressed for device to
|
| /Documentation/devicetree/bindings/iio/accel/ |
| D | lis302.txt | 43 - st,wu-duration-1: duration register for Free-Fall/Wake-Up
45 - st,wu-duration-2: duration register for Free-Fall/Wake-Up
|
| /Documentation/devicetree/bindings/power/ |
| D | domain-idle-state.yaml | 34 state. Note that, the exit-latency-us duration may be guaranteed only
44 The minimum residency duration in microseconds after which the idle
|
| /Documentation/devicetree/bindings/gpio/ |
| D | gpio-latch.yaml | 58 setup-duration-ns:
62 clock-duration-ns:
86 setup-duration-ns = <100>;
87 clock-duration-ns = <100>;
|
| /Documentation/accounting/ |
| D | taskstats-struct.rst | 153 /* Accumulated RSS usage in duration of a task, in MBytes-usecs.
161 /* Accumulated virtual memory usage in duration of a task.
166 /* High watermark of RSS usage in duration of a task, in KBytes. */
169 /* High watermark of VM usage in duration of a task, in KBytes. */
|
| /Documentation/RCU/ |
| D | torture.rst | 228 The --duration parameter can override the default run time of 30 minutes.
229 For example, ``--duration 2d`` would run for two days, ``--duration 3h``
230 would run for three hours, ``--duration 5m`` would run for five minutes,
231 and ``--duration 45s`` would run for 45 seconds. This last can be useful
326 most notably --duration and --bootargs. For example::
329 --duration 45s
355 --cpus 64 --duration 8h --configs "5*CFLIST"
371 --duration 24h
|
| /Documentation/admin-guide/pm/ |
| D | cpuidle.rst | 156 duration* from now on) and it can use that information somehow along with the
157 time until the closest timer to estimate the idle duration in future. How the
208 the tick period length. Moreover, in that case the idle duration of any CPU
270 idle duration and uses the predicted value for idle state selection.
287 up and the closer the sleep length is to the observed idle duration, the closer
290 falls into to obtain the first approximation of the predicted idle duration.
293 idle duration prediction. Namely, it saves the last 8 observed idle duration
294 values and, when predicting the idle duration next time, it computes the average
298 interval" value. Otherwise, the longest of the saved observed idle duration
306 taken as the predicted idle duration.
[all …]
|
12345