summaryrefslogtreecommitdiffstats
path: root/lib/Kconfig.kasan
diff options
context:
space:
mode:
authorLukasz Luba <lukasz.luba@arm.com>2020-11-03 09:05:58 +0000
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2020-11-10 20:29:28 +0100
commit5a64f775691647c242aa40d34f3512e7b179a921 (patch)
tree469e6eeb2e64d129f0b2242084875081e65ef4ab /lib/Kconfig.kasan
parentc250d50fe2ce627ca9805d9c8ac11cbbf922a4a6 (diff)
downloadlinux-5a64f775691647c242aa40d34f3512e7b179a921.tar.gz
linux-5a64f775691647c242aa40d34f3512e7b179a921.tar.bz2
linux-5a64f775691647c242aa40d34f3512e7b179a921.zip
PM: EM: Clarify abstract scale usage for power values in Energy Model
The Energy Model (EM) can store power values in milli-Watts or in abstract scale. This might cause issues in the subsystems which use the EM for estimating the device power, such as: - mixing of different scales in a subsystem which uses multiple (cooling) devices (e.g. thermal Intelligent Power Allocation (IPA)) - assuming that energy [milli-Joules] can be derived from the EM power values which might not be possible since the power scale doesn't have to be in milli-Watts To avoid misconfiguration add the requisite documentation to the EM and related subsystems: EAS and IPA. Signed-off-by: Lukasz Luba <lukasz.luba@arm.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'lib/Kconfig.kasan')
0 files changed, 0 insertions, 0 deletions