Changes in Kconfig

207a792d - thermal: intel: Fix compile issue when CONFIG_NET is not defined

Wed, 18 Dec 2024 21:44:44 +0000

thermal: intel: Fix compile issue when CONFIG_NET is not definedIf CONFIG_NET is not defined then THERMAL_NETLINK can't be selected.Hence add dependency on CONFIG_NET. Othewise it will generate compileerrors while compiling thermal_netlink.c.Fixes: 4596cbea0ed2 ("thermal: intel: Remove explicit user_space governor selection")Reported-by: kernel test robot Signed-off-by: Srinivas Pandruvada Link: https://patch.msgid.link/20241218214444.1904650-1-srinivas.pandruvada@linux.intel.com[ rjw: Merge the "depends on" lines ]Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/thermal/intel/Kconfig

4596cbea - thermal: intel: Remove explicit user_space governor selection

Mon, 16 Dec 2024 19:08:21 +0000

thermal: intel: Remove explicit user_space governor selectionCurrently some user space programs like Linux thermald needs to registerto get notifications from both thermal user space governor and alsoThermal netlink. This is required as some messages like HFI (HardwareFeedback Notifications) requires Thermal netlink.This results in additional processing in kernel and user space to processboth notifications. The cost of using user space governor usingkobject_uevent is much higher as this is also used by other user spacedaemons like udev daemon.Do not select user_space thermal governor by default. If it is presentuser space programs can always use this governor by writing to"policy" attribute.Instead from the kernel select THERMAL_NETLINK. Trip temperatureviolation can be received by user space programs via thermal netlinkevents:THERMAL_GENL_EVENT_TZ_TRIP_UPTHERMAL_GENL_EVENT_TZ_TRIP_DOWNSigned-off-by: Srinivas Pandruvada Link: https://patch.msgid.link/20241216190821.1137162-1-srinivas.pandruvada@linux.intel.comSigned-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/thermal/intel/Kconfig

a85739c8 - thermal: Get rid of CONFIG_THERMAL_WRITABLE_TRIPS

Mon, 12 Feb 2024 18:26:25 +0000

thermal: Get rid of CONFIG_THERMAL_WRITABLE_TRIPSThe only difference made by CONFIG_THERMAL_WRITABLE_TRIPS is whether ornot the writable trips mask passed during thermal zone registrationwill take any effect, but whoever passes a non-zero writable trips maskto thermal_zone_device_register_with_trips() can be forgiven thinkingthat it will always work.Moreover, some thermal drivers expect user space to set trip temperaturevalues, so they select CONFIG_THERMAL_WRITABLE_TRIPS, possibly overridinga manual choice to unset it and going against the design purportedlyallowing system integrators to decide on the writability of trip pointsfor the given kernel build. It is also set in one platform's defconfig.Forthermore, CONFIG_THERMAL_WRITABLE_TRIPS only affects trip temperature,because trip hysteresis is writable as long as the thermal zone providesa callback to update it, regardless of the CONFIG_THERMAL_WRITABLE_TRIPSvalue.The above means that the symbol in question is used inconsistently andits purpose is at least moot, so remove it and always take the writabletrip mask passed to thermal_zone_device_register_with_trips() intoaccount.Signed-off-by: Rafael J. Wysocki Reviewed-by: Daniel Lezcano List of files: /linux-6.15/drivers/thermal/intel/Kconfig

f4750798 - thermal: ACPI: Move the ACPI thermal library to drivers/acpi/

Tue, 17 Oct 2023 20:05:23 +0000

thermal: ACPI: Move the ACPI thermal library to drivers/acpi/The ACPI thermal library contains functions that can be used toretrieve trip point temperature values through the platform firmwarefor various types of trip points. Each of these functions basicallyevaluates a specific ACPI object, checks if the value produced by itis reasonable and returns it (or THERMAL_TEMP_INVALID if anythingfails).It made sense to hold it in drivers/thermal/ so long as it was only usedby the code in that directory, but since it is also going to be used bythe ACPI thermal driver located in drivers/acpi/, move it to the latterin order to keep the code related to evaluating ACPI objects defined inthe specification proper together.No intentional functional impact.Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/thermal/intel/Kconfig

2b6a7409 - thermal: intel: menlow: Get rid of this driver

Wed, 26 Apr 2023 16:46:05 +0000

thermal: intel: menlow: Get rid of this driverAccording to my information, there are no active users of this driver inthe field.Moreover, it does some really questionable things and gets in the way ofthermal core improvements, so drop it.Signed-off-by: Rafael J. Wysocki Acked-by: Daniel Lezcano List of files: /linux-6.15/drivers/thermal/intel/Kconfig

1467fb96 - thermal: intel: BXT_PMIC: select REGMAP instead of depending on it

Sun, 26 Feb 2023 05:39:52 +0000

thermal: intel: BXT_PMIC: select REGMAP instead of depending on itREGMAP is a hidden (not user visible) symbol. Users cannot set itdirectly thru "make *config", so drivers should select it instead ofdepending on it if they need it.Consistently using "select" or "depends on" can also help reduceKconfig circular dependency issues.Therefore, change the use of "depends on REGMAP" to "select REGMAP".Fixes: b474303ffd57 ("thermal: add Intel BXT WhiskeyCove PMIC thermal driver")Signed-off-by: Randy Dunlap Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/thermal/intel/Kconfig

8526eb7f - thermal: intel: powerclamp: Use powercap idle-inject feature

Wed, 01 Feb 2023 18:28:53 +0000

thermal: intel: powerclamp: Use powercap idle-inject featureThere are two idle injection implementation in the Linux kernel. Onevia intel_powerclamp and the other using powercap/idle_inject. Bothimplementation end up in calling play_idle* function from a FIFOpriority thread. Both can't be used at the same time.It is better to use one idle injection framework for bettermaintainability. In this way, there is only one caller for play_idle.Here powercap/idle_inject can be used for both per-core and for systemwide idle injection. This framework has a well defined interface whichallow registry for per-core or for all CPUs (system wide).This reduces code complexity in the intel powerclamp driver as all theper CPU kthreads, delayed work and calls to play_idle can be removed.The changes include: - Remove unneeded include files - Remove per CPU kthread workers: balancing_work and idle_injection_work. - Reuse the compensation related code by moving from previous worker thread to idle_injection callback. - Adjust the idle_duration and runtime by using powercap/idle_inject interface. - Remove all variables, which are not required once powercap/idle_inject is used. - Add mutex to avoid race during removal of idle injection during module unload and user action to change idle inject percent. Also for protection during dynamic adjustment of run and idle time from update() callback. - Remove online/offline callbacks to designate control CPU - Use cpu_present_mask global variable for CPU mask - Remove hot plug locksSigned-off-by: Srinivas Pandruvada Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/thermal/intel/Kconfig

fee19c69 - thermal: intel: intel_pch: Use generic trip points

Mon, 23 Jan 2023 18:40:33 +0000

thermal: intel: intel_pch: Use generic trip pointsThe thermal framework gives the possibility to register the trippoints along with the thermal zone. When that is done, no get_trip_*callbacks are needed and they can be removed.Convert the existing callbacks content logic into generic trip pointsinitialization code and register them along with the thermal zone.In order to consolidate the code, use an ACPI trip library functionto populate a generic trip point.Signed-off-by: Daniel Lezcano Reviewed-by: Zhang Rui [ rjw: Subject and changelog edits, rebase ]Signed-off-by: Rafael J. Wysocki Tested-by: Srinivas Pandruvada List of files: /linux-6.15/drivers/thermal/intel/Kconfig

983eb370 - thermal/x86_pkg_temp_thermal: Use Intel TCC library

Mon, 19 Dec 2022 15:46:19 +0000

thermal/x86_pkg_temp_thermal: Use Intel TCC libraryCleanup the code by using Intel TCC library for TCC (Thermal ControlCircuitry) MSR access.Signed-off-by: Zhang Rui Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/thermal/intel/Kconfig

4e3ecc28 - thermal/intel/intel_tcc_cooling: Use Intel TCC library

Mon, 19 Dec 2022 15:46:18 +0000

thermal/intel/intel_tcc_cooling: Use Intel TCC libraryCleanup the code by using Intel TCC library for TCC (Thermal ControlCircuitry) MSR access.Signed-off-by: Zhang Rui Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/thermal/intel/Kconfig

955fb871 - thermal/intel/intel_soc_dts_iosf: Use Intel TCC library

Mon, 19 Dec 2022 15:46:17 +0000

thermal/intel/intel_soc_dts_iosf: Use Intel TCC libraryCleanup the code by using Intel TCC library for TCC (Thermal ControlCircuitry) MSR access.Signed-off-by: Zhang Rui Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/thermal/intel/Kconfig

a3c1f066 - thermal/intel: Introduce Intel TCC library

Mon, 19 Dec 2022 15:46:15 +0000

thermal/intel: Introduce Intel TCC libraryThere are several different drivers that accesses the Intel TCC(thermal control circuitry) MSRs, and each of them has its ownimplementation for the same functionalities, e.g. getting the currenttemperature, getting the tj_max, and getting/setting the tj_max offset.Introduce a library to unify the code for Intel CPU TCC MSR access.At the same time, ensure the temperature is got based on the updatedtjmax value because tjmax can be changed at runtime for cases likethe Intel SST-PP (Intel Speed Select Technology - Performance Profile)level change.Signed-off-by: Zhang Rui Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/thermal/intel/Kconfig

c95aa2ba - thermal: intel: hfi: INTEL_HFI_THERMAL depends on NET

Wed, 09 Feb 2022 00:15:46 +0000

thermal: intel: hfi: INTEL_HFI_THERMAL depends on NETTHERMAL_NETLINK depends on NET and since 'select' does not followany dependency chain, INTEL_HFI_THERMAL also should depend on NET.Fix one Kconfig warning and 48 subsequent build errors:WARNING: unmet direct dependencies detected for THERMAL_NETLINK Depends on [n]: THERMAL [=y] && NET [=n] Selected by [y]: - INTEL_HFI_THERMAL [=y] && THERMAL [=y] && (X86 [=y] || X86_INTEL_QUARK [=n] || COMPILE_TEST [=y]) && CPU_SUP_INTEL [=y] && X86_THERMAL_VECTOR [=y]Fixes: bd30cdfd9bd7 ("thermal: intel: hfi: Notify user space for HFI events")Signed-off-by: Randy Dunlap Reviewed-by: Srinivas Pandruvada Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/thermal/intel/Kconfig

bd30cdfd - thermal: intel: hfi: Notify user space for HFI events

Thu, 27 Jan 2022 19:34:54 +0000

thermal: intel: hfi: Notify user space for HFI eventsWhen the hardware issues an HFI event, relay a notification to user space.This allows user space to respond by reading performance and efficiency ofeach CPU and take appropriate action.For example, when the performance and efficiency of a CPU is 0, user spacecan either offline the CPU or inject idle. Also, if user space notices adownward trend in performance, it may proactively adjust power limits toavoid 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 asingle message. If there are more than 16 CPUs, issue as many messages asneeded to notify the status of all CPUs.In the HFI specification, both performance and efficiency capabilities aredefined in the [0, 255] range. The existing implementations of HFI hardwaredo not scale the maximum values to 255. Since userspace cares aboutcapability values that are either 0 or show a downward/upward trend, thisfact does not matter much. Relative changes in capabilities are enough. Tocomply with the thermal netlink ABI, scale both performance and efficiencycapabilities to the [0, 1023] interval.Reviewed-by: Len Brown Signed-off-by: Srinivas Pandruvada Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/thermal/intel/Kconfig

1cb19cab - thermal: intel: hfi: Minimally initialize the Hardware Feedback Interface

Thu, 27 Jan 2022 19:34:50 +0000

thermal: intel: hfi: Minimally initialize the Hardware Feedback InterfaceThe Intel Hardware Feedback Interface provides guidance to the operatingsystem about the performance and energy efficiency capabilities of eachCPU in the system. Capabilities are numbers between 0 and 255 where ahigher number represents a higher capability. For each CPU, energyefficiency and performance are reported as separate capabilities.Hardware computes these capabilities based on the operating conditions ofthe system such as power and thermal limits. These capabilities are sharedwith the operating system in a table resident in memory. Each package inthe system has its own HFI instance. Every logical CPU in the package isrepresented in the table. More than one logical CPUs may be represented ina single table entry. When the hardware updates the table, it generates apackage-level thermal interrupt.The size and format of the HFI table depend on the supported features andcan only be determined at runtime. To minimally initialize the HFI, parseits features and allocate one instance per package of a data structure withthe necessary parameters to read and navigate a local copy (i.e., owned bythe driver) of individual HFI tables.A subsequent changeset will provide per-CPU initialization and interrupthandling.Reviewed-by: Len Brown Co-developed by: Aubrey Li Signed-off-by: Aubrey Li Signed-off-by: Ricardo Neri Signed-off-by: Rafael J. Wysocki List of files: /linux-6.15/drivers/thermal/intel/Kconfig

2010319b - thermal/drivers/intel: Move intel_menlow to thermal drivers

Mon, 16 Aug 2021 03:53:56 +0000

thermal/drivers/intel: Move intel_menlow to thermal driversMoved drivers/platform/x86/intel_menlow.c to drivers/thermal/intel.Signed-off-by: Srinivas Pandruvada Acked-by: Daniel Lezcano Acked-by: Zhang Rui Link: https://lore.kernel.org/r/20210816035356.1955982-1-srinivas.pandruvada@linux.intel.comSigned-off-by: Hans de Goede List of files: /linux-6.15/drivers/thermal/intel/Kconfig

2eb87d75 - thermal/drivers/intel: Introduce tcc cooling driver

Mon, 12 Apr 2021 12:59:01 +0000

thermal/drivers/intel: Introduce tcc cooling driverOn Intel processors, the core frequency can be reduced below OS request,when the current temperature reaches the TCC (Thermal Control Circuit)activation temperature.The default TCC activation temperature is specified byMSR_IA32_TEMPERATURE_TARGET. However, it can be adjusted by specifying anoffset in degrees C, using the TCC Offset bits in the same MSR register.This patch introduces a cooling devices driver that utilizes the TCCOffset feature. The bigger the current cooling state is, the lower theeffective TCC activation temperature is, so that the processors can bethrottled earlier before system critical overheats.Note that, on different platforms, the behavior might be different onhow fast the setting takes effect, and how much the CPU frequency isreduced.This patch has been tested on a KabyLake mobile platform from me, and alsoon a CometLake platform from Doug.Signed-off-by: Zhang Rui Tested by: Doug Smythies Signed-off-by: Daniel Lezcano Link: https://lore.kernel.org/r/20210412125901.12549-1-rui.zhang@intel.com List of files: /linux-6.15/drivers/thermal/intel/Kconfig

9223d0dc - thermal: Move therm_throt there from x86/mce

Thu, 07 Jan 2021 12:29:05 +0000

thermal: Move therm_throt there from x86/mceThis functionality has nothing to do with MCE, move it to the thermalframework and untangle it from MCE.Requested-by: Peter Zijlstra Signed-off-by: Borislav Petkov Reviewed-by: Srinivas Pandruvada Tested-by: Srinivas Pandruvada Link: https://lkml.kernel.org/r/20210202121003.GD18075@zn.tnic List of files: /linux-6.15/drivers/thermal/intel/Kconfig

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/thermal/intel/Kconfig

e9cf125b - thermal/drivers/core: Remove depends on THERMAL in Kconfig

Tue, 02 Apr 2019 16:12:48 +0000

thermal/drivers/core: Remove depends on THERMAL in KconfigThe dependency on the THERMAL option to be set is already there implicitlyby the "if THERMAL" conditionnal option. The sub Kconfigs do not have tocheck against the THERMAL option as they are called from a Kconfig blockwhich is enabled by the conditionnal option.Remove the useless "depends on THERMAL" in the Kconfigs.Signed-off-by: Daniel Lezcano Signed-off-by: Zhang Rui List of files: /linux-6.15/drivers/thermal/intel/Kconfig