| /linux/Documentation/scheduler/ |
| 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 …]
|
| A D | index.rst | 16 sched-energy
|
| /linux/Documentation/devicetree/bindings/net/ |
| 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;
|
| A D | ethernet-phy.yaml | 105 Mark the corresponding energy efficient ethernet mode as
111 Mark the corresponding energy efficient ethernet mode as
117 Mark the corresponding energy efficient ethernet mode as
123 Mark the corresponding energy efficient ethernet mode as
129 Mark the corresponding energy efficient ethernet mode as
135 Mark the corresponding energy efficient ethernet mode as
|
| /linux/arch/x86/events/ |
| 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 …]
|
| /linux/Documentation/hwmon/ |
| 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)
|
| 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
|
| /linux/Documentation/devicetree/bindings/hwmon/ |
| A D | vexpress.txt | 10 "arm,vexpress-energy"
19 energy@0 {
20 compatible = "arm,vexpress-energy";
|
| 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
|
| /linux/Documentation/devicetree/bindings/arm/ |
| A D | idle-states.yaml | 51 timing and energy related properties, that underline the HW behaviour
81 IDLE: This is the actual energy-saving idle period. This may last
124 expressed in time units but must factor in energy consumption coefficients.
126 The energy consumption of a cpu when it enters a power state can be roughly
153 and denotes the energy costs incurred while entering and leaving the idle
161 which choosing that state become the most energy efficient option. A good
163 states energy consumptions plots.
187 |IDLE1-energy < IDLE2-energy | IDLE2-energy < IDLE1-energy
193 In graph 2 above, that takes into account idle states entry/exit energy
201 However, the lower power consumption (i.e. shallower energy curve slope) of
[all …]
|
| A 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/Documentation/power/ |
| 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 milli-Joules would not be possible.
132 There are two API functions which provide the access to the energy model:
138 Subsystems interested in the energy model of a CPU can retrieve it using the
139 em_cpu_get() API. The energy model tables are allocated once upon creation of
142 The energy consumed by a performance domain can be estimated using the
|
| A D | index.rst | 14 energy-model
|
| /linux/arch/arm/boot/dts/ |
| A 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";
|
| A D | vexpress-v2p-ca15-tc1.dts | 231 energy {
232 /* Total energy */
233 compatible = "arm,vexpress-energy";
|
| /linux/drivers/net/wireless/intel/iwlwifi/mvm/ |
| A D | rx.c | 650 u8 *energy = _data; in iwl_mvm_stats_energy_iter() local
657 if (energy[sta_id]) in iwl_mvm_stats_energy_iter()
658 mvmsta->avg_energy = energy[sta_id]; in iwl_mvm_stats_energy_iter()
761 u8 *energy; in iwl_mvm_handle_rx_statistics() local
842 energy = (void *)&v11->load_stats.avg_energy; in iwl_mvm_handle_rx_statistics()
848 energy = (void *)&stats->load_stats.avg_energy; in iwl_mvm_handle_rx_statistics()
853 energy); in iwl_mvm_handle_rx_statistics()
|
| /linux/Documentation/devicetree/bindings/power/supply/ |
| A D | bq27xxx.yaml | 65 - energy-full-design-microwatt-hours
86 energy-full-design-microwatt-hours = <5290000>;
|
| A D | battery.yaml | 60 energy-full-design-microwatt-hours:
61 description: battery design energy
149 energy-full-design-microwatt-hours = <5290000>;
|
| /linux/drivers/powercap/ |
| A D | Kconfig | 54 bool "Add CPU power capping based on the energy model"
58 energy model.
|
| /linux/Documentation/power/powercap/ |
| A 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/drivers/hwmon/ |
| A 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()
|
| /linux/kernel/rcu/ |
| A 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
|
| /linux/include/linux/power/ |
| A D | bq27xxx_battery.h | 55 int energy; member
|
| /linux/Documentation/admin-guide/pm/ |
| A 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/Documentation/devicetree/bindings/mfd/ |
| A D | ene-kb930.yaml | 40 energy-full-design-microwatt-hours = <24000000>;
|