aboutsummaryrefslogtreecommitdiff
path: root/Documentation/PCI
diff options
context:
space:
mode:
authorGravatar Lukasz Luba <lukasz.luba@arm.com> 2021-11-02 18:01:44 +0000
committerGravatar Rafael J. Wysocki <rafael.j.wysocki@intel.com> 2021-11-10 21:26:34 +0100
commit08374410a5ea3ff2fa9a87edd7d7ab15375b1c31 (patch)
tree3b6144cef691cdaf40c76f671a8ba90585dcbe3b /Documentation/PCI
parentDocumentation: power: Add description about new callback for EM registration (diff)
downloadlinux-08374410a5ea3ff2fa9a87edd7d7ab15375b1c31.tar.gz
linux-08374410a5ea3ff2fa9a87edd7d7ab15375b1c31.tar.bz2
linux-08374410a5ea3ff2fa9a87edd7d7ab15375b1c31.zip
Documentation: power: Describe 'advanced' and 'simple' EM models
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>
Diffstat (limited to 'Documentation/PCI')
0 files changed, 0 insertions, 0 deletions