| /linux-4.1.27/Documentation/devicetree/bindings/hwmon/ |
| D | vexpress.txt | 10 "arm,vexpress-energy"
19 energy@0 {
20 compatible = "arm,vexpress-energy";
|
| /linux-4.1.27/arch/x86/kernel/cpu/ |
| D | perf_event_intel_rapl.c | 424 RAPL_EVENT_ATTR_STR(energy-cores, rapl_cores, "event=0x01");
425 RAPL_EVENT_ATTR_STR(energy-pkg , rapl_pkg, "event=0x02");
426 RAPL_EVENT_ATTR_STR(energy-ram , rapl_ram, "event=0x03");
427 RAPL_EVENT_ATTR_STR(energy-gpu , rapl_gpu, "event=0x04");
429 RAPL_EVENT_ATTR_STR(energy-cores.unit, rapl_cores_unit, "Joules");
430 RAPL_EVENT_ATTR_STR(energy-pkg.unit , rapl_pkg_unit, "Joules");
431 RAPL_EVENT_ATTR_STR(energy-ram.unit , rapl_ram_unit, "Joules");
432 RAPL_EVENT_ATTR_STR(energy-gpu.unit , rapl_gpu_unit, "Joules");
437 RAPL_EVENT_ATTR_STR(energy-cores.scale, rapl_cores_scale, "2.3283064365386962890625e-10");
438 RAPL_EVENT_ATTR_STR(energy-pkg.scale, rapl_pkg_scale, "2.3283064365386962890625e-10");
[all …]
|
| /linux-4.1.27/Documentation/hwmon/ |
| D | ibmaem | 20 This driver implements sensor reading support for the energy and power meters
25 The v1 AEM interface has a simple set of features to monitor energy use. There
26 is a register that displays an estimate of raw energy consumption since the
31 range of energy and power use registers, the power cap as set by the AEM
|
| D | vexpress | 26 temperature and power usage. Some of them also calculate consumed energy
|
| D | sysfs-interface | 574 energy[1-*]_input Cumulative energy use
|
| /linux-4.1.27/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 whilst 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-4.1.27/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-4.1.27/arch/arm/boot/dts/ |
| D | vexpress-v2p-ca15_a7.dts | 347 energy@0 {
348 /* Total energy for the two A15 cores */
349 compatible = "arm,vexpress-energy";
354 energy@2 {
355 /* Total energy for the three A7 cores */
356 compatible = "arm,vexpress-energy";
|
| D | vexpress-v2p-ca15-tc1.dts | 215 energy@0 {
216 /* Total energy */
217 compatible = "arm,vexpress-energy";
|
| /linux-4.1.27/Documentation/power/powercap/ |
| D | powercap.txt | 152 the zones and subzones contain energy monitoring attributes (energy_uj,
185 energy_uj (rw): Current energy counter in micro joules. Write "0" to reset.
188 max_energy_range_uj (ro): Range of the above energy counter in micro-joules.
196 It is possible that some domains have both power ranges and energy counter ranges;
|
| /linux-4.1.27/drivers/hwmon/ |
| D | ibmaem.c | 172 u64 energy[AEM_NUM_ENERGY_REGS]; member
443 &data->energy[which], 8); in update_aem_energy_one()
849 before = data->energy[attr->index]; in aem_show_power()
861 after = data->energy[attr->index]; in aem_show_power()
882 (unsigned long long)a->energy[attr->index] * 1000); in aem_show_energy()
|
| D | Kconfig | 1523 range of information like temperature, power, energy.
|
| /linux-4.1.27/arch/powerpc/platforms/pseries/ |
| D | Kconfig | 52 tristate "pSeries energy management capabilities driver"
56 Provides interface to platform energy management capabilities
|
| /linux-4.1.27/drivers/power/ |
| D | bq27x00_battery.c | 102 int energy; member
489 cache.energy = -ENODATA; in bq27x00_update()
502 cache.energy = bq27x00_battery_read_energy(di); in bq27x00_update()
744 ret = bq27x00_simple_value(di->cache.energy, val); in bq27x00_battery_get_property()
|
| /linux-4.1.27/Documentation/ABI/testing/ |
| D | sysfs-class-powercap | 60 Current energy counter in micro-joules. Write "0" to reset.
69 Range of the above energy counter in micro-joules.
|
| D | sysfs-bus-iio | 1137 This attribute is used to read the energy value reported by the
1138 device (e.g.: human activity sensors report energy burnt by the
|
| /linux-4.1.27/Documentation/power/ |
| D | power_supply_class.txt | 61 ~ Because both "charge" (µAh) and "energy" (µWh) represents "capacity" ~
111 ENERGY_FULL_DESIGN, ENERGY_EMPTY_DESIGN - same as above but for energy.
139 ENERGY_FULL, ENERGY_EMPTY - same as above but for energy.
|
| D | states.txt | 32 It allows more energy to be saved relative to runtime idle by freezing user
54 state. For this reason, it should allow more energy to be saved relative to
|
| D | pm_qos_interface.txt | 191 to energy-saving operation modes on the fly. In those systems, if the operation
192 mode chosen by the hardware attempts to save energy in an overly aggressive way,
|
| D | swsusp.txt | 78 save ourselves the time machine goes down and later boots up, energy costs
|
| D | runtime_pm.txt | 794 Changing a device's power state isn't free; it requires both time and energy.
|
| D | pci.txt | 27 In general, power management is a feature allowing one to save energy by putting
|
| /linux-4.1.27/kernel/time/ |
| D | Kconfig | 85 This is usually interesting for energy saving.
163 large a concern as is energy efficiency. The sysidle subsystem
|
| /linux-4.1.27/drivers/staging/iio/meter/ |
| D | Kconfig | 4 menu "Active energy metering IC"
|
| /linux-4.1.27/drivers/net/wireless/iwlwifi/mvm/ |
| D | fw-api-scan.h | 838 u8 energy; member
|
| /linux-4.1.27/Documentation/networking/ |
| D | ieee802154.txt | 132 taking into account limited bandwidth, memory, or energy resources that are
|
| /linux-4.1.27/drivers/powercap/ |
| D | intel_rapl.c | 309 static int get_max_energy_counter(struct powercap_zone *pcd_dev, u64 *energy) in get_max_energy_counter() argument
313 *energy = rapl_unit_xlate(rd, 0, ENERGY_UNIT, ENERGY_STATUS_MASK, 0); in get_max_energy_counter()
|
| /linux-4.1.27/init/ |
| D | Kconfig | 607 scheduling-clock interrupts for energy-efficiency reasons will
647 parameter), thus improving energy efficiency. On the other
651 Say Y if energy efficiency is critically important, and you
727 callback invocation to energy-efficient CPUs in battery-powered
777 or energy-efficiency reasons, but the real reason it exists
792 or energy-efficiency reasons.
|
| /linux-4.1.27/kernel/power/ |
| D | Kconfig | 136 Enable functionality allowing I/O devices to be put into energy-saving
|
| /linux-4.1.27/drivers/net/wireless/brcm80211/brcmsmac/phy/ |
| D | phy_int.h | 359 u16 energy; member
|
| /linux-4.1.27/Documentation/timers/ |
| D | NO_HZ.txt | 5 reduce the number of scheduling-clock interrupts, thereby improving energy
|
| /linux-4.1.27/Documentation/usb/ |
| D | power-management.txt | 31 Power Management (PM) is the practice of saving energy by suspending
|
| /linux-4.1.27/Documentation/ |
| D | SubmittingPatches | 460 counter-productive waste of time and energy. Rule (b) allows you to adjust
|
| D | kernel-parameters.txt | 2991 real-time workloads. It can also improve energy
3002 energy efficiency by requiring that the kthreads
3184 real-time latency, and degrade energy efficiency.
|