| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | amd_energy.rst | 29 The Energy driver exposes the energy counters that are
51 Since, the energy status registers are accessed at core level,
53 in duplicate values. Hence, energy counter entries are not
62 indicating energy status unit is 15.3 micro-Joules increment.
74 Current, Socket energy status register is 32bit, assuming a 240W
79 The Core energy register may wrap around after several days.
82 to accumulate the socket energy counters and one core energy counter
88 based on the chosen energy unit resolution. For example
92 A socket and core energy read would return the current register
93 value added to the respective energy accumulator.
[all …]
|
| 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
|
| D | vexpress.rst | 33 temperature and power usage. Some of them also calculate consumed energy
|
| /kernel/linux/linux-5.10/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;
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/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 …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/hwmon/ |
| D | vexpress.txt | 10 "arm,vexpress-energy"
19 energy@0 {
20 compatible = "arm,vexpress-energy";
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/ |
| D | ste,mcde.txt | 18 (HDMI clock), DSI0ESCLK (DSI0 energy save clock),
19 DSI1ESCLK (DSI1 energy save clock), DSI2ESCLK (DSI2 energy
37 - clocks: phandles to the high speed and low power (energy save) clocks
41 (energy save) clock
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | vexpress-sysreg.txt | 71 "arm,vexpress-energy"
86 - some functions (eg. energy meter, with its 64 bit long counter)
99 energy@0 {
100 compatible = "arm,vexpress-energy";
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | energy-model.rst | 12 subsystems willing to use that information to make energy-aware decisions.
92 There are two API functions which provide the access to the energy model:
98 Subsystems interested in the energy model of a CPU can retrieve it using the
99 em_cpu_get() API. The energy model tables are allocated once upon creation of
102 The energy consumed by a performance domain can be estimated using the
|
| D | index.rst | 14 energy-model
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/supply/ab8500/ |
| D | fg.txt | 4 device comprising: power and energy-management-module,
8 Fuelgauge support is part of energy-management-modules, other
|
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | vexpress-v2p-ca15-tc1.dts | 231 energy {
232 /* Total energy */
233 compatible = "arm,vexpress-energy";
|
| 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";
|
| /kernel/linux/linux-5.10/drivers/net/wireless/intel/iwlwifi/mvm/ |
| D | rx.c | 693 u8 energy[IWL_MVM_STATION_COUNT_MAX]) in iwl_mvm_update_avg_energy()
707 if (!energy[i]) in iwl_mvm_update_avg_energy()
713 sta->avg_energy = energy[i]; in iwl_mvm_update_avg_energy()
816 u8 *energy; in iwl_mvm_handle_rx_statistics() local
897 energy = (void *)&v11->load_stats.avg_energy; in iwl_mvm_handle_rx_statistics()
903 energy = (void *)&stats->load_stats.avg_energy; in iwl_mvm_handle_rx_statistics()
908 iwl_mvm_update_avg_energy(mvm, energy); in iwl_mvm_handle_rx_statistics()
|
| /kernel/linux/linux-5.10/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;
|
| /kernel/linux/linux-5.10/include/linux/power/ |
| D | bq27xxx_battery.h | 54 int energy; member
|
| /kernel/linux/linux-5.10/drivers/staging/iio/meter/ |
| D | Kconfig | 5 menu "Active energy metering IC"
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/iio/temperature/ |
| D | mlx90632.txt | 16 Since measured object emissivity effects Infra Red energy emitted, emissivity
|
| /kernel/linux/linux-5.10/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
|
| /kernel/linux/linux-5.10/kernel/rcu/ |
| D | Kconfig | 149 scheduling-clock interrupts for energy-efficiency reasons will
181 parameter), thus improving energy efficiency. On the other
185 Say Y if energy efficiency is critically important, and you
224 callback invocation to energy-efficient CPUs in battery-powered
|
| /kernel/linux/linux-5.10/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()
|
| /kernel/linux/linux-5.10/Documentation/driver-api/xilinx/ |
| D | eemi.rst | 14 The embedded energy management interface is used to allow software
|