08374410a5
The Energy Model (EM) can be registered in two ways:
1) Using a helper function, which under the hood relies on OPP framework
and DT entry in CPU node: 'dynamic-power-coefficient'. This is
a 'simple' EM because it's tied to the math formula:
Power = dynamic-power-coefficient * V^2 * f
2) Using em_dev_register_perf_domain() API function with a driver
custom callback which provides power for each performance state.
This is 'advanced' EM, since it can better reflect real power
measurements for each performance state. It's not limited to any
math formula and can better reflect real physics of the device.
Add description of these two methods to the documentation, so developers
could choose the suitable registration method (option).
Signed-off-by: Lukasz Luba <lukasz.luba@arm.com>
[ rjw: Changelog edits ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
|
||
|---|---|---|
| .. | ||
| powercap | ||
| regulator | ||
| apm-acpi.rst | ||
| basic-pm-debugging.rst | ||
| charger-manager.rst | ||
| drivers-testing.rst | ||
| energy-model.rst | ||
| freezing-of-tasks.rst | ||
| index.rst | ||
| opp.rst | ||
| pci.rst | ||
| pm_qos_interface.rst | ||
| power_supply_class.rst | ||
| runtime_pm.rst | ||
| s2ram.rst | ||
| suspend-and-cpuhotplug.rst | ||
| suspend-and-interrupts.rst | ||
| swsusp-and-swap-files.rst | ||
| swsusp-dmcrypt.rst | ||
| swsusp.rst | ||
| tricks.rst | ||
| userland-swsusp.rst | ||
| video.rst | ||