/openbmc/linux/Documentation/devicetree/bindings/net/ |
H A D | smsc-lan87xx.txt | 12 - 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;
|
H A D | ethernet-phy.yaml | 120 Mark the corresponding energy efficient ethernet mode as 126 Mark the corresponding energy efficient ethernet mode as 132 Mark the corresponding energy efficient ethernet mode as 138 Mark the corresponding energy efficient ethernet mode as 144 Mark the corresponding energy efficient ethernet mode as 150 Mark the corresponding energy efficient ethernet mode as
|
/openbmc/linux/Documentation/ABI/testing/ |
H A D | sysfs-firmware-papr-energy-scale-info | 5 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>
|
/openbmc/linux/Documentation/scheduler/ |
H A D | sched-energy.rst | 9 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, 32 - energy = [joule] (resource like a battery on powered devices) 33 - power = energy/time = [joule/second] = [watt] 44 energy [J] 54 implications of its decisions rather than blindly applying energy-saving 65 and their respective energy costs. 247 is be the best candidate from an energy-efficiency standpoint. 348 independent EM framework in Documentation/power/energy-model.rst. 365 The energy-aware wake-up algorithm has a complexity of: [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/hwmon/ |
H A D | vexpress.txt | 10 "arm,vexpress-energy" 19 energy@0 { 20 compatible = "arm,vexpress-energy";
|
H A D | adi,ltc2947.yaml | 7 title: Analog Devices LTC2947 high precision power and energy monitor 13 Analog Devices LTC2947 high precision power and energy monitor over SPI or I2C. 29 charge and energy. When an external clock is used, this property must be 36 calculate charge and energy so that, they can be only accumulated for 68 the accumulation of charge, energy and time. This function can be
|
/openbmc/qemu/docs/specs/ |
H A D | rapl-msr.rst | 6 energy consumption of various power domains (e.g. CPU packages, DRAM, etc.). 10 registers that represent the accumulated energy consumption in micro Joules. 35 energy consumed since the last time the register was cleared. If you multiply 42 "rdmsr 0x611") will retrieve the same value. The value represents the energy 60 will do what they have to do and so the energy counter will increase. 63 time spent scheduled for each QEMU thread *and* the energy spent by the 71 7. The total energy spent by the non-vcpu threads is divided by the number 73 energy spent by the QEMU workers. 75 8. Calculate the ratio of energy spent per vcpu threads. 77 9. Calculate the energy for each virtual package. [all …]
|
/openbmc/linux/arch/x86/events/ |
H A D | rapl.c | 397 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 …]
|
/openbmc/linux/Documentation/hwmon/ |
H A D | ltc2947.rst | 21 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)
|
H A D | ibmaem.rst | 26 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
|
/openbmc/phosphor-dbus-interfaces/yaml/org/freedesktop/UPower/ |
H A D | Device.interface.yaml | 142 "Amount of energy (measured in Wh) currently available in the power 149 "Amount of energy (measured in Wh) in the power source when it's 156 "Amount of energy (measured in Wh) in the power source when it's 163 "Amount of energy (measured in Wh) the power source is designed to 170 "Amount of energy being drained from the source, measured in W. If 202 "The amount of energy left in the power source expressed as a 203 percentage between 0 and 100. Typically this is the same as (energy - 204 energy-empty) / (energy-full - energy-empty). However, some primitive 206 case the energy-* properties will be unset while this property is
|
/openbmc/linux/Documentation/translations/zh_CN/scheduler/ |
H A D | sched-energy.rst | 4 :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框架部分。
|
/openbmc/linux/tools/testing/selftests/amd-pstate/ |
H A D | gitsource.sh | 86 …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)
|
H A D | tbench.sh | 71 …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…
|
/openbmc/linux/drivers/powercap/ |
H A D | Kconfig | 84 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.
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Sensor/ |
H A D | Value.interface.yaml | 8 energy 44 namespace, Unit must be "Amperes". For objects in the energy 94 Rate of energy transfer as Watts. 124 value: energy
|
/openbmc/linux/Documentation/devicetree/bindings/arm/ |
H A D | vexpress-config.yaml | 242 "^energy(-.+)?$": 246 const: arm,vexpress-energy 249 description: energy sensor identifier 281 energy { 282 compatible = "arm,vexpress-energy";
|
/openbmc/linux/Documentation/devicetree/bindings/cpu/ |
H A D | idle-states.yaml | 71 timing and energy related properties, that underline the HW behaviour 101 IDLE: This is the actual energy-saving idle period. This may last 144 expressed in time units but must factor in energy consumption coefficients. 146 The energy consumption of a cpu when it enters a power state can be roughly 173 and denotes the energy costs incurred while entering and leaving the idle 181 which choosing that state become the most energy efficient option. A good 183 states energy consumptions plots. 207 |IDLE1-energy < IDLE2-energy | IDLE2-energy < IDLE1-energy 213 In graph 2 above, that takes into account idle states entry/exit energy 221 However, the lower power consumption (i.e. shallower energy curve slope) of [all …]
|
/openbmc/webui-vue/src/env/assets/styles/ |
H A D | _intel.scss | 26 $energy-blue: #00C7FD; 34 $cyan: $energy-blue;
|
/openbmc/linux/Documentation/arch/x86/ |
H A D | intel-hfi.rst | 14 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.
|
/openbmc/phosphor-dbus-interfaces/yaml/org/open_power/Sensor/Aggregation/History/ |
H A D | Average.interface.yaml | 22 Unit must be "Watts". For objects in the energy namespace, Unit must 54 Rate of energy transfer as Watts.
|
H A D | Maximum.interface.yaml | 22 Unit must be "Watts". For objects in the energy namespace, Unit must 54 Rate of energy transfer as Watts.
|
/openbmc/linux/Documentation/devicetree/bindings/power/supply/ |
H A D | bq27xxx.yaml | 64 - energy-full-design-microwatt-hours 81 energy-full-design-microwatt-hours = <5290000>;
|
/openbmc/linux/Documentation/power/ |
H A D | energy-model.rst | 12 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
|
/openbmc/linux/drivers/gpu/drm/i915/ |
H A D | i915_hwmon.c | 126 hwm_energy(struct hwm_drvdata *ddat, long *energy) in hwm_energy() argument 151 *energy = mul_u64_u32_shr(ei->accum_energy, SF_ENERGY, in hwm_energy() 277 HWMON_CHANNEL_INFO(energy, HWMON_E_INPUT), 283 HWMON_CHANNEL_INFO(energy, HWMON_E_INPUT), 730 long energy; in hwm_get_preregistration_info() local 775 hwm_energy(ddat, &energy); in hwm_get_preregistration_info() 778 hwm_energy(&hwmon->ddat_gt[i], &energy); in hwm_get_preregistration_info()
|