summaryrefslogtreecommitdiffstats
path: root/lib/fdt.c
diff options
context:
space:
mode:
authorSrinivas Pandruvada <srinivas.pandruvada@linux.intel.com>2022-01-27 11:34:54 -0800
committerRafael J. Wysocki <rafael.j.wysocki@intel.com>2022-02-03 19:50:49 +0100
commitbd30cdfd9bd73b68e4977ce7c5540aa7b14c25cd (patch)
tree543219e79331a3edbc9b9f007331b2556d4f2209 /lib/fdt.c
parente4b1eb24ce5a696ef7229f9926ff34d7502f0582 (diff)
downloadlinux-bd30cdfd9bd73b68e4977ce7c5540aa7b14c25cd.tar.bz2
thermal: intel: hfi: Notify user space for HFI events
When the hardware issues an HFI event, relay a notification to user space. This allows user space to respond by reading performance and efficiency of each CPU and take appropriate action. For example, when the performance and efficiency of a CPU is 0, user space can either offline the CPU or inject idle. Also, if user space notices a downward trend in performance, it may proactively adjust power limits to avoid future situations in which performance drops to 0. To avoid excessive notifications, the rate is limited by one HZ per event. To limit the netlink message size, send parameters for up to 16 CPUs in a single message. If there are more than 16 CPUs, issue as many messages as needed to notify the status of all CPUs. In the HFI specification, both performance and efficiency capabilities are defined in the [0, 255] range. The existing implementations of HFI hardware do not scale the maximum values to 255. Since userspace cares about capability values that are either 0 or show a downward/upward trend, this fact does not matter much. Relative changes in capabilities are enough. To comply with the thermal netlink ABI, scale both performance and efficiency capabilities to the [0, 1023] interval. Reviewed-by: Len Brown <len.brown@intel.com> Signed-off-by: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com> Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'lib/fdt.c')
0 files changed, 0 insertions, 0 deletions