Changes in Makefile

9eef7f9d - powercap: intel_rapl: Introduce RAPL TPMI interface driver

Wed, 19 Apr 2023 02:44:19 +0000

powercap: intel_rapl: Introduce RAPL TPMI interface driverThe TPMI (Topology Aware Register and PM Capsule Interface) provides aflexible, extendable and PCIe enumerable MMIO interface for PM features.Intel RAPL (Running Average Power Limit) is one of the features thatbenefit from this. Using TPMI Interface has advantage over traditional MSR(Model Specific Register) interface, where a thread needs to be scheduledon the target CPU to read or write. Also the RAPL features vary betweenCPU models, and hence lot of model specific code. Here TPMI provides anarchitectural interface by providing hierarchical tables and fields,which will not need any model specific implementation.TPMI interface uses a PCI VSEC structure to expose the location of MMIOinterface for PM feature enumeration and control.The Intel VSEC driver parses VSEC structures present in the PCIconfiguration space of the given device and creates an auxiliary deviceobject for each of them. In particular, it creates an auxiliary deviceobject representing TPMI that can be bound to by an auxiliary driver.Then the TPMI enumeration driver binds to the TPMI auxiliary deviceobject created by the Intel VSEC driver, parses the PM Feature Structure(PFS) present in the TPMI MMIO region and creates device nodes for PMfeatures described in the PFS.This RAPL TPMI Interface driver binds the RAPL auxiliary device createdby the TPMI enumeration driver and expose the RAPL control to userspacevia powercap sysfs class.RAPL TPMI details are published in the following document:https://github.com/intel/tpmi_power_management/blob/main/RAPL_TPMI_public_disclosure_FINAL.docxNote, for now, the RAPL TPMI Interface and RAPL MSR Interface cannotco-exists on the same platform (RAPL TPMI Interface is not supported onany platforms in the CPU model list for RAPL MSR Interface). Thusregister the RAPL TPMI powercap control type with name "intel-rapl",the same as RAPL MSR Interface, so that it is transparent to userspace.Signed-off-by: Zhang Rui Tested-by: Wang Wendy Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/powercap/Makefile

b55eef52 - powercap: arm_scmi: Add SCMI Powercap based driver

Thu, 13 Oct 2022 17:46:12 +0000

powercap: arm_scmi: Add SCMI Powercap based driverAdd a powercap driver that, using the ARM SCMI Protocol to query the SCMIplatform firmware for the list of existing Powercap domains, registers allof such discovered domains under the new 'arm-scmi' powercap control type.A new simple powercap zone and constraint is registered for all the SCMIpowercap zones that are found.Reviewed-by: Lukasz Luba Signed-off-by: Cristian Marussi Acked-by: Sudeep Holla Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/powercap/Makefile

e4465561 - powercap/drivers/dtpm: Add dtpm devfreq with energy model support

Fri, 28 Jan 2022 16:35:36 +0000

powercap/drivers/dtpm: Add dtpm devfreq with energy model supportCurrently the dtpm supports the CPUs via cpufreq and the energymodel. This change provides the same for the device which supportsdevfreq.Each device supporting devfreq and having an energy model can be addedto the hierarchy.The concept is the same as the cpufreq DTPM support: the QoS is usedto aggregate the requests and the energy model gives the value of theinstantaneous power consumption ponderated by the load of the device.Cc: Chanwoo Choi Cc: Lukasz Luba Cc: Kyungmin Park Cc: MyungJoo Ham Signed-off-by: Daniel Lezcano Link: https://lore.kernel.org/r/20220128163537.212248-5-daniel.lezcano@linaro.org List of files: /linux-6.15/drivers/powercap/Makefile

0e8f68d7 - powercap/drivers/dtpm: Add CPU energy model based support

Tue, 08 Dec 2020 16:41:45 +0000

powercap/drivers/dtpm: Add CPU energy model based supportWith the powercap dtpm controller, we are able to plug devices withpower limitation features in the tree.The following patch introduces the CPU power limitation based on theenergy model and the performance states.The power limitation is done at the performance domain level. If someCPUs are unplugged, the corresponding power will be subtracted fromthe performance domain total power.It is up to the platform to initialize the dtpm tree and add the CPU.Here is an example to create a simple tree with one root node called"pkg" and the CPU's performance domains.static int dtpm_register_pkg(struct dtpm_descr *descr){ struct dtpm *pkg; int ret; pkg = dtpm_alloc(NULL); if (!pkg) return -ENOMEM; ret = dtpm_register(descr->name, pkg, descr->parent); if (ret) return ret; return dtpm_register_cpu(pkg);}static struct dtpm_descr descr = { .name = "pkg", .init = dtpm_register_pkg,};DTPM_DECLARE(descr);Signed-off-by: Daniel Lezcano Reviewed-by: Lukasz Luba Tested-by: Lukasz Luba Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/powercap/Makefile

a20d0ef9 - powercap/drivers/dtpm: Add API for dynamic thermal power management

Tue, 08 Dec 2020 16:41:44 +0000

powercap/drivers/dtpm: Add API for dynamic thermal power managementOn the embedded world, the complexity of the SoC leads to anincreasing number of hotspots which need to be monitored and mitigatedas a whole in order to prevent the temperature to go above thenormative and legally stated 'skin temperature'.Another aspect is to sustain the performance for a given power budget,for example virtual reality where the user can feel dizziness if theGPU performance is capped while a big CPU is processing somethingelse. Or reduce the battery charging because the dissipated power istoo high compared with the power consumed by other devices.The userspace is the most adequate place to dynamically act on thedifferent devices by limiting their power given an applicationprofile: it has the knowledge of the platform.These userspace daemons are in charge of the Dynamic Thermal PowerManagement (DTPM).Nowadays, the dtpm daemons are abusing the thermal framework as theyact on the cooling device state to force a specific and arbitrarystate without taking care of the governor decisions. Given the closedloop of some governors that can confuse the logic or directly enter ina decision conflict.As the number of cooling device support is limited today to the CPUand the GPU, the dtpm daemons have little control on the powerdissipation of the system. The out of tree solutions are hackingaround here and there in the drivers, in the frameworks to havecontrol on the devices. The common solution is to declare them ascooling devices.There is no unification of the power limitation unit, opaque statesare used.This patch provides a way to create a hierarchy of constraints usingthe powercap framework. The devices which are registered as powerlimit-able devices are represented in this hierarchy as a tree. Theyare linked together with intermediate nodes which are just there topropagate the constraint to the children.The leaves of the tree are the real devices, the intermediate nodesare virtual, aggregating the children constraints and powercharacteristics.Each node have a weight on a 2^10 basis, in order to reflect thepercentage of power distribution of the children's node. Thispercentage is used to dispatch the power limit to the children.The weight is computed against the max power of the siblings.This simple approach allows to do a fair distribution of the powerlimit.Signed-off-by: Daniel Lezcano Reviewed-by: Lukasz Luba Tested-by: Lukasz Luba Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/powercap/Makefile

3382388d - intel_rapl: abstract RAPL common code

Wed, 10 Jul 2019 13:44:30 +0000

intel_rapl: abstract RAPL common codeSplit intel_rapl.c to intel_rapl_common.c and intel_rapl_msr.c, whereintel_rapl_common.c contains the common code that can be used by both MSRand MMIO interface.intel_rapl_msr.c contains the implementation of RAPL MSR interface.Reviewed-by: Pandruvada, Srinivas Tested-by: Pandruvada, Srinivas Signed-off-by: Zhang Rui Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/powercap/Makefile

ec8f24b7 - treewide: Add SPDX license identifier - Makefile/Kconfig

Sun, 19 May 2019 12:07:45 +0000

treewide: Add SPDX license identifier - Makefile/KconfigAdd SPDX license identifiers to all Make/Kconfig files which: - Have no license information of any formThese files fall under the project license, GPL v2 only. The resulting SPDXlicense identifier is: GPL-2.0-onlySigned-off-by: Thomas Gleixner Signed-off-by: Greg Kroah-Hartman List of files: /linux-6.15/drivers/powercap/Makefile

88763a5c - powercap / idle_inject: Add an idle injection framework

Tue, 26 Jun 2018 10:53:29 +0000

powercap / idle_inject: Add an idle injection frameworkInitially, the cpu_cooling device for ARM was changed by adding a newpolicy inserting idle cycles. The intel_powerclamp driver does asimilar action.Instead of implementing idle injections privately in the cpu_coolingdevice, move the idle injection code in a dedicated framework and givethe opportunity to other frameworks to make use of it.The framework relies on the smpboot kthreads which handles via itsmain loop the common code for hotplugging and [un]parking.This code was previously tested with the cpu cooling device and wentthrough several iterations. It results now in split code and APIexported in the header file. It was tested with the cpu cooling devicewith success.Signed-off-by: Daniel Lezcano Reviewed-by: Viresh Kumar [ rjw: Rewrite of all comments ]Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/powercap/Makefile

2d281d81 - PowerCap: Introduce Intel RAPL power capping driver

Thu, 17 Oct 2013 17:28:35 +0000

PowerCap: Introduce Intel RAPL power capping driverThe Intel Running Average Power Limit (RAPL) technology provides platformsoftware with the ability to monitor, control, and get notifications onpower usage.This feature is present in all Sandy Bridge and later Intel processors.Newer models allow more fine grained controls to be applied. In RAPL,power control is divided into domains, which include package, DRAMcontroller, CPU core (Power Plane 0), graphics uncore (power plane 1), etc.The purpose of this driver is to expose the RAPL settings to userspace.Overall, RAPL fits in the new powercap class driver in that platformlevel power capping controls are exposed via this generic interface.This driver is based on an earlier patch from Zhang Rui.However, while the previous work was mainly focused on thermal monitoringthe focus here is on the usability from user space perspective.References: https://lkml.org/lkml/2011/5/26/93Signed-off-by: Srinivas Pandruvada Signed-off-by: Jacob Pan Reviewed-by: Rafael J. Wysocki Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/powercap/Makefile

75d2364e - PowerCap: Add class driver

Fri, 11 Oct 2013 23:54:56 +0000

PowerCap: Add class driverThe power capping framework providing a consistent interface between thekernel and user space that allows power capping drivers to expose theirsettings to user space in a uniform way.The overall design of the framework is described in the documentationadded by the previous patch in this series.Signed-off-by: Srinivas Pandruvada Signed-off-by: Jacob Pan Reviewed-by: Rafael J. Wysocki Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/powercap/Makefile