| /Linux-v6.1/Documentation/devicetree/bindings/net/ |
| 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;
|
| /Linux-v6.1/Documentation/scheduler/ |
| 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,
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 …]
|
| D | index.rst | 16 sched-energy
|
| /Linux-v6.1/Documentation/ABI/testing/ |
| 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>
|
| /Linux-v6.1/arch/x86/events/ |
| 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 …]
|
| /Linux-v6.1/Documentation/devicetree/bindings/hwmon/ |
| D | vexpress.txt | 10 "arm,vexpress-energy"
19 energy@0 {
20 compatible = "arm,vexpress-energy";
|
| /Linux-v6.1/Documentation/hwmon/ |
| 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)
|
| 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
|
| /Linux-v6.1/drivers/powercap/ |
| D | Kconfig | 55 bool "Add CPU power capping based on the energy model"
59 energy model.
62 bool "Add device power capping based on the energy model"
66 energy model.
|
| /Linux-v6.1/Documentation/translations/zh_CN/scheduler/ |
| 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框架部分。
|
| D | index.rst | 27 sched-energy
|
| /Linux-v6.1/Documentation/x86/ |
| 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.
|
| /Linux-v6.1/Documentation/power/ |
| 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
|
| D | index.rst | 14 energy-model
|
| /Linux-v6.1/Documentation/translations/zh_CN/power/ |
| D | energy-model.rst | 4 :Original: Documentation/power/energy-model.rst
28 Documentation/scheduler/sched-energy.rst。对于一些子系统，比如热能或
|
| D | index.rst | 17 energy-model
|
| /Linux-v6.1/arch/arm/boot/dts/ |
| D | vexpress-v2p-ca15_a7.dts | 394 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";
|
| D | vexpress-v2p-ca15-tc1.dts | 231 energy {
232 /* Total energy */
233 compatible = "arm,vexpress-energy";
|
| /Linux-v6.1/Documentation/power/powercap/ |
| D | powercap.rst | 154 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.1/drivers/net/wireless/intel/iwlwifi/mvm/ |
| D | rx.c | 716 u8 *energy = _data; in iwl_mvm_stats_energy_iter() local
723 if (energy[sta_id]) in iwl_mvm_stats_energy_iter()
724 mvmsta->avg_energy = energy[sta_id]; in iwl_mvm_stats_energy_iter()
916 u8 *energy; in iwl_mvm_handle_rx_statistics() local
997 energy = (void *)&v11->load_stats.avg_energy; in iwl_mvm_handle_rx_statistics()
1003 energy = (void *)&stats->load_stats.avg_energy; in iwl_mvm_handle_rx_statistics()
1008 energy); in iwl_mvm_handle_rx_statistics()
|
| /Linux-v6.1/include/linux/power/ |
| D | bq27xxx_battery.h | 55 int energy; member
|
| /Linux-v6.1/drivers/staging/iio/meter/ |
| D | Kconfig | 5 menu "Active energy metering IC"
|
| /Linux-v6.1/Documentation/admin-guide/pm/ |
| D | strategies.rst | 39 draw (or maximum energy usage) of it. If all of them are inactive, the system
46 runtime idle in one go. For this reason, systems usually use less energy in
|
| /Linux-v6.1/drivers/hwmon/ |
| D | ibmaem.c | 159 u64 energy[AEM_NUM_ENERGY_REGS]; member
430 &data->energy[which], 8); in update_aem_energy_one()
839 before = data->energy[attr->index]; in aem_show_power()
851 after = data->energy[attr->index]; in aem_show_power()
872 (unsigned long long)a->energy[attr->index] * 1000); in aem_show_energy()
|
| /Linux-v6.1/Documentation/driver-api/thermal/ |
| D | cpu-idle-cooling.rst | 50 dynamic leakage for this period (modulo the energy needed to enter
138 for thermal mitigation, otherwise we end up consuming more energy.
193 target residency, otherwise we end up consuming more energy and
|
