Home
last modified time | relevance | path

Searched +full:50 +full:ms (Results 1 – 25 of 744) sorted by relevance

12345678910>>...30

/linux/tools/power/cpupower/bench/
H A DREADME-BENCH41 This part of the configuration file will create 25ms load/sleep turns,
48 Will increase load and sleep time by 25ms 5 times.
50 25ms load/sleep time repeated 20 times (cycles).
51 50ms load/sleep time repeated 20 times (cycles).
53 100ms load/sleep time repeated 20 times (cycles).
70 25 ms | 25 ms | 1
71 50 ms | 50 ms | 2
73 For example if ondemand governor is configured to have a 50ms
76 In round 1, ondemand should have rather static 50% load and probably
84 will always see 50% loads and you get worst performance impact never
[all …]
/linux/tools/testing/selftests/rseq/
H A Drun_param_test.sh115 echo "Yield injection (50%)"
124 echo "Kill injection (50%)"
130 echo "Sleep injection (1ms, 25%)"
133 echo "Sleep injection (1ms, 50%)"
136 echo "Sleep injection (1ms, 100%)"
148 echo "Yield injection (50%)"
157 echo "Kill injection (50%)"
163 echo "Sleep injection (1ms, 25%)"
166 echo "Sleep injection (1ms, 50%)"
169 echo "Sleep injection (1ms, 100%)"
/linux/Documentation/devicetree/bindings/sound/
H A Dcs35l33.txt31 20ms. If this property is set to 0,1,2,3 then ramp times would be 40ms,
32 60ms,100ms,175ms respectively for 48KHz sample rate.
62 stage enters LDO operation. Starts as a default value of 50mV for a value
63 of 1 and increases with a step size of 50mV to a maximum of 750mV (value of
72 from 0 to 7 for delays of 5ms, 10ms, 50ms, 100ms, 200ms, 500ms, 1000ms.
73 The default is 100ms.
91 1800mV with a step size of 50mV up to a maximum value of 1750mV.
H A Dcs35l36.txt15 increments of 50mV.
21 50mA.
61 (in ms) before the Class H algorithm switches to the weak-FET voltage
64 0 = 0ms
65 1 = 5ms
66 2 = 10ms
67 3 = 50ms
68 4 = 100ms (Default)
69 5 = 200ms
70 6 = 500ms
[all …]
H A Ddialog,da7219.yaml104 Mic bias higher voltage pulse duration (ms).
109 enum: [2, 5, 10, 50, 100, 200, 500]
111 Periodic button press measurements for 4-pole jack (ms).
121 enum: [5, 10, 20, 50, 100, 200, 500, 1000]
123 Debounce time for jack insertion (ms).
135 Jack type (3/4 pole) detection latency (ms).
141 Debounce time for jack removal (ms).
222 dlg,btn-cfg = <50>;
/linux/include/media/i2c/
H A Dlm3646.h61 * min 50ms, step 50ms, max 400ms
63 #define LM3646_FLASH_TOUT_MIN 50
64 #define LM3646_FLASH_TOUT_STEP 50
/linux/drivers/media/rc/
H A Dnuvoton-cir.h131 /* select sample period as 50us */
317 /* MCE CIR controller signal length: about 43ms
318 * 43ms / 50us (sample period) * 0.85 (inaccuracy)
322 /* MCE CIR keyboard signal length: about 26ms
323 * 26ms / 50us (sample period) * 0.85 (inaccuracy)
328 /* MCE CIR mouse signal length: about 24ms
329 * 24ms / 50us (sample period) * 0.85 (inaccuracy)
333 #define CIR_SAMPLE_PERIOD 50
343 #define SAMPLE_PERIOD 50
/linux/Documentation/devicetree/bindings/mfd/
H A Dst,stmpe.yaml156 1 = 50 us
159 4 = 1 ms
160 5 = 5 ms
161 6 = 10 ms
162 7 = 50 ms
172 3 = 1 ms
173 4 = 5 ms
174 5 = 10 ms
175 6 = 50 ms
176 7 = 100 ms
[all …]
/linux/Documentation/fb/
H A Dviafb.modes15 # Sync Width 3.813 us 0.064 ms
17 # Front Porch 0.636 us 0.318 ms
19 # Back Porch 1.907 us 1.048 ms
21 # Active Time 25.422 us 15.253 ms
23 # Blank Time 6.356 us 1.430 ms
40 # Sync Width 2.032 us 0.080 ms
42 # Front Porch 0.508 us 0.027 ms
44 # Back Porch 3.810 us 0.427 ms
46 # Active Time 20.317 us 12.800 ms
48 # Blank Time 6.349 us 0.533 ms
[all …]
/linux/drivers/input/touchscreen/
H A Dstmpe-ts.c59 * (0 -> 10 us, 1 -> 50 us, 2 -> 100 us, 3 -> 500 us,
60 * 4-> 1 ms, 5 -> 5 ms, 6 -> 10 ms, 7 -> 50 ms)
63 * (0 -> 10 us, 1 -> 100 us, 2 -> 500 us, 3 -> 1 ms,
64 * 4 -> 5 ms, 5 -> 10 ms, 6 for 50 ms, 7 -> 100 ms)
70 * (0 -> 20 mA typical 35 mA max, 1 -> 50 mA typical 80 mA max)
112 * touch_det keeps coming in after 4ms, while the FIFO contains no value in stmpe_work()
169 schedule_delayed_work(&ts->work, msecs_to_jiffies(50)); in stmpe_ts_handler()
/linux/Documentation/translations/zh_CN/scheduler/
H A Dsched-bwc.rst78 cpu.cfs_period_us=100ms
104 /proc/sys/kernel/sched_cfs_bandwidth_slice_us (default=5ms)
174 # echo 250000 > cpu.cfs_quota_us /* quota = 250ms */
175 # echo 250000 > cpu.cfs_period_us /* period = 250ms */
181 # echo 1000000 > cpu.cfs_quota_us /* quota = 1000ms */
182 # echo 500000 > cpu.cfs_period_us /* period = 500ms */
190 # echo 10000 > cpu.cfs_quota_us /* quota = 10ms */
191 # echo 50000 > cpu.cfs_period_us /* period = 50ms */
200 # echo 20000 > cpu.cfs_quota_us /* quota = 20ms */
201 # echo 50000 > cpu.cfs_period_us /* period = 50ms */
[all …]
/linux/drivers/leds/trigger/
H A Dledtrig-activity.c73 /* We come here every 100ms in the worst case, so that's 100M ns of in led_activity_function()
100 * (typically 10ms every second, or 10ms ON, 990ms OFF). Then we want in led_activity_function()
102 * enough to saturate one core in multi-core systems or 50% in single in led_activity_function()
104 * cycle (10ms ON, 90ms OFF). After this point, the blinking frequency in led_activity_function()
106 * the activity, up to the point where we have 90ms ON, 10ms OFF when in led_activity_function()
112 * - a target CPU usage of min(50%, 100%/#CPU) for a 10% duty cycle in led_activity_function()
113 * (10ms ON, 90ms OFF) in led_activity_function()
122 * 100 ms and keep track of the sleep time left. This allows us to in led_activity_function()
135 target = (cpus > 1) ? (100 / cpus) : 50; in led_activity_function()
/linux/sound/soc/codecs/
H A Dmax98373.c85 static DECLARE_TLV_DB_SCALE(max98373_digital_tlv, -6350, 50, 1);
87 0, 8, TLV_DB_SCALE_ITEM(0, 50, 0),
106 14, 15, TLV_DB_SCALE_ITEM(-100, 50, 0),
135 "45ms", "225ms", "450ms", "1150ms",
136 "2250ms", "3100ms", "4500ms", "675
[all...]
/linux/drivers/phy/intel/
H A Dphy-intel-lgm-emmc.c104 0, 50); in intel_emmc_phy_power()
128 * our source clock is at 50 MHz and that lock time scales linearly in intel_emmc_phy_power()
130 * is super slow (like 100 kHZ) this could take as long as 5.1 ms as in intel_emmc_phy_power()
131 * per the math: 10.2 us * (50000000 Hz / 100000 Hz) => 5.1 ms in intel_emmc_phy_power()
137 * extreme cases we've seen it take up to over 10ms (!). We'll be in intel_emmc_phy_power()
138 * generous and give it 50ms. in intel_emmc_phy_power()
143 0, 50 * USEC_PER_MSEC); in intel_emmc_phy_power()
192 /* Drive impedance: 50 Ohm */ in intel_emmc_phy_power_on()
196 dev_err(&phy->dev, "ERROR set drive-impednce-50ohm: %d\n", ret); in intel_emmc_phy_power_on()
H A Dphy-intel-keembay-emmc.c93 else if (mhz <= 80 && mhz >= 50) in keembay_emmc_phy_power()
125 0, 50); in keembay_emmc_phy_power()
161 * our source clock is at 50 MHz and that lock time scales linearly in keembay_emmc_phy_power()
163 * is super slow (like 100kHz) this could take as long as 5.1 ms as in keembay_emmc_phy_power()
164 * per the math: 10.2 us * (50000000 Hz / 100000 Hz) => 5.1 ms in keembay_emmc_phy_power()
170 * extreme cases we've seen it take up to over 10ms (!). We'll be in keembay_emmc_phy_power()
171 * generous and give it 50ms. in keembay_emmc_phy_power()
175 0, 50 * USEC_PER_MSEC); in keembay_emmc_phy_power()
/linux/tools/testing/selftests/net/mptcp/
H A Dsimult_flows.sh21 slack=50
231 [ $delay1 -gt 0 ] && delay1="delay ${delay1}ms" || delay1=""
232 [ $delay2 -gt 0 ] && delay2="delay ${delay2}ms" || delay2=""
243 tc -n $ns1 qdisc add dev ns1eth1 root netem rate ${rate1}mbit $delay1 limit 50
244 tc -n $ns1 qdisc add dev ns1eth2 root netem rate ${rate2}mbit $delay2 limit 50
245 tc -n $ns2 qdisc add dev ns2eth1 root netem rate ${rate1}mbit $delay1 limit 50
246 tc -n $ns2 qdisc add dev ns2eth2 root netem rate ${rate2}mbit $delay2 limit 50
248 # time is measured in ms, account for transfer size, aggregated link speed
250 # ms byte -> bit 10% mbit -> kbit -> bit 10%
254 # completion (see mptcp_connect): 200ms on each side, add some slack
/linux/drivers/video/fbdev/via/
H A Dvt1636.c16 /* T1: VDD on - Data on. Each increment is 1 ms. (50ms = 031h) */
18 /* T2: Data on - Backlight on. Each increment is 2 ms. (210ms = 068h) */
20 /* T3: Backlight off -Data off. Each increment is 2 ms. (210ms = 068h)*/
22 /* T4: Data off - VDD off. Each increment is 1 ms. (50ms = 031h) */
24 /* T5: VDD off - VDD on. Each increment is 100 ms. (500ms = 04h) */
/linux/drivers/iio/light/
H A Dnoa1305.c48 100, 8 * 77, /* 800 ms */
49 100, 4 * 77, /* 400 ms */
50 100, 2 * 77, /* 200 ms */
51 100, 1 * 77, /* 100 ms */
52 1000, 5 * 77, /* 50 ms */
53 10000, 25 * 77, /* 25 ms */
54 100000, 125 * 77, /* 12.5 ms */
55 1000000, 625 * 77, /* 6.25 ms */
59 0, 800000, /* 800 ms */
60 0, 400000, /* 400 ms */
[all …]
/linux/tools/testing/selftests/tc-testing/tc-tests/qdiscs/
H A Ddualpi2.json17 …"matchPattern": "qdisc dualpi2 1: root refcnt [0-9]+ limit 10000p.* step_thresh 1ms min_qlen_step …
56 … "cmdUnderTest": "$TC qdisc add dev $DUMMY handle 1: root dualpi2 typical_rtt 20ms max_rtt 200ms",
59 …ttern": "qdisc dualpi2 1: root refcnt [0-9]+ limit 10000p.* target 20ms tupdate 20ms alpha 0.04296…
77 "cmdUnderTest": "$TC qdisc add dev $DUMMY handle 1: root dualpi2 max_rtt 300ms",
80 …attern": "qdisc dualpi2 1: root refcnt [0-9]+ limit 10000p.* target 50ms tupdate 50ms alpha 0.0507…
/linux/Documentation/devicetree/bindings/hwmon/
H A Dadi,ltc4282.yaml43 adi,fet-bad-timeout-ms:
91 If set, disables the chip to auto-retry 50ms after an Overvoltage fault.
97 If set, disables the chip to auto-retry 50ms after an Undervoltage fault.
150 hwmon@50 {
/linux/Documentation/scsi/
H A Daic7xxx.rst63 AHA-274X[A] aic7770 EISA SE-50M SE-HD50F
65 SE-50M
66 AHA-274X[A]T aic7770 EISA 2 X SE-50M SE-HD50F
67 AHA-2842 aic7770 VL SE-50M SE-HD50F
68 AHA-2940AU aic7860 PCI/32 SE-50M SE-HD50F
69 AVA-2902I aic7860 PCI/32 SE-50M
70 AVA-2902E aic7860 PCI/32 SE-50M
71 AVA-2906 aic7856 PCI/32 SE-50M SE-DB25F
72 APC-7850 aic7850 PCI/32 SE-50M 1
73 AVA-2940 aic7860 PCI/32 SE-50M
[all …]
/linux/drivers/thermal/
H A Dcpuidle_cooling.c37 * means the running duration is zero. If we have a 50% ratio
49 * For example, if we have an injected duration of 50%, then we end up
50 * with 10ms of idle injection and 10ms of running duration.
83 * injection ratio means no idle injection at all and 50% in cpuidle_cooling_get_max_state()
84 * means for 10ms of idle injection, we have 10ms of running in cpuidle_cooling_get_max_state()
/linux/Documentation/accounting/
H A Dpsi.rst74 time window, e.g. 100ms of total stall time within any 500ms window to
86 would add 150ms threshold for partial memory stall measured within
88 would add 50ms threshold for full io stall measured within 1sec time window.
102 The kernel accepts window sizes ranging from 500ms to 10s, therefore min
103 monitoring update interval is 50ms and max is 1s. Min limit is set to
135 * and 150ms threshold.
/linux/Documentation/devicetree/bindings/leds/
H A Dleds-trigger-pattern.txt3 The pattern is given by a series of tuples, of brightness and duration (ms).
8 1. For gradual dimming, the dimming interval now is set as 50 milliseconds. So
9 the tuple with duration less than dimming interval (50ms) is treated as a step
/linux/drivers/input/mouse/
H A Dgpio_mouse.c43 * Timer function which is run every scan_ms ms when the device is opened.
81 error = device_property_read_u32(dev, "scan-interval-ms", in gpio_mouse_probe()
84 dev_warn(dev, "invalid scan time, set to 50 ms\n"); in gpio_mouse_probe()
85 gmouse->scan_ms = 50; in gpio_mouse_probe()
143 dev_dbg(dev, "%d ms scan time, buttons: %s%s%s\n", in gpio_mouse_probe()

12345678910>>...30