| /Linux-v5.4/Documentation/devicetree/bindings/net/ |
| D | smsc-lan87xx.txt | 8 - smsc,disable-energy-detect:
9 If set, do not enable energy detect mode for the SMSC phy.
10 default: enable energy detect mode
13 smsc phy with disabled energy detect mode on an am335x based board.
21 smsc,disable-energy-detect;
|
| /Linux-v5.4/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 | 15 sched-energy
|
| /Linux-v5.4/arch/x86/events/intel/ |
| D | rapl.c | 398 RAPL_EVENT_ATTR_STR(energy-cores, rapl_cores, "event=0x01");
399 RAPL_EVENT_ATTR_STR(energy-pkg , rapl_pkg, "event=0x02");
400 RAPL_EVENT_ATTR_STR(energy-ram , rapl_ram, "event=0x03");
401 RAPL_EVENT_ATTR_STR(energy-gpu , rapl_gpu, "event=0x04");
402 RAPL_EVENT_ATTR_STR(energy-psys, rapl_psys, "event=0x05");
404 RAPL_EVENT_ATTR_STR(energy-cores.unit, rapl_cores_unit, "Joules");
405 RAPL_EVENT_ATTR_STR(energy-pkg.unit , rapl_pkg_unit, "Joules");
406 RAPL_EVENT_ATTR_STR(energy-ram.unit , rapl_ram_unit, "Joules");
407 RAPL_EVENT_ATTR_STR(energy-gpu.unit , rapl_gpu_unit, "Joules");
408 RAPL_EVENT_ATTR_STR(energy-psys.unit, rapl_psys_unit, "Joules");
[all …]
|
| /Linux-v5.4/Documentation/devicetree/bindings/hwmon/ |
| D | vexpress.txt | 10 "arm,vexpress-energy"
19 energy@0 {
20 compatible = "arm,vexpress-energy";
|
| /Linux-v5.4/Documentation/hwmon/ |
| 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-v5.4/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
|
| /Linux-v5.4/Documentation/devicetree/bindings/arm/ |
| D | idle-states.txt | 43 timing and energy related properties, that underline the HW behaviour
73 IDLE: This is the actual energy-saving idle period. This may last
116 expressed in time units but must factor in energy consumption coefficients.
118 The energy consumption of a cpu when it enters a power state can be roughly
145 and denotes the energy costs incurred while entering and leaving the idle
148 shallower slope and essentially represents the energy consumption of the idle
153 which choosing that state become the most energy efficient option. A good
155 states energy consumptions plots.
179 |IDLE1-energy < IDLE2-energy | IDLE2-energy < IDLE1-energy
185 In graph 2 above, that takes into account idle states entry/exit energy
[all …]
|
| 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";
|
| /Linux-v5.4/Documentation/power/ |
| D | energy-model.rst | 10 subsystems willing to use that information to make energy-aware decisions.
88 Subsystems interested in the energy model of a CPU can retrieve it using the
89 em_cpu_get() API. The energy model tables are allocated once upon creation of
92 The energy consumed by a performance domain can be estimated using the
|
| D | index.rst | 14 energy-model
|
| /Linux-v5.4/Documentation/devicetree/bindings/power/supply/ |
| D | battery.txt | 20 - energy-full-design-microwatt-hours: battery design energy
53 energy-full-design-microwatt-hours = <5290000>;
|
| D | bq27xxx.txt | 37 + energy-full-design-microwatt-hours
48 energy-full-design-microwatt-hours = <5290000>;
|
| /Linux-v5.4/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
|
| /Linux-v5.4/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";
|
| /Linux-v5.4/Documentation/power/powercap/ |
| D | powercap.rst | 154 the zones and subzones contain energy monitoring attributes (energy_uj,
192 Current energy counter in micro joules. Write "0" to reset.
196 Range of the above energy counter in micro-joules.
207 It is possible that some domains have both power ranges and energy counter ranges;
|
| /Linux-v5.4/drivers/net/wireless/intel/iwlwifi/mvm/ |
| D | rx.c | 703 u8 *energy; in iwl_mvm_handle_rx_statistics() local
779 energy = (void *)&v11->load_stats.avg_energy; in iwl_mvm_handle_rx_statistics()
785 energy = (void *)&stats->load_stats.avg_energy; in iwl_mvm_handle_rx_statistics()
794 if (!energy[i]) in iwl_mvm_handle_rx_statistics()
800 sta->avg_energy = energy[i]; in iwl_mvm_handle_rx_statistics()
|
| /Linux-v5.4/kernel/rcu/ |
| D | Kconfig | 121 scheduling-clock interrupts for energy-efficiency reasons will
153 parameter), thus improving energy efficiency. On the other
157 Say Y if energy efficiency is critically important, and you
196 callback invocation to energy-efficient CPUs in battery-powered
|
| /Linux-v5.4/include/linux/power/ |
| D | bq27xxx_battery.h | 51 int energy; member
|
| /Linux-v5.4/drivers/staging/iio/meter/ |
| D | Kconfig | 5 menu "Active energy metering IC"
|
| /Linux-v5.4/Documentation/devicetree/bindings/iio/temperature/ |
| D | mlx90632.txt | 16 Since measured object emissivity effects Infra Red energy emitted, emissivity
|
| /Linux-v5.4/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
|
| D | sleep-states.rst | 32 referred to as S2I or S2Idle). It allows more energy to be saved relative to
52 This state, if supported, offers moderate, but real, energy savings, while
61 allow more energy to be saved relative to :ref:`suspend-to-idle <s2idle>`, but
79 energy savings as everything in the system is put into a low-power state, except
113 energy savings and can be used even in the absence of low-level platform support
|
| /Linux-v5.4/drivers/hwmon/ |
| D | ibmaem.c | 159 u64 energy[AEM_NUM_ENERGY_REGS]; member
430 &data->energy[which], 8); in update_aem_energy_one()
835 before = data->energy[attr->index]; in aem_show_power()
847 after = data->energy[attr->index]; in aem_show_power()
868 (unsigned long long)a->energy[attr->index] * 1000); in aem_show_energy()
|
