Home
last modified time | relevance | path

Searched refs:power (Results 1 – 25 of 35) sorted by relevance

12

/tools/
DMakefile62 $(call descend,power/$@)
65 $(call descend,power/$@)
91 $(call descend,power/x86/$@)
109 $(call descend,power/$(@:_install=),install)
112 $(call descend,power/$(@:_install=),install)
124 $(call descend,power/x86/$(@:_install=),install)
143 $(call descend,power/acpi,clean)
146 $(call descend,power/cpupower,clean)
171 $(call descend,power/x86/$(@:_clean=),clean)
/tools/testing/selftests/cpufreq/
Dcpufreq.sh211 if [ ! -d $SYSFS/power/ -o ! -f $SYSFS/power/state ]; then
226 present=$(cat $SYSFS/power/state | grep $filename)
235 echo $filename > $SYSFS/power/state
/tools/power/cpupower/utils/
Dcpufreq-set.c69 int power = 0, match_count = 0, i, cp, pad; in string_to_frequency() local
91 power = unit->power_of_ten; in string_to_frequency()
102 while (power > -1 && isdigit(str[cp+1])) { in string_to_frequency()
104 power--; in string_to_frequency()
107 if (power >= -1) { /* not enough => pad */ in string_to_frequency()
108 pad = power + 1; in string_to_frequency()
111 cp += power + 1; in string_to_frequency()
/tools/perf/Documentation/
Dperf-timechart.txt19 and CPU events (task switches, running times, CPU power states, etc),
45 --power-only::
46 Only output the CPU power section of the diagram
86 --power-only::
87 Record only power-related events
Ditrace.txt7 p synthesize power events
46 ptwrite, power) at the beginning. This is useful to ignore initialization code.
Dperf-kvm.txt125 Number of mmap data pages (must be a power of two) or size
127 size is rounded up to have nearest pages power of two value.
Dperf-intel-pt.txt177 unpack the raw data for power events and PTWRITE.
461 pwr_evt Enable power events. The power events provide information about
861 p synthesize "power" events
894 "Power" events correspond to power event packets and CBR (core-to-bus ratio)
895 packets. While CBR packets are always recorded when tracing is enabled, power
897 the config terms section above. The power events record information about
1039 - power events, ptwrite, transaction start and abort
1043 option must be used also to show power events.
Dexamples.txt217 expressive power of system analysis and performance
/tools/testing/selftests/ftrace/test.d/event/
Devent-no-pid.tc52 enable_system power
/tools/power/acpi/
DMakefile.config18 OUTPUT := $(O)/tools/power/acpi/
/tools/power/cpupower/
DToDo6 - Somewhere saw the ability to read power consumption of
/tools/testing/selftests/powerpc/nx-gzip/
DREADME45 https://github.com/libnxz/power-gzip
/tools/power/pm-graph/config/
Dstandby.cfg43 # command: echo standby > /sys/power/state
Dfreeze.cfg43 # command: echo freeze > /sys/power/state
Dstandby-callgraph.cfg44 # command: echo standby > /sys/power/state
Dsuspend.cfg43 # command: echo mem > /sys/power/state
Dfreeze-dev.cfg43 # command: echo freeze > /sys/power/state
Dsuspend-callgraph.cfg44 # command: echo mem > /sys/power/state
Dsuspend-dev.cfg43 # command: echo mem > /sys/power/state
Dsuspend-x2-proc.cfg43 # command: echo mem > /sys/power/state
Dstandby-dev.cfg43 # command: echo standby > /sys/power/state
Dfreeze-callgraph.cfg44 # command: echo freeze > /sys/power/state
Dexample.cfg67 # command: echo mem > /sys/power/state
/tools/power/pm-graph/
DREADME107 in file: kernel/power/suspend.c
131 Execute a test using one of the available power modes, e.g. mem (S3):
304 There are corresponding configs for other power modes:
368 command: echo mem > /sys/power/state
558 is "mem" a valid power mode: YES
/tools/power/cpupower/bench/
DREADME-BENCH19 throughput is, the worse the power savings will be, but the first should

12