Home
last modified time | relevance | path

Searched refs:energy (Results 1 – 25 of 95) sorted by relevance

1234

/Linux-v6.6/Documentation/devicetree/bindings/net/
Dsmsc-lan87xx.txt12 - smsc,disable-energy-detect:
13 If set, do not enable energy detect mode for the SMSC phy.
14 default: enable energy detect mode
17 smsc phy with disabled energy detect mode on an am335x based board.
25 smsc,disable-energy-detect;
/Linux-v6.6/Documentation/scheduler/
Dsched-energy.rst9 the impact of its decisions on the energy consumed by CPUs. EAS relies on an
10 Energy Model (EM) of the CPUs to select an energy efficient CPU for each task,
20 because this is where the potential for saving energy through scheduling is
25 please refer to its documentation (see Documentation/power/energy-model.rst).
32 - energy = [joule] (resource like a battery on powered devices)
33 - power = energy/time = [joule/second] = [watt]
35 The goal of EAS is to minimize energy, while still getting the job done. That
44 energy [J]
50 scheduler. This alternative considers two objectives: energy-efficiency and
54 implications of its decisions rather than blindly applying energy-saving
[all …]
Dindex.rst16 sched-energy
/Linux-v6.6/Documentation/ABI/testing/
Dsysfs-firmware-papr-energy-scale-info5 energy/frequency on Linux running as a PAPR guest.
9 energy-savings mode and processor frequency.
19 Description: String description of the energy attribute of <id>
24 Description: Numeric value of the energy attribute of <id>
29 Description: String value of the energy attribute of <id>
Dsysfs-driver-intel-i915-hwmon73 reflects energy input for the entire device. For gt level
74 hwmon devices (name "i915_gtN") this reflects energy input
/Linux-v6.6/arch/x86/events/
Drapl.c397 RAPL_EVENT_ATTR_STR(energy-cores, rapl_cores, "event=0x01");
398 RAPL_EVENT_ATTR_STR(energy-pkg , rapl_pkg, "event=0x02");
399 RAPL_EVENT_ATTR_STR(energy-ram , rapl_ram, "event=0x03");
400 RAPL_EVENT_ATTR_STR(energy-gpu , rapl_gpu, "event=0x04");
401 RAPL_EVENT_ATTR_STR(energy-psys, rapl_psys, "event=0x05");
403 RAPL_EVENT_ATTR_STR(energy-cores.unit, rapl_cores_unit, "Joules");
404 RAPL_EVENT_ATTR_STR(energy-pkg.unit , rapl_pkg_unit, "Joules");
405 RAPL_EVENT_ATTR_STR(energy-ram.unit , rapl_ram_unit, "Joules");
406 RAPL_EVENT_ATTR_STR(energy-gpu.unit , rapl_gpu_unit, "Joules");
407 RAPL_EVENT_ATTR_STR(energy-psys.unit, rapl_psys_unit, "Joules");
[all …]
/Linux-v6.6/Documentation/devicetree/bindings/hwmon/
Dvexpress.txt10 "arm,vexpress-energy"
19 energy@0 {
20 compatible = "arm,vexpress-energy";
/Linux-v6.6/Documentation/hwmon/
Dltc2947.rst21 The LTC2947 is a high precision power and energy monitor that measures current,
22 voltage, power, temperature, charge and energy. The device supports both SPI
24 The device also measures accumulated quantities as energy. It has two banks of
25 register's to read/set energy related values. These banks can be configured
97 energy1_input Measured energy over time (in microJoule)
99 energy2_input Measured energy over time (in microJoule)
Dibmaem.rst26 This driver implements sensor reading support for the energy and power meters
31 The v1 AEM interface has a simple set of features to monitor energy use. There
32 is a register that displays an estimate of raw energy consumption since the
37 range of energy and power use registers, the power cap as set by the AEM
/Linux-v6.6/Documentation/translations/zh_CN/scheduler/
Dsched-energy.rst4 :Original: Documentation/scheduler/sched-energy.rst
30 它提供的内容,请参考其文档(见Documentation/power/energy-model.rst)。
77 见Documentation/power/energy-model.rst)
287 Documentation/power/energy-model.rst中的独立EM框架部分。
Dindex.rst27 sched-energy
/Linux-v6.6/tools/testing/selftests/amd-pstate/
Dgitsource.sh86 …perf stat -a --per-socket -I 1000 -e power/energy-pkg/ /usr/bin/time -o ../$OUTFILE_GIT.time-gitso…
115 grep Joules $OUTFILE_GIT-perf-$1-$2.log | awk '{print $4}' > $OUTFILE_GIT-energy-$1-$2.log
116 en_sum=$(awk 'BEGIN {sum=0};{sum += $1};END {print sum}' $OUTFILE_GIT-energy-$1-$2.log)
170 …$OUTFILE_GIT.result | grep "power consumption(J):" | awk '{print $NF}' > $OUTFILE_GIT-energy-$1.log
171 en_sum=$(awk 'BEGIN {sum=0};{sum += $1};END {print sum}' $OUTFILE_GIT-energy-$1.log)
174 avg_en=$(awk 'BEGIN {sum=0};{sum += $1};END {print sum/'$LOOP_TIMES'}' $OUTFILE_GIT-energy-$1.log)
Dtbench.sh71 …perf stat -a --per-socket -I 1000 -e power/energy-pkg/ tbench -t $TIME_LIMIT $PROCESS_NUM > $OUTFI…
102 grep Joules $OUTFILE_TBENCH-perf-$1-$2.log | awk '{print $4}' > $OUTFILE_TBENCH-energy-$1-$2.log
103 en_sum=$(awk 'BEGIN {sum=0};{sum += $1};END {print sum}' $OUTFILE_TBENCH-energy-$1-$2.log)
157 …LE_TBENCH.result | grep "power consumption(J):" | awk '{print $NF}' > $OUTFILE_TBENCH-energy-$1.log
158 en_sum=$(awk 'BEGIN {sum=0};{sum += $1};END {print sum}' $OUTFILE_TBENCH-energy-$1.log)
161 …avg_en=$(awk 'BEGIN {sum=0};{sum += $1};END {print sum/'$LOOP_TIMES'}' $OUTFILE_TBENCH-energy-$1.l…
/Linux-v6.6/drivers/powercap/
DKconfig84 bool "Add CPU power capping based on the energy model"
88 energy model.
91 bool "Add device power capping based on the energy model"
95 energy model.
/Linux-v6.6/Documentation/arch/x86/
Dintel-hfi.rst14 The HFI gives the operating system a performance and energy efficiency
22 about the performance and energy efficiency of each CPU in the system. Each
38 task placement decisions. For instance, if either the performance or energy
41 that processor for performance or energy efficiency reasons, respectively.
/Linux-v6.6/Documentation/power/
Denergy-model.rst12 subsystems willing to use that information to make energy-aware decisions.
27 Documentation/scheduler/sched-energy.rst. For some subsystems like thermal or
36 an 'abstract scale' deriving real energy in micro-Joules would not be possible.
162 There are two API functions which provide the access to the energy model:
168 Subsystems interested in the energy model of a CPU can retrieve it using the
169 em_cpu_get() API. The energy model tables are allocated once upon creation of
172 The energy consumed by a performance domain can be estimated using the
Dindex.rst14 energy-model
/Linux-v6.6/drivers/gpu/drm/i915/
Di915_hwmon.c125 hwm_energy(struct hwm_drvdata *ddat, long *energy) in hwm_energy() argument
150 *energy = mul_u64_u32_shr(ei->accum_energy, SF_ENERGY, in hwm_energy()
275 HWMON_CHANNEL_INFO(energy, HWMON_E_INPUT),
281 HWMON_CHANNEL_INFO(energy, HWMON_E_INPUT),
729 long energy; in hwm_get_preregistration_info() local
774 hwm_energy(ddat, &energy); in hwm_get_preregistration_info()
777 hwm_energy(&hwmon->ddat_gt[i], &energy); in hwm_get_preregistration_info()
/Linux-v6.6/arch/arm/boot/dts/arm/
Dvexpress-v2p-ca15_a7.dts394 energy-a15 {
395 /* Total energy for the two A15 cores */
396 compatible = "arm,vexpress-energy";
401 energy-a7 {
402 /* Total energy for the three A7 cores */
403 compatible = "arm,vexpress-energy";
Dvexpress-v2p-ca15-tc1.dts231 energy {
232 /* Total energy */
233 compatible = "arm,vexpress-energy";
/Linux-v6.6/Documentation/translations/zh_CN/power/
Denergy-model.rst4 :Original: Documentation/power/energy-model.rst
28 Documentation/scheduler/sched-energy.rst。对于一些子系统,比如热能或
Dindex.rst17 energy-model
/Linux-v6.6/Documentation/power/powercap/
Dpowercap.rst154 the zones and subzones contain energy monitoring attributes (energy_uj,
197 Current energy counter in micro joules. Write "0" to reset.
201 Range of the above energy counter in micro-joules.
212 It is possible that some domains have both power ranges and energy counter ranges;
/Linux-v6.6/drivers/net/wireless/intel/iwlwifi/mvm/
Drx.c719 u8 *energy = _data; in iwl_mvm_stats_energy_iter() local
726 if (energy[sta_id]) in iwl_mvm_stats_energy_iter()
727 mvmsta->deflink.avg_energy = energy[sta_id]; in iwl_mvm_stats_energy_iter()
919 u8 *energy; in iwl_mvm_handle_rx_statistics() local
1000 energy = (void *)&v11->load_stats.avg_energy; in iwl_mvm_handle_rx_statistics()
1006 energy = (void *)&stats->load_stats.avg_energy; in iwl_mvm_handle_rx_statistics()
1011 energy); in iwl_mvm_handle_rx_statistics()
/Linux-v6.6/Documentation/admin-guide/pm/
Damd-pstate.rst116 more energy efficient than higher performance levels. This register
159 toward performance (0x0) or energy efficiency (0xff).
270 to the low-level firmware about the user's desired energy vs efficiency
276 The current energy performance preference can be read from this attribute.
277 and user can change current preference according to energy or performance needs
299 platforms. The AMD P-States mechanism is the more performance and energy
311 and takes into account only the values set to the minimum, maximum and energy
327 wants to bias toward performance (0x0) or energy efficiency (0xff) to the CPPC firmware.
526 These changes include desire performance, frequency, load, performance, energy etc.
533 These changes include desire performance, frequency, load, time, energy etc.
[all …]

1234