| /kernel/linux/linux-4.19/drivers/thermal/ |
| D | Kconfig | 2 # Generic thermal sysfs drivers configuration
5 menuconfig THERMAL config
6 tristate "Generic Thermal sysfs driver"
8 Generic Thermal Sysfs driver offers a generic mechanism for
9 thermal management. Usually it's made up of one or more thermal
11 Each thermal zone contains its own temperature, trip points,
13 All platforms with ACPI thermal support can use this driver.
16 if THERMAL
19 bool "Thermal state transition statistics"
21 Export thermal state transition statistics information through sysfs.
[all …]
|
| D | da9062-thermal.c | 2 * Thermal device driver for DA9062 and DA9061
20 * implementation of the thermal driver will include a .notify() function
36 #include <linux/thermal.h>
71 struct da9062_thermal *thermal = container_of(work, in da9062_thermal_poll_on() local
79 ret = regmap_write(thermal->hw->regmap, in da9062_thermal_poll_on()
83 dev_err(thermal->dev, in da9062_thermal_poll_on()
92 ret = regmap_read(thermal->hw->regmap, in da9062_thermal_poll_on()
96 dev_err(thermal->dev, in da9062_thermal_poll_on()
102 mutex_lock(&thermal->lock); in da9062_thermal_poll_on()
103 thermal->temperature = DA9062_MILLI_CELSIUS(125); in da9062_thermal_poll_on()
[all …]
|
| D | rockchip_thermal.c | 26 #include <linux/thermal.h>
134 * struct rockchip_thermal_sensor - hold the information of thermal sensor
135 * @thermal: pointer to the platform/configuration data
136 * @tzd: pointer to a thermal zone
137 * @id: identifier of the thermal sensor
140 struct rockchip_thermal_data *thermal; member
146 * struct rockchip_thermal_data - hold the private data of thermal driver
148 * @pdev: platform device of thermal
150 * @sensors[SOC_MAX_SENSORS]: the thermal sensor
1036 struct rockchip_thermal_data *thermal = dev; in rockchip_thermal_alarm_irq_thread() local
[all …]
|
| /kernel/linux/linux-5.10/drivers/thermal/ |
| D | Kconfig | 3 # Generic thermal drivers configuration
6 menuconfig THERMAL config
7 bool "Thermal drivers"
9 Thermal drivers offer a generic mechanism for
10 thermal management. Usually it's made up of one or more thermal
12 Each thermal zone contains its own temperature, trip points,
14 All platforms with ACPI or Open Firmware thermal support can use
18 if THERMAL
21 bool "Thermal netlink management"
24 The thermal framework has a netlink interface to do thermal
[all …]
|
| D | da9062-thermal.c | 3 * Thermal device driver for DA9062 and DA9061
11 * implementation of the thermal driver will include a .notify() function
27 #include <linux/thermal.h>
61 struct da9062_thermal *thermal = container_of(work, in da9062_thermal_poll_on() local
69 ret = regmap_write(thermal->hw->regmap, in da9062_thermal_poll_on()
73 dev_err(thermal->dev, in da9062_thermal_poll_on()
82 ret = regmap_read(thermal->hw->regmap, in da9062_thermal_poll_on()
86 dev_err(thermal->dev, in da9062_thermal_poll_on()
92 mutex_lock(&thermal->lock); in da9062_thermal_poll_on()
93 thermal->temperature = DA9062_MILLI_CELSIUS(125); in da9062_thermal_poll_on()
[all …]
|
| D | rockchip_thermal.c | 18 #include <linux/thermal.h>
129 * struct rockchip_thermal_sensor - hold the information of thermal sensor
130 * @thermal: pointer to the platform/configuration data
131 * @tzd: pointer to a thermal zone
132 * @id: identifier of the thermal sensor
135 struct rockchip_thermal_data *thermal; member
141 * struct rockchip_thermal_data - hold the private data of thermal driver
143 * @pdev: platform device of thermal
145 * @sensors: array of thermal sensors
1079 struct rockchip_thermal_data *thermal = dev; in rockchip_thermal_alarm_irq_thread() local
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/thermal/ |
| D | rcar-thermal.yaml | 5 $id: http://devicetree.org/schemas/thermal/rcar-thermal.yaml#
8 title: Renesas R-Car Thermal
18 - renesas,thermal-r8a73a4 # R-Mobile APE6
19 - renesas,thermal-r8a7779 # R-Car H1
20 - const: renesas,rcar-thermal # Generic without thermal-zone
23 - renesas,thermal-r8a7742 # RZ/G1H
24 - renesas,thermal-r8a7743 # RZ/G1M
25 - renesas,thermal-r8a7744 # RZ/G1N
26 - const: renesas,rcar-gen2-thermal # Generic thermal-zone
29 - renesas,thermal-r8a7790 # R-Car H2
[all …]
|
| D | thermal-zones.yaml | 5 $id: http://devicetree.org/schemas/thermal/thermal-zones.yaml#
8 title: Thermal zone binding
14 Thermal management is achieved in devicetree by describing the sensor hardware
15 and the software abstraction of cooling devices and thermal zones required to
16 take appropriate action to mitigate thermal overloads.
18 The following node types are used to completely describe a thermal management
20 - thermal-sensor: device that measures temperature, has SoC-specific bindings
22 - thermal-zones: a container of the following node types used to describe all
23 thermal data for the platform
25 This binding describes the thermal-zones.
[all …]
|
| D | brcm,sr-thermal.txt | 1 * Broadcom Stingray Thermal
3 This binding describes thermal sensors that is part of Stingray SoCs.
6 - compatible : Must be "brcm,sr-thermal"
10 - #thermal-sensor-cells : Thermal sensor phandler
12 - thermal-sensors: A list of thermal sensor phandles and specifier.
25 compatible = "brcm,sr-thermal";
28 #thermal-sensor-cells = <1>;
32 thermal-zones {
33 ihost0_thermal: ihost0-thermal {
36 thermal-sensors = <&tmon 0>;
[all …]
|
| D | brcm,bcm2835-thermal.txt | 1 Binding for Thermal Sensor driver for BCM2835 SoCs.
6 compatible: should be one of: "brcm,bcm2835-thermal",
7 "brcm,bcm2836-thermal" or "brcm,bcm2837-thermal"
8 reg: Address range of the thermal registers.
9 clocks: Phandle of the clock used by the thermal sensor.
10 #thermal-sensor-cells: should be 0 (see Documentation/devicetree/bindings/thermal/thermal-sensor.ya…
14 thermal-zones {
15 cpu_thermal: cpu-thermal {
19 thermal-sensors = <&thermal>;
36 thermal: thermal@7e212000 {
[all …]
|
| D | rcar-gen3-thermal.yaml | 5 $id: http://devicetree.org/schemas/thermal/rcar-gen3-thermal.yaml#
8 title: Renesas R-Car Gen3 Thermal Sensor
11 On R-Car Gen3 SoCs, the thermal sensor controllers (TSC) control the thermal
21 - renesas,r8a774a1-thermal # RZ/G2M
22 - renesas,r8a774b1-thermal # RZ/G2N
23 - renesas,r8a774e1-thermal # RZ/G2H
24 - renesas,r8a7795-thermal # R-Car H3
25 - renesas,r8a7796-thermal # R-Car M3-W
26 - renesas,r8a77961-thermal # R-Car M3-W+
27 - renesas,r8a77965-thermal # R-Car M3-N
[all …]
|
| D | mediatek-thermal.txt | 1 * Mediatek Thermal
3 This describes the device tree binding for the Mediatek thermal controller
12 - "mediatek,mt8173-thermal" : For MT8173 family of SoCs
13 - "mediatek,mt2701-thermal" : For MT2701 family of SoCs
14 - "mediatek,mt2712-thermal" : For MT2712 family of SoCs
15 - "mediatek,mt7622-thermal" : For MT7622 SoC
16 - "mediatek,mt8183-thermal" : For MT8183 family of SoCs
17 - reg: Address range of the thermal controller
18 - interrupts: IRQ for the thermal controller
19 - clocks, clock-names: Clocks needed for the thermal controller. required
[all …]
|
| D | thermal-sensor.yaml | 5 $id: http://devicetree.org/schemas/thermal/thermal-sensor.yaml#
8 title: Thermal sensor binding
14 Thermal management is achieved in devicetree by describing the sensor hardware
15 and the software abstraction of thermal zones required to take appropriate
16 action to mitigate thermal overloads.
18 The following node types are used to completely describe a thermal management
20 - thermal-sensor: device that measures temperature, has SoC-specific bindings
22 - thermal-zones: a container of the following node types used to describe all
23 thermal data for the platform
25 This binding describes the thermal-sensor.
[all …]
|
| D | amazon,al-thermal.txt | 1 Amazon's Annapurna Labs Thermal Sensor
3 Simple thermal device that allows temperature reading by a single MMIO
7 - compatible: "amazon,al-thermal".
9 - #thermal-sensor-cells: Must be 1. See Documentation/devicetree/bindings/thermal/thermal-sensor.ya…
12 thermal: thermal {
13 compatible = "amazon,al-thermal";
15 #thermal-sensor-cells = <0x1>;
18 thermal-zones {
19 thermal-z0 {
22 thermal-sensors = <&thermal 0>;
|
| D | nvidia,tegra186-bpmp-thermal.txt | 1 NVIDIA Tegra186 BPMP thermal sensor
5 and GPU temperatures. This binding describes the thermal sensor that is
8 The BPMP thermal node must be located directly inside the main BPMP node. See
11 This node represents a thermal sensor. See Documentation/devicetree/bindings/thermal/thermal-sensor…
12 core thermal binding.
18 - "nvidia,tegra186-bpmp-thermal"
19 - "nvidia,tegra194-bpmp-thermal"
20 - #thermal-sensor-cells: Cell for sensor index.
29 bpmp_thermal: thermal {
30 compatible = "nvidia,tegra186-bpmp-thermal";
[all …]
|
| /kernel/linux/linux-4.19/Documentation/thermal/ |
| D | sysfs-api.txt | 1 Generic Thermal Sysfs driver How To
13 The generic thermal sysfs provides a set of interfaces for thermal zone
14 devices (sensors) and thermal cooling devices (fan, processor...) to register
15 with the thermal management solution and to be a part of it.
17 This how-to focuses on enabling new thermal zone and cooling devices to
18 participate in thermal management.
19 This solution is platform independent and any type of thermal zone devices
22 The main task of the thermal sysfs driver is to expose thermal zone attributes
24 An intelligent thermal management application can make decisions based on
25 inputs from thermal zone attributes (the current temperature and trip point
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/thermal/ |
| D | rcar-thermal.txt | 1 * Renesas R-Car Thermal
4 - compatible : "renesas,thermal-<soctype>",
5 "renesas,rcar-gen2-thermal" (with thermal-zone) or
6 "renesas,rcar-thermal" (without thermal-zone) as
9 - "renesas,thermal-r8a73a4" (R-Mobile APE6)
10 - "renesas,thermal-r8a7743" (RZ/G1M)
11 - "renesas,thermal-r8a7779" (R-Car H1)
12 - "renesas,thermal-r8a7790" (R-Car H2)
13 - "renesas,thermal-r8a7791" (R-Car M2-W)
14 - "renesas,thermal-r8a7792" (R-Car V2H)
[all …]
|
| D | thermal.txt | 1 * Thermal Framework Device Tree descriptor
4 defining hardware thermal structure using device tree.
5 A thermal structure includes thermal zones and their components,
9 The target of device tree thermal descriptors is to describe only
10 the hardware thermal aspects. The thermal device tree bindings are
14 There are five types of nodes involved to describe thermal bindings:
15 - thermal sensors: devices which may be used to take temperature
21 - thermal zones: used to describe thermal data within the hardware;
25 * Thermal sensor devices
27 Thermal sensor devices are nodes providing temperature sensing capabilities on
[all …]
|
| D | brcm,bcm2835-thermal.txt | 1 Binding for Thermal Sensor driver for BCM2835 SoCs.
6 compatible: should be one of: "brcm,bcm2835-thermal",
7 "brcm,bcm2836-thermal" or "brcm,bcm2837-thermal"
8 reg: Address range of the thermal registers.
9 clocks: Phandle of the clock used by the thermal sensor.
10 #thermal-sensor-cells: should be 0 (see thermal.txt)
14 thermal-zones {
15 cpu_thermal: cpu-thermal {
19 thermal-sensors = <&thermal>;
36 thermal: thermal@7e212000 {
[all …]
|
| D | mediatek-thermal.txt | 1 * Mediatek Thermal
3 This describes the device tree binding for the Mediatek thermal controller
12 - "mediatek,mt8173-thermal" : For MT8173 family of SoCs
13 - "mediatek,mt2701-thermal" : For MT2701 family of SoCs
14 - "mediatek,mt2712-thermal" : For MT2712 family of SoCs
15 - "mediatek,mt7622-thermal" : For MT7622 SoC
16 - reg: Address range of the thermal controller
17 - interrupts: IRQ for the thermal controller
18 - clocks, clock-names: Clocks needed for the thermal controller. required
22 - resets: Reference to the reset controller controlling the thermal controller.
[all …]
|
| D | armada-thermal.txt | 1 * Marvell Armada 370/375/380/XP thermal management
6 * marvell,armada370-thermal
7 * marvell,armada375-thermal
8 * marvell,armada380-thermal
9 * marvell,armadaxp-thermal
10 * marvell,armada-ap806-thermal
11 * marvell,armada-cp110-thermal
22 Note: The compatibles marvell,armada370-thermal,
23 marvell,armada380-thermal, and marvell,armadaxp-thermal must point to
31 thermal@d0018300 {
[all …]
|
| /kernel/linux/linux-5.10/drivers/net/ethernet/mellanox/mlxsw/ |
| D | core_thermal.c | 10 #include <linux/thermal.h>
31 /* External cooling devices, allowed for binding to mlxsw thermal zones. */
124 static int mlxsw_get_cooling_device_idx(struct mlxsw_thermal *thermal, in mlxsw_get_cooling_device_idx() argument
130 if (thermal->cdevs[i] == cdev) in mlxsw_get_cooling_device_idx()
133 /* Allow mlxsw thermal zone binding to an external cooling device */ in mlxsw_get_cooling_device_idx()
177 /* According to the system thermal requirements, the thermal zones are in mlxsw_thermal_module_trips_update()
197 static void mlxsw_thermal_tz_score_update(struct mlxsw_thermal *thermal, in mlxsw_thermal_tz_score_update() argument
205 /* Calculate thermal zone score, if temperature is above the critical in mlxsw_thermal_tz_score_update()
219 if (score > thermal->tz_highest_score) { in mlxsw_thermal_tz_score_update()
220 thermal->tz_highest_score = score; in mlxsw_thermal_tz_score_update()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/thermal/ |
| D | sysfs-api.rst | 2 Generic Thermal Sysfs driver How To
15 The generic thermal sysfs provides a set of interfaces for thermal zone
16 devices (sensors) and thermal cooling devices (fan, processor...) to register
17 with the thermal management solution and to be a part of it.
19 This how-to focuses on enabling new thermal zone and cooling devices to
20 participate in thermal management.
21 This solution is platform independent and any type of thermal zone devices
24 The main task of the thermal sysfs driver is to expose thermal zone attributes
26 An intelligent thermal management application can make decisions based on
27 inputs from thermal zone attributes (the current temperature and trip point
[all …]
|
| /kernel/linux/linux-4.19/drivers/net/ethernet/mellanox/mlxsw/ |
| D | core_thermal.c | 10 #include <linux/thermal.h>
87 static int mlxsw_get_cooling_device_idx(struct mlxsw_thermal *thermal, in mlxsw_get_cooling_device_idx() argument
93 if (thermal->cdevs[i] == cdev) in mlxsw_get_cooling_device_idx()
102 struct mlxsw_thermal *thermal = tzdev->devdata; in mlxsw_thermal_bind() local
103 struct device *dev = thermal->bus_info->dev; in mlxsw_thermal_bind()
107 if (mlxsw_get_cooling_device_idx(thermal, cdev) < 0) in mlxsw_thermal_bind()
111 const struct mlxsw_thermal_trip *trip = &thermal->trips[i]; in mlxsw_thermal_bind()
128 struct mlxsw_thermal *thermal = tzdev->devdata; in mlxsw_thermal_unbind() local
129 struct device *dev = thermal->bus_info->dev; in mlxsw_thermal_unbind()
134 if (mlxsw_get_cooling_device_idx(thermal, cdev) < 0) in mlxsw_thermal_unbind()
[all …]
|
| /kernel/linux/linux-5.10/drivers/thermal/intel/ |
| D | Kconfig | 9 user interface is exposed via generic thermal framework.
12 tristate "X86 package temperature thermal driver"
19 thermal zone. Each package will have its own thermal zone. There are
20 two trip points which can be set by user to get notifications via thermal
34 tristate "Intel SoCs DTS thermal driver"
42 thermal zone. There are two trip points. One of the trip point can
43 be set by user mode programs to get notifications via Linux thermal
48 tristate "Intel Quark DTS thermal driver"
53 The DTS will be registered as a thermal zone. There are two trip points:
57 menu "ACPI INT340X thermal drivers"
[all …]
|