Searched +full:cooling +full:- +full:device (Results 1 – 25 of 30) sorted by relevance
12
| /Documentation/devicetree/bindings/thermal/ |
| D | thermal-cooling-devices.yaml | 1 # SPDX-License-Identifier: (GPL-2.0)
4 ---
5 $id: http://devicetree.org/schemas/thermal/thermal-cooling-devices.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Thermal cooling device
11 - Amit Kucheria <amitk@kernel.org>
15 and the software abstraction of cooling devices and thermal zones required to
20 - thermal-sensor: device that measures temperature, has SoC-specific bindings
21 - cooling-device: device used to dissipate heat either passively or actively
22 - thermal-zones: a container of the following node types used to describe all
[all …]
|
| D | thermal-idle.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
5 $id: http://devicetree.org/schemas/thermal/thermal-idle.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
8 title: Thermal idle cooling device
11 - Daniel Lezcano <daniel.lezcano@linaro.org>
14 The thermal idle cooling device allows the system to passively
15 mitigate the temperature on the device by injecting idle cycles,
22 const: thermal-idle
24 A thermal-idle node describes the idle cooling device properties to
[all …]
|
| D | thermal-zones.yaml | 1 # SPDX-License-Identifier: (GPL-2.0)
4 ---
5 $id: http://devicetree.org/schemas/thermal/thermal-zones.yaml#
6 $schema: http://devicetree.org/meta-schemas/base.yaml#
11 - Daniel Lezcano <daniel.lezcano@linaro.org>
15 and the software abstraction of cooling devices and thermal zones required to
20 - thermal-sensor: device that measures temperature, has SoC-specific bindings
21 - cooling-device: device used to dissipate heat either passively or actively
22 - thermal-zones: a container of the following node types used to describe all
25 This binding describes the thermal-zones.
[all …]
|
| D | max77620_thermal.txt | 5 are not configurable. Device does not provide the real temperature
10 -------------------
11 #thermal-sensor-cells: For more details, please refer to
12 <devicetree/bindings/thermal/thermal-sensor.yaml>
22 --------
23 #include <dt-bindings/mfd/max77620.h>
24 #include <dt-bindings/thermal/thermal.h>
31 #thermal-sensor-cells = <0>;
36 cool_dev: cool-dev {
37 compatible = "cooling-dev";
[all …]
|
| D | nvidia,tegra124-soctherm.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/thermal/nvidia,tegra124-soctherm.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
14 polled or interrupt-based thermal monitoring, CPU and GPU throttling based
21 - nvidia,tegra124-soctherm
22 - nvidia,tegra132-soctherm
23 - nvidia,tegra210-soctherm
[all …]
|
| D | db8500-thermal.txt | 1 * ST-Ericsson DB8500 Thermal
5 - compatible : "stericsson,db8500-thermal";
6 - reg : address range of the thermal sensor registers;
7 - interrupts : interrupts generated from PRCMU;
8 - interrupt-names : "IRQ_HOTMON_LOW" and "IRQ_HOTMON_HIGH";
9 - num-trips : number of total trip points, this is required, set it 0 if none,
11 - tripN-temp : temperature of trip point N, should be in ascending order;
12 - tripN-type : type of trip point N, should be one of "active" "passive" "hot"
14 - tripN-cdev-num : number of the cooling devices which can be bound to trip
16 otherwise the following cooling device names must be defined;
[all …]
|
| D | brcm,ns-thermal.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/thermal/brcm,ns-thermal.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rafał Miłecki <rafal@milecki.pl>
13 Thermal sensor that is part of Northstar's DMU (Device Management Unit).
16 - $ref: thermal-sensor.yaml#
20 const: brcm,ns-thermal
26 "#thermal-sensor-cells":
32 - reg
[all …]
|
| D | thermal-sensor.yaml | 1 # SPDX-License-Identifier: (GPL-2.0)
4 ---
5 $id: http://devicetree.org/schemas/thermal/thermal-sensor.yaml#
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Amit Kucheria <amitk@kernel.org>
20 - thermal-sensor: device that measures temperature, has SoC-specific bindings
21 - cooling-device: device used to dissipate heat either passively or actively
22 - thermal-zones: a container of the following node types used to describe all
25 This binding describes the thermal-sensor.
32 "#thermal-sensor-cells":
[all …]
|
| /Documentation/driver-api/thermal/ |
| D | sysfs-api.rst | 14 devices (sensors) and thermal cooling devices (fan, processor...) to register
17 This how-to focuses on enabling new thermal zone and cooling devices to
20 and cooling devices should be able to make use of the infrastructure.
23 as well as cooling device attributes to the user space.
28 - `[0-*]` denotes any positive number starting from 0
29 - `[1-*]` denotes any positive number starting from 1
34 1.1 thermal zone device interface
35 ---------------------------------
48 This interface function adds a new thermal zone device (sensor) to the
49 /sys/class/thermal folder as `thermal_zone[0-*]`. It tries to bind all the
[all …]
|
| D | cpu-cooling-api.rst | 2 CPU cooling APIs How To
14 The generic cpu cooling(freq clipping) provides registration/unregistration APIs
15 to the caller. The binding of the cooling devices to the trip point is left for
16 the user. The registration APIs returns the cooling device pointer.
18 1. cpu cooling APIs
22 --------------------------------------------
29 This interface function registers the cpufreq cooling device with the name
30 "thermal-cpufreq-%x". This api can support multiple instances of cpufreq
31 cooling devices.
41 This interface function registers the cpufreq cooling device with
[all …]
|
| D | power_allocator.rst | 6 -----------
20 --------------
23 Proportional-Integral-Derivative controller (PID controller) with
29 - e = desired_temperature - current_temperature
30 - err_integral is the sum of previous errors
31 - diff_err = e - previous_error
39 | +----------+ +---+
40 | +----->| diff_err |-->| X |------+
41 | | +----------+ +---+ |
47 +---+ | +-------+ +---+ +---+ +---+ +----------+
[all …]
|
| D | cpu-idle-cooling.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 CPU Idle Cooling
8 ----------
13 act on a cooling device to mitigate the dissipated power. When the
26 budget lower than the requested one and under-utilize the CPU, thus
27 losing performance. In other words, one OPP under-utilizes the CPU
33 ----------
58 ---------------
78 |------- -------
81 <------>
[all …]
|
| D | intel_dptf.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 ------------
31 ----------------------------
43 "42A441D6-AE6A-462b-A84B-4A8CE79027D3" : Passive 1
45 "3A95C389-E4B8-4629-A526-C52C88626BAE" : Active
47 "97C68AE7-15FA-499c-B8C9-5DA81D606E0A" : Critical
49 "63BE270F-1C11-48FD-A6F7-3AF253FF3E2D" : Adaptive performance
51 "5349962F-71E6-431D-9AE8-0A635B710AEE" : Emergency call
53 "9E04115A-AE87-4D1C-9500-0F3E340BFE75" : Passive 2
55 "F5A35014-C209-46A4-993A-EB56DE7530A1" : Power Boss
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-thermal | 5 E.g: "acpitz" indicates it's an ACPI thermal device.
61 E.g. it can be one of critical, hot, passive, `active[0-*]`
77 Sysfs link to the thermal cooling device node where the sys I/F
78 for cooling device throttling control represents.
84 The trip point in this thermal zone which `cdev[0-*]` is
85 associated with; -1 means the cooling device is not
92 The influence of `cdev[0-*]` in this thermal zone. This value
93 is relative to the rest of cooling devices in the thermal
94 zone. For example, if a cooling device has a weight double
95 than that of other, it's twice as effective in cooling the
[all …]
|
| /Documentation/devicetree/bindings/hwmon/ |
| D | aspeed-pwm-tacho.txt | 1 ASPEED AST2400/AST2500 PWM and Fan Tacho controller device driver
9 Required properties for pwm-tacho node:
10 - #address-cells : should be 1.
12 - #size-cells : should be 1.
14 - #cooling-cells: should be 2.
16 - reg : address and length of the register set for the device.
18 - pinctrl-names : a pinctrl state named "default" must be defined.
20 - pinctrl-0 : phandle referencing pin configuration of the PWM ports.
22 - compatible : should be "aspeed,ast2400-pwm-tacho" for AST2400 and
23 "aspeed,ast2500-pwm-tacho" for AST2500.
[all …]
|
| D | npcm750-pwm-fan.txt | 1 Nuvoton NPCM PWM and Fan Tacho controller device
3 The Nuvoton BMC NPCM7XX supports 8 Pulse-width modulation (PWM)
6 The Nuvoton BMC NPCM8XX supports 12 Pulse-width modulation (PWM)
9 Required properties for pwm-fan node
10 - #address-cells : should be 1.
11 - #size-cells : should be 0.
12 - compatible : "nuvoton,npcm750-pwm-fan" for Poleg NPCM7XX.
13 : "nuvoton,npcm845-pwm-fan" for Arbel NPCM8XX.
14 - reg : specifies physical base address and size of the registers.
15 - reg-names : must contain:
[all …]
|
| D | pwm-fan.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/hwmon/pwm-fan.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jean Delvare <jdelvare@suse.com>
11 - Guenter Roeck <linux@roeck-us.net>
15 const: pwm-fan
17 cooling-levels:
18 description: PWM duty cycle values corresponding to thermal cooling states.
19 $ref: /schemas/types.yaml#/definitions/uint32-array
[all …]
|
| /Documentation/hwmon/ |
| D | mlxreg-fan.rst | 1 Kernel driver mlxreg-fan
6 - QMB700, equipped with 40x200GbE InfiniBand ports;
7 - MSN3700, equipped with 32x200GbE or 16x400GbE Ethernet ports;
8 - MSN3410, equipped with 6x400GbE plus 48x50GbE Ethernet ports;
9 - MSN3800, equipped with 64x1000GbE Ethernet ports;
14 board with Mellanox Quantum or Spectrume-2 devices.
15 FAN controller is implemented by the programmable device logic.
17 The default registers offsets set within the programmable device is as
36 This setup can be re-programmed with other registers.
39 -----------
[all …]
|
| D | emc2305.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 https://www.microchip.com/en-us/product/EMC2305
15 ------------
16 This driver implements support for Microchip EMC2301/2/3/5 RPM-based PWM Fan Controller.
19 The driver supports the RPM-based PWM control to keep a fan at the desired speed.
26 fan[1-5]_fault RO files for tachometers TACH1-TACH5 fault indication
27 fan[1-5]_input RO files for tachometers TACH1-TACH5 input (in RPM)
28 pwm[1-5] RW file for fan[1-5] target duty cycle (0..255)
34 cur_state RW file for the current cooling state of the cooling device (0..max_state)
35 max_state RO file for the maximum cooling state of the cooling device
|
| D | aquacomputer_d5next.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later
3 Kernel driver aquacomputer-d5next
25 -----------
37 available through debugfs are the serial number, firmware version and power-on
39 temperature curves directly from the pump. If it's not connected, the fan-related
61 and an estimation of the dissipated/absorbed power in the liquid cooling loop.
65 filled with coolant. Pump RPM and flow can be set to enhance on-device calculations,
83 Depending on the device, not all sysfs and debugfs entries will be available.
87 -----------
93 -------------
[all …]
|
| /Documentation/admin-guide/acpi/ |
| D | fan_performance_states.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 When the optional _FPS object is present under an ACPI device representing a
9 "state*" attributes in the sysfs directory of the ACPI device in question.
16 For instance, the contents of the INT3404 ACPI device sysfs directory
19 $ ls -l /sys/bus/acpi/devices/INT3404:00/
22 -r--r--r-- 1 root root 4096 Dec 13 20:38 state0
23 -r--r--r-- 1 root root 4096 Dec 13 20:38 state1
24 -r--r--r-- 1 root root 4096 Dec 13 20:38 state10
25 -r--r--r-- 1 root root 4096 Dec 13 20:38 state11
26 -r--r--r-- 1 root root 4096 Dec 13 20:38 state2
[all …]
|
| /Documentation/admin-guide/thermal/ |
| D | intel_powerclamp.rst | 6 - Arjan van de Ven <arjan@linux.intel.com>
7 - Jacob Pan <jacob.jun.pan@linux.intel.com>
12 - Goals and Objectives
15 - Idle Injection
16 - Calibration
19 - Effectiveness and Limitations
20 - Power vs Performance
21 - Scalability
22 - Calibration
23 - Comparison with Alternative Techniques
[all …]
|
| /Documentation/devicetree/bindings/display/msm/ |
| D | gpu.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Rob Clark <robdclark@gmail.com>
14 # as a work-around:
20 - qcom,adreno
21 - amd,imageon
23 - compatible
28 - description: |
30 figure out the chip-id.
[all …]
|
| /Documentation/driver-api/surface_aggregator/ |
| D | overview.rst | 1 .. SPDX-License-Identifier: GPL-2.0+
10 its responsibilities and feature-set have since been expanded significantly
23 sensors (e.g. skin temperature) and cooling/performance-mode setting to the
26 display part from the keyboard part of the device), on the Surface Laptop 1
36 SAN), translating ACPI generic serial bus write-/read-accesses to SAM
40 harder to discover and requiring us to hard-code a sort of device registry.
49 generation of the Surface device. On 4th generation devices, host and EC
50 communicate via HID, specifically using a HID-over-I2C device, whereas on
52 device. In accordance to the drivers found on other operating systems, we
53 refer to the serial device and its driver as Surface Serial Hub (SSH). When
[all …]
|
| /Documentation/driver-api/gpio/ |
| D | drivers-on-gpio.rst | 6 the right in-kernel and userspace APIs/ABIs for the job, and that these
8 hardware descriptions such as device tree or ACPI:
10 - leds-gpio: drivers/leds/leds-gpio.c will handle LEDs connected to GPIO
13 - ledtrig-gpio: drivers/leds/trigger/ledtrig-gpio.c will provide a LED trigger,
15 (and that LED may in turn use the leds-gpio as per above).
17 - gpio-keys: drivers/input/keyboard/gpio_keys.c is used when your GPIO line
20 - gpio-keys-polled: drivers/input/keyboard/gpio_keys_polled.c is used when your
24 - gpio_mouse: drivers/input/mouse/gpio_mouse.c is used to provide a mouse with
29 - gpio-beeper: drivers/input/misc/gpio-beeper.c is used to provide a beep from
31 off/on, for an actual PWM waveform, see pwm-gpio below.)
[all …]
|
12