| /kernel/linux/linux-5.10/Documentation/hwmon/ |
| D | amd_energy.rst | 29 The Energy driver exposes the energy counters that are
34 1. Power, Energy and Time Units
38 2. Energy consumed by each Core
42 3. Energy consumed by Socket
51 Since, the energy status registers are accessed at core level,
53 in duplicate values. Hence, energy counter entries are not
56 Energy Caluclation
59 Energy information (in Joules) is based on the multiplier,
62 indicating energy status unit is 15.3 micro-Joules increment.
71 Energy accumulation
[all …]
|
| D | ibmaem.rst | 4 This driver talks to the IBM Systems Director Active Energy Manager, known
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 | 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)
|
| /kernel/linux/linux-6.6/Documentation/scheduler/ |
| D | sched-energy.rst | 2 Energy Aware Scheduling
8 Energy Aware Scheduling (or EAS) gives the scheduler the ability to predict
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]
[all …]
|
| /kernel/linux/linux-5.10/Documentation/scheduler/ |
| D | sched-energy.rst | 2 Energy Aware Scheduling
8 Energy Aware Scheduling (or EAS) gives the scheduler the ability to predict
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]
[all …]
|
| /kernel/linux/linux-6.6/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.
14 Description: Energy, frequency attributes directory for POWERVM servers
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>
|
| /kernel/linux/linux-6.6/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/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/include/linux/ |
| D | energy_model.h | 20 * energy calculation. Equal to: power * max_frequency / frequency
34 * misses during energy calculations in the scheduler
55 * Increase resolution of energy estimation calculations for 64-bit
57 * task placement when two Performance Domains might provide similar energy
102 * em_cpu_energy() - Estimates the energy consumed by the CPUs of a
104 * @pd : performance domain for which energy has to be estimated
112 * Return: the sum of the energy consumed by the CPUs of the domain assuming
133 * Find the lowest performance state of the Energy Model above the in em_cpu_energy()
151 * the EM), the energy consumed by this CPU at that performance state in em_cpu_energy()
161 * units of power, it can be manipulated as an energy value in em_cpu_energy()
[all …]
|
| /kernel/linux/linux-6.6/net/bluetooth/ |
| D | Kconfig | 31 SMP (Security Manager Protocol) on LE (Low Energy) links
66 bool "Bluetooth Low Energy (LE) features"
70 Bluetooth Low Energy includes support low-energy physical
78 Bluetooth Low Energy L2CAP Enhanced Credit Flow Control available with
88 IPv6 compression over Bluetooth Low Energy.
139 Bluetooth Low Energy Secure Connections feature.
|
| /kernel/linux/linux-6.6/Documentation/hwmon/ |
| D | ibmaem.rst | 4 This driver talks to the IBM Systems Director Active Energy Manager, known
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 | 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)
|
| /kernel/linux/linux-5.10/drivers/isdn/mISDN/ |
| D | dsp_ecdis.h | 61 /* Estimate the overall energy in the channel, and the energy in in echo_can_disable_detector_update()
62 the notch (i.e. overall channel energy - tone energy => noise). in echo_can_disable_detector_update()
64 Damp the overall energy a little more for a stable result. in echo_can_disable_detector_update()
65 Damp the notch energy a little less, so we don't damp out the in echo_can_disable_detector_update()
70 /* There is adequate energy in the channel. in echo_can_disable_detector_update()
|
| /kernel/linux/linux-6.6/drivers/isdn/mISDN/ |
| D | dsp_ecdis.h | 61 /* Estimate the overall energy in the channel, and the energy in in echo_can_disable_detector_update()
62 the notch (i.e. overall channel energy - tone energy => noise). in echo_can_disable_detector_update()
64 Damp the overall energy a little more for a stable result. in echo_can_disable_detector_update()
65 Damp the notch energy a little less, so we don't damp out the in echo_can_disable_detector_update()
70 /* There is adequate energy in the channel. in echo_can_disable_detector_update()
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | energy_model.h | 19 * energy calculation. Equal to: power * max_frequency / frequency
46 * misses during energy calculations in the scheduler
69 * energy consumption.
91 * To avoid possible energy estimation overflow on 32bit machines add
102 * To avoid an overflow on 32bit machines while calculating the energy
208 * em_cpu_energy() - Estimates the energy consumed by the CPUs of a
210 * @pd : performance domain for which energy has to be estimated
220 * Return: the sum of the energy consumed by the CPUs of the domain assuming
251 * Find the lowest performance state of the Energy Model above the in em_cpu_energy()
265 * the EM), the energy consumed by this CPU at that performance state in em_cpu_energy()
[all …]
|
| /kernel/linux/linux-5.10/arch/x86/events/ |
| D | rapl.c | 3 * Support Intel/AMD RAPL energy consumption counters
12 * RAPL provides more controls than just reporting energy consumption
13 * however here we only expose the 3 energy consumption free running
70 * RAPL energy status counters
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");
[all …]
|
| /kernel/linux/linux-6.6/arch/x86/events/ |
| D | rapl.c | 3 * Support Intel/AMD RAPL energy consumption counters
12 * RAPL provides more controls than just reporting energy consumption
13 * however here we only expose the 3 energy consumption free running
70 * RAPL energy status counters
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");
[all …]
|
| /kernel/linux/linux-5.10/net/bluetooth/ |
| D | Kconfig | 31 SMP (Security Manager Protocol) on LE (Low Energy) links
73 bool "Bluetooth Low Energy (LE) features"
77 Bluetooth Low Energy includes support low-energy physical
84 IPv6 compression over Bluetooth Low Energy.
128 Bluetooth Low Energy Secure Connections feature.
|
| /kernel/linux/linux-6.6/Documentation/power/ |
| D | energy-model.rst | 4 Energy Model of devices
10 The Energy Model (EM) framework serves as an interface between drivers knowing
12 subsystems willing to use that information to make energy-aware decisions.
26 can be found in the Energy-Aware Scheduler documentation
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.
51 | Energy Model |
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
[all …]
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | energy-model.rst | 4 Energy Model of devices
10 The Energy Model (EM) framework serves as an interface between drivers knowing
12 subsystems willing to use that information to make energy-aware decisions.
36 | Energy Model |
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
114 performance domain in the Energy Model framework using the (fake) 'foo'
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| 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
149 Graph 1: Energy vs time example
153 and denotes the energy costs incurred while entering and leaving the idle
156 shallower slope and essentially represents the energy consumption of 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
[all …]
|
| /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
98 /* This DSI port only has the Low Power / Energy Save clock */
|
| /kernel/linux/linux-5.10/tools/power/x86/x86_energy_perf_policy/ |
| D | x86_energy_perf_policy.8 | 5 x86_energy_perf_policy \- Manage Energy vs. Performance Policy via x86 Model Specific Registers
21 displays and updates energy-performance policy settings specific to
31 Further, it allows the OS to influence energy/performance trade-offs where there
82 Set a policy with a normal balance between performance and energy efficiency.
84 for potentially significant energy savings.
90 accepting no performance sacrifice for the benefit of energy efficiency.
94 but allowing some performance loss to benefit energy efficiency.
102 a measurable performance impact to maximize energy efficiency.
|
| /kernel/linux/linux-6.6/tools/power/x86/x86_energy_perf_policy/ |
| D | x86_energy_perf_policy.8 | 5 x86_energy_perf_policy \- Manage Energy vs. Performance Policy via x86 Model Specific Registers
21 displays and updates energy-performance policy settings specific to
31 Further, it allows the OS to influence energy/performance trade-offs where there
82 Set a policy with a normal balance between performance and energy efficiency.
84 for potentially significant energy savings.
90 accepting no performance sacrifice for the benefit of energy efficiency.
94 but allowing some performance loss to benefit energy efficiency.
102 a measurable performance impact to maximize energy efficiency.
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/hwmon/ |
| 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
|