Searched +full:power +full:- +full:on +full:- +full:time +full:- +full:ms (Results 1 – 25 of 1060) sorted by relevance
12345678910>>...43
| /kernel/linux/linux-6.6/Documentation/hwmon/ |
| D | lochnagar.rst | 10 -----------
12 Lochnagar 2 features built-in Current Monitor circuitry that allows for the
13 measurement of both voltage and current on up to eight of the supply voltage
22 ----------------
30 power1_average Measured average power for DBVDD1 (microWatts)
31 power1_average_interval Power averaging time input valid from 1 to 1708mS
37 power2_average Measured average power for 1V8 DSP (microWatts)
38 power2_average_interval Power averaging time input valid from 1 to 1708mS
44 power3_average Measured average power for 1V8 CDC (microWatts)
45 power3_average_interval Power averaging time input valid from 1 to 1708mS
[all …]
|
| D | ds1621.rst | 47 - Christian W. Zuckschwerdt <zany@triq.net>
48 - valuable contributions by Jan M. Sendler <sendler@sendler.de>
49 - ported to 2.6 by Aurelien Jarno <aurelien@aurel32.net>
53 ------------------
62 -----------
66 programmed into non-volatile on-chip registers). Temperature range is -55
68 Fahrenheit range of -67 to +257 degrees with 0.9 steps. If polarity
72 toggle. On the one hand ("heater"), the thermostat output of the chip,
74 stays high until the high limit is met or exceeded. On the other hand
81 of up to +/- 0.5 degrees even when compared against precise temperature
[all …]
|
| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | lochnagar.rst | 10 -----------
12 Lochnagar 2 features built-in Current Monitor circuitry that allows for the
13 measurement of both voltage and current on up to eight of the supply voltage
22 ----------------
30 power1_average Measured average power for DBVDD1 (microWatts)
31 power1_average_interval Power averaging time input valid from 1 to 1708mS
37 power2_average Measured average power for 1V8 DSP (microWatts)
38 power2_average_interval Power averaging time input valid from 1 to 1708mS
44 power3_average Measured average power for 1V8 CDC (microWatts)
45 power3_average_interval Power averaging time input valid from 1 to 1708mS
[all …]
|
| D | ds1621.rst | 47 - Christian W. Zuckschwerdt <zany@triq.net>
48 - valuable contributions by Jan M. Sendler <sendler@sendler.de>
49 - ported to 2.6 by Aurelien Jarno <aurelien@aurel32.net>
53 ------------------
62 -----------
66 programmed into non-volatile on-chip registers). Temperature range is -55
68 Fahrenheit range of -67 to +257 degrees with 0.9 steps. If polarity
72 toggle. On the one hand ("heater"), the thermostat output of the chip,
74 stays high until the high limit is met or exceeded. On the other hand
81 of up to +/- 0.5 degrees even when compared against precise temperature
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/sound/ |
| D | cirrus,cs42l42.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - patches@opensource.cirrus.com
13 The CS42L42 is a low-power audio codec designed for portable applications.
14 It provides a high-dynamic range, stereo DAC for audio playback and a mono
15 high-dynamic-range ADC for audio capture. There is an integrated headset
21 - cirrus,cs42l42
22 - cirrus,cs42l83
29 VP-supply:
[all …]
|
| D | cs35l33.txt | 5 - compatible : "cirrus,cs35l33"
7 - reg : the I2C address of the device for I2C
9 - VA-supply, VP-supply : power supplies for the device,
15 - reset-gpios : gpio used to reset the amplifier
17 - interrupts : IRQ line info CS35L33.
18 (See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
21 - cirrus,boost-ctl : Booster voltage use to supply the amp. If the value is
26 - cirrus,ramp-rate : On power up, it affects the time from when the power
27 up sequence begins to the time the audio reaches a full-scale output.
28 On power down, it affects the time from when the power-down sequence
[all …]
|
| D | cirrus,cs42l43.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - patches@opensource.cirrus.com
21 - $ref: dai-common.yaml#
26 - cirrus,cs42l43
31 vdd-p-supply:
33 Power supply for the high voltage interface.
35 vdd-a-supply:
37 Power supply for internal analog circuits.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/reset/ |
| D | gpio-poweroff.txt | 1 Driver a GPIO line that can be used to turn the power off.
3 The driver supports both level triggered and edge triggered power off.
4 At driver load time, the driver will request the given gpio line and
5 install a handler to power off the system. If the optional properties
9 When the power-off handler is called, the gpio is configured as an
10 output, and drive active, so triggering a level triggered power off
11 condition. This will also cause an inactive->active edge condition, so
12 triggering positive edge triggered power off. After a delay of 100ms,
13 the GPIO is set to inactive, thus causing an active->inactive edge,
14 triggering negative edge triggered power off. After another 100ms
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/sound/ |
| D | cs35l33.txt | 5 - compatible : "cirrus,cs35l33"
7 - reg : the I2C address of the device for I2C
9 - VA-supply, VP-supply : power supplies for the device,
15 - reset-gpios : gpio used to reset the amplifier
17 - interrupts : IRQ line info CS35L33.
18 (See Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
21 - cirrus,boost-ctl : Booster voltage use to supply the amp. If the value is
26 - cirrus,ramp-rate : On power up, it affects the time from when the power
27 up sequence begins to the time the audio reaches a full-scale output.
28 On power down, it affects the time from when the power-down sequence
[all …]
|
| /kernel/linux/linux-6.6/tools/power/cpupower/bench/ |
| D | README-BENCH | 1 This is cpufreq-bench, a microbenchmark for the cpufreq framework.
7 - Identify worst case performance loss when doing dynamic frequency
9 - Identify average reaction time of a governor to CPU load changes
10 - (Stress) Testing whether a cpufreq low level driver or governor works
12 - Identify cpufreq related performance regressions between kernels
13 - Possibly Real time priority testing? -> what happens if there are
15 - ...
18 - Power saving related regressions (In fact as better the performance
19 throughput is, the worse the power savings will be, but the first should
21 - Real world (workloads)
[all …]
|
| /kernel/linux/linux-5.10/tools/power/cpupower/bench/ |
| D | README-BENCH | 1 This is cpufreq-bench, a microbenchmark for the cpufreq framework.
7 - Identify worst case performance loss when doing dynamic frequency
9 - Identify average reaction time of a governor to CPU load changes
10 - (Stress) Testing whether a cpufreq low level driver or governor works
12 - Identify cpufreq related performance regressions between kernels
13 - Possibly Real time priority testing? -> what happens if there are
15 - ...
18 - Power saving related regressions (In fact as better the performance
19 throughput is, the worse the power savings will be, but the first should
21 - Real world (workloads)
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/usb/ |
| D | usb251xb.txt | 1 Microchip USB 2.0 Hi-Speed Hub Controller
4 Hi-Speed Controller.
7 - compatible : Should be "microchip,usb251xb" or one of the specific types:
11 - reg : I2C address on the selected bus (default is <0x2C>)
14 - reset-gpios : Should specify the gpio for hub reset
15 - vdd-supply : Should specify the phandle to the regulator supplying vdd
16 - skip-config : Skip Hub configuration, but only send the USB-Attach command
17 - vendor-id : Set USB Vendor ID of the hub (16 bit, default is 0x0424)
18 - product-id : Set USB Product ID of the hub (16 bit, default depends on type)
19 - device-id : Set USB Device ID of the hub (16 bit, default is 0x0bb3)
[all …]
|
| /kernel/linux/linux-6.6/tools/perf/Documentation/ |
| D | perf-timechart.txt | 1 perf-timechart(1)
5 ----
6 perf-timechart - Tool to visualize total system behavior during a workload
9 --------
14 -----------
19 and CPU events (task switches, running times, CPU power states, etc),
20 but it's possible to record IO (disk, network) activity using -I argument.
24 on the events in the perf.data file, timechart will contain scheduler/cpu
30 There are also poll bars which show how much time application spent
34 -----------------
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/Documentation/ |
| D | perf-timechart.txt | 1 perf-timechart(1)
5 ----
6 perf-timechart - Tool to visualize total system behavior during a workload
9 --------
14 -----------
19 and CPU events (task switches, running times, CPU power states, etc),
20 but it's possible to record IO (disk, network) activity using -I argument.
24 on the events in the perf.data file, timechart will contain scheduler/cpu
30 There are also poll bars which show how much time application spent
34 -----------------
[all …]
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/input/touchscreen/ |
| D | cypress,cy8ctma340.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
14 - Javier Martinez Canillas <javier@dowhile0.org>
15 - Linus Walleij <linus.walleij@linaro.org>
18 - $ref: touchscreen.yaml#
26 - const: cypress,cy8ctma340
27 - const: cypress,cy8ctst341
28 - const: cypress,cyttsp-spi
31 - const: cypress,cyttsp-i2c
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/wireless/ti/wl12xx/ |
| D | conf.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
11 /* these are number of channels on the band divided by two, rounded up */
17 * Per channel power compensation for 2.4GHz
24 * Per channel power compensation for 5GHz
38 * Configure the min and max time BT gains the antenna
41 * Range: 0 - 255 (ms)
47 * Configure the min and max time BT gains the antenna
50 * Range: 0 - 255 (ms)
56 * Configure the min and max time BT gains the antenna
59 * Range: 0 - 255 (ms)
[all …]
|
| /kernel/linux/linux-6.6/drivers/net/wireless/ti/wl12xx/ |
| D | conf.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
11 /* these are number of channels on the band divided by two, rounded up */
17 * Per channel power compensation for 2.4GHz
24 * Per channel power compensation for 5GHz
38 * Configure the min and max time BT gains the antenna
41 * Range: 0 - 255 (ms)
47 * Configure the min and max time BT gains the antenna
50 * Range: 0 - 255 (ms)
56 * Configure the min and max time BT gains the antenna
59 * Range: 0 - 255 (ms)
[all …]
|
| /kernel/linux/linux-6.6/Documentation/leds/ |
| D | leds-mt6370-rgb.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 -----------
10 The MT6370 integrates a four-channel RGB LED driver, designed to provide a
13 a sink current up to 24mA and a CHG_VIN power good indicator LED with sink
22 --------------------------------
26 The breath pattern is a series of timing pairs, with the hold-time expressed in
30 depending on the current brightness setting.
34 "0 Tr1 0 Tr2 0 Tf1 0 Tf2 0 Ton 0 Toff" --> '0' for dummy brightness code
43 | --- --- ---
44 |--- --- ---
[all …]
|
| /kernel/linux/linux-5.10/tools/power/pm-graph/config/ |
| D | suspend-x2-proc.cfg | 2 # Proc S3 (Suspend to Mem) x2 test - includes user processes
5 # all the tool arguments so that they don't have to be given on the
9 # sudo ./sleepgraph.py -config config/suspend-proc.cfg
14 # ---- General Options ----
25 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
26 output-dir: suspend-{hostname}-{date}-{time}-x2-proc
37 # insert a small visible gap between suspend and resume on the timeline (default: false)
40 # ---- Advanced Options ----
43 # command: echo mem > /sys/power/state
58 # Time delay between the two test runs in ms (default: 0 ms)
[all …]
|
| D | standby-dev.cfg | 2 # Dev S1 (Standby) test - includes src calls / kernel threads
5 # all the tool arguments so that they don't have to be given on the
9 # sudo ./sleepgraph.py -config config/standby-dev.cfg
14 # ---- General Options ----
25 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
26 output-dir: standby-{hostname}-{date}-{time}-dev
37 # insert a small visible gap between suspend and resume on the timeline (default: false)
40 # ---- Advanced Options ----
43 # command: echo standby > /sys/power/state
58 # Time delay between the two test runs in ms (default: 0 ms)
[all …]
|
| D | freeze-dev.cfg | 2 # Dev S2 (Freeze) test - includes src calls / kernel threads
5 # all the tool arguments so that they don't have to be given on the
9 # sudo ./sleepgraph.py -config config/freeze-dev.cfg
14 # ---- General Options ----
25 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
26 output-dir: freeze-{hostname}-{date}-{time}-dev
37 # insert a small visible gap between suspend and resume on the timeline (default: false)
40 # ---- Advanced Options ----
43 # command: echo freeze > /sys/power/state
58 # Time delay between the two test runs in ms (default: 0 ms)
[all …]
|
| D | suspend-dev.cfg | 2 # Dev S3 (Suspend to Mem) test - includes src calls / kernel threads
5 # all the tool arguments so that they don't have to be given on the
9 # sudo ./sleepgraph.py -config config/suspend-dev.cfg
14 # ---- General Options ----
25 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
26 output-dir: suspend-{hostname}-{date}-{time}-dev
37 # insert a small visible gap between suspend and resume on the timeline (default: false)
40 # ---- Advanced Options ----
43 # command: echo mem > /sys/power/state
58 # Time delay between the two test runs in ms (default: 0 ms)
[all …]
|
| /kernel/linux/linux-6.6/tools/power/pm-graph/config/ |
| D | suspend-x2-proc.cfg | 2 # Proc S3 (Suspend to Mem) x2 test - includes user processes
5 # all the tool arguments so that they don't have to be given on the
9 # sudo ./sleepgraph.py -config config/suspend-proc.cfg
14 # ---- General Options ----
25 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
26 output-dir: suspend-{hostname}-{date}-{time}-x2-proc
37 # insert a small visible gap between suspend and resume on the timeline (default: false)
40 # ---- Advanced Options ----
43 # command: echo mem > /sys/power/state
58 # Time delay between the two test runs in ms (default: 0 ms)
[all …]
|
| D | standby-dev.cfg | 2 # Dev S1 (Standby) test - includes src calls / kernel threads
5 # all the tool arguments so that they don't have to be given on the
9 # sudo ./sleepgraph.py -config config/standby-dev.cfg
14 # ---- General Options ----
25 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
26 output-dir: standby-{hostname}-{date}-{time}-dev
37 # insert a small visible gap between suspend and resume on the timeline (default: false)
40 # ---- Advanced Options ----
43 # command: echo standby > /sys/power/state
58 # Time delay between the two test runs in ms (default: 0 ms)
[all …]
|
| D | freeze-dev.cfg | 2 # Dev S2 (Freeze) test - includes src calls / kernel threads
5 # all the tool arguments so that they don't have to be given on the
9 # sudo ./sleepgraph.py -config config/freeze-dev.cfg
14 # ---- General Options ----
25 # output folder for html, ftrace, and dmesg. Use {date} and {time} for current values
26 output-dir: freeze-{hostname}-{date}-{time}-dev
37 # insert a small visible gap between suspend and resume on the timeline (default: false)
40 # ---- Advanced Options ----
43 # command: echo freeze > /sys/power/state
58 # Time delay between the two test runs in ms (default: 0 ms)
[all …]
|
12345678910>>...43