Searched +full:thermal +full:- +full:idle (Results 1 – 21 of 21) sorted by relevance
| /Documentation/devicetree/bindings/thermal/ |
| 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, 18 This binding describes the thermal idle node. 22 const: thermal-idle [all …]
|
| 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> 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 overload. 18 The following node types are used to completely describe a thermal management [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/driver-api/thermal/ |
| D | cpu-idle-cooling.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 CPU Idle Cooling 8 ---------- 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 ---------- 37 decrease. Acting on the idle state duration or the idle cycle 44 that will result in loss of performance during thermal control and 47 At a specific OPP, we can assume that injecting idle cycle on all CPUs 49 idle state target residency, we lead to dropping the static and the [all …]
|
| D | index.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 Thermal title 10 cpu-cooling-api 11 cpu-idle-cooling 12 sysfs-api
|
| D | intel_dptf.rst | 1 .. SPDX-License-Identifier: GPL-2.0 4 Intel(R) Dynamic Platform and Thermal Framework Sysfs Interface 12 ------------ 14 Intel(R) Dynamic Platform and Thermal Framework (DPTF) is a platform 15 level hardware/software solution for power and thermal management. 17 As a container for multiple power/thermal technologies, DPTF provides 25 to user space. This allows user space thermal solutions like 26 "Linux Thermal Daemon" to read platform specific thermal and power 28 thermal limits. 31 ---------------------------- [all …]
|
| D | cpu-cooling-api.rst | 22 -------------------------------------------- 30 "thermal-cpufreq-%x". This api can support multiple instances of cpufreq 42 the name "thermal-cpufreq-%x" linking it with a device tree node, in 43 order to bind it via the thermal DT code. This api can support multiple 54 This interface function unregisters the "thermal-cpufreq-%x" cooling device. 63 supported currently). This power model requires that the operating-points of 73 - The time the processor spends running, consuming dynamic power, as 74 compared to the time in idle states where dynamic consumption is 76 - The voltage and frequency levels as a result of DVFS. The DVFS 78 - In running time the 'execution' behaviour (instruction types, memory [all …]
|
| /Documentation/devicetree/bindings/cpufreq/ |
| D | cpufreq-mediatek.txt | 5 - clocks: A list of phandle + clock-specifier pairs for the clocks listed in clock names. 6 - clock-names: Should contain the following: 7 "cpu" - The multiplexer for clock input of CPU cluster. 8 "intermediate" - A parent of "cpu" clock which is used as "intermediate" clock 11 Please refer to Documentation/devicetree/bindings/clock/clock-bindings.txt for 13 - operating-points-v2: Please refer to Documentation/devicetree/bindings/opp/opp-v2.yaml 15 - proc-supply: Regulator for Vproc of CPU cluster. 18 - sram-supply: Regulator for Vsram of CPU cluster. When present, the cpufreq driver 23 - mediatek,cci: 30 - #cooling-cells: [all …]
|
| /Documentation/timers/ |
| D | no_hz.rst | 2 NO_HZ: Reducing Scheduling-Clock Ticks 7 reduce the number of scheduling-clock interrupts, thereby improving energy 9 some types of computationally intensive high-performance computing (HPC) 10 applications and for real-time applications. 12 There are three main ways of managing scheduling-clock interrupts 13 (also known as "scheduling-clock ticks" or simply "ticks"): 15 1. Never omit scheduling-clock ticks (CONFIG_HZ_PERIODIC=y or 16 CONFIG_NO_HZ=n for older kernels). You normally will -not- 19 2. Omit scheduling-clock ticks on idle CPUs (CONFIG_NO_HZ_IDLE=y or 23 3. Omit scheduling-clock ticks on CPUs that are either idle or that [all …]
|
| /Documentation/RCU/ |
| D | stallwarn.rst | 1 .. SPDX-License-Identifier: GPL-2.0 9 options that can be used to fine-tune the detector's operation. Finally, 20 - A CPU looping in an RCU read-side critical section. 22 - A CPU looping with interrupts disabled. 24 - A CPU looping with preemption disabled. 26 - A CPU looping with bottom halves disabled. 28 - For !CONFIG_PREEMPTION kernels, a CPU looping anywhere in the 33 - Booting Linux using a console connection that is too slow to 34 keep up with the boot-time console-message rate. For example, 36 with boot-time message rates, and will frequently result in [all …]
|
| /Documentation/admin-guide/pm/ |
| D | cpufreq.rst | 1 .. SPDX-License-Identifier: GPL-2.0 20 Operating Performance Points or P-states (in ACPI terminology). As a rule, 24 time (or the more power is drawn) by the CPU in the given P-state. Therefore 29 as possible and then there is no reason to use any P-states different from the 30 highest one (i.e. the highest-performance frequency/voltage configuration 35 long for thermal or power supply capacity reasons or similar. To cover those 38 put into different P-states. 41 capacity, so as to decide which P-states to put the CPUs into. Of course, since 64 information on the available P-states (or P-state ranges in some cases) and 65 access platform-specific hardware interfaces to change CPU P-states as requested [all …]
|
| D | intel_pstate.rst | 1 .. SPDX-License-Identifier: GPL-2.0 22 Documentation/admin-guide/pm/cpufreq.rst if you have not done that yet.] 24 For the processors supported by ``intel_pstate``, the P-state concept is broader 27 information about that). For this reason, the representation of P-states used 32 ``intel_pstate`` maps its internal representation of P-states to frequencies too 38 Since the hardware P-state selection interface used by ``intel_pstate`` is 43 time the corresponding CPU is taken offline and need to be re-initialized when 47 only way to pass early-configuration-time parameters to it is via the kernel 66 ----------- 69 hardware-managed P-states (HWP) support. If it works in this mode, the [all …]
|
| D | amd-pstate.rst | 1 .. SPDX-License-Identifier: GPL-2.0 5 ``amd-pstate`` CPU Performance Scaling Driver 16 ``amd-pstate`` is the AMD CPU performance scaling driver that introduces a 20 than legacy ACPI hardware P-States. Current AMD CPU/APU platforms are using 21 the ACPI P-states driver to manage CPU frequency and clocks with switching 22 only in 3 P-states. CPPC replaces the ACPI P-states controls and allows a 23 flexible, low-latency interface for the Linux kernel to directly 26 ``amd-pstate`` leverages the Linux kernel governors such as ``schedutil``, 30 Volume 2: System Programming [1]_). Currently, ``amd-pstate`` supports basic 40 continuous, abstract, and unit-less performance value in a scale that is [all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-regulator | 20 supplying power to the system (unless some non-Linux 38 - off 39 - on 40 - error 41 - fast 42 - normal 43 - idle 44 - standby 52 "error" indicates an out-of-regulation status such as being 53 disabled due to thermal shutdown, or voltage being unstable [all …]
|
| /Documentation/accel/qaic/ |
| D | aic100.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only 10 The Qualcomm Cloud AI 100/AIC100 family of products (including SA9000P - part of 20 performance. AIC100 cards are multi-user capable and able to execute workloads 26 An AIC100 card consists of an AIC100 SoC, on-card DDR, and a set of misc 39 AIC100 implements MSI but does not implement MSI-X. AIC100 prefers 17 MSIs to 44 hardware. AIC100 provides 3, 64-bit BARs. 54 From the host perspective, AIC100 has several key hardware components - 63 --- 71 --- 74 firmware of the card and performs on-card management tasks. It also [all …]
|
| /Documentation/scheduler/ |
| D | sched-util-clamp.rst | 1 .. SPDX-License-Identifier: GPL-2.0 57 foreground, top-app, etc. Util clamp can be used to constrain how much 60 the ones belonging to the currently active app (top-app group). Beside this 65 1. The big cores are free to run top-app tasks immediately. top-app 97 User space can form a feedback loop with the thermal subsystem too to ensure 106 Note that by design RT tasks don't have per-task PELT signal and must always 114 See :ref:`section 3.4 <uclamp-default-values>` for default values and 115 :ref:`3.4.1 <sched-util-clamp-min-rt-default>` on how to change RT tasks 150 task on the rq to only a subset of tasks on the top-most bucket. 157 uclamp value of the rq. See :ref:`section 2.1 <uclamp-buckets>` for details on [all …]
|
| /Documentation/power/regulator/ |
| D | consumer.rst | 139 changes. e.g. consumer driver is idle and subsequently draws less current 144 -------------------------------- 163 ------------------------------ 199 they need to do low-level hardware access to regulators, with no involvement 202 - clocksource with a voltage-controlled oscillator and control logic to change 204 - thermal management firmware that can issue an arbitrary I2C transaction to 212 Bus-specific details, like I2C addresses or transfer rates are handled by the 225 regulator_list_voltage) to a hardware-specific voltage selector that can be
|
| /Documentation/admin-guide/ |
| D | kernel-parameters.txt | 16 force -- enable ACPI if default was off 17 on -- enable ACPI but allow fallback to DT [arm64,riscv64] 18 off -- disable ACPI if default was on 19 noirq -- do not use ACPI for IRQ routing 20 strict -- Be less tolerant of platforms that are not 22 rsdt -- prefer RSDT over (default) XSDT 23 copy_dsdt -- copy DSDT to memory 24 nospcr -- disable console in ACPI SPCR table as 41 If set to vendor, prefer vendor-specific driver 73 Documentation/firmware-guide/acpi/debug.rst for more information about [all …]
|
| /Documentation/arch/arm64/ |
| D | acpi_object_usage.rst | 16 - Required: DSDT, FADT, GTDT, MADT, MCFG, RSDP, SPCR, XSDT 18 - Recommended: BERT, EINJ, ERST, HEST, PCCT, SSDT 20 - Optional: AGDI, BGRT, CEDT, CPEP, CSRT, DBG2, DRTM, ECDT, FACS, FPDT, 24 - Not supported: AEST, APMT, BOOT, DBGP, DMAR, ETDT, HPET, IVRS, LPIT, 41 This table describes a non-maskable event, that is used by the platform 68 Optional, not currently supported, with no real use-case for an 83 time as ARM-compatible hardware is available, and the specification 151 UEFI-based; if it is UEFI-based, this table may be supplied. When this 167 the hardware reduced profile, and only 64-bit address fields will 184 filled in properly - that the PSCI_COMPLIANT flag is set and that [all …]
|
| /Documentation/arch/arm/ |
| D | cluster-pm-race-avoidance.rst | 2 Cluster-wide Power-up/power-down race avoidance algorithm 16 --------- 19 ability to turn off individual CPUs when the system is idle, reducing 20 power consumption and thermal dissipation. 29 cluster-level operations are only performed when it is truly safe to do 35 disabling those mechanisms may itself be a non-atomic operation (such as 38 power-down and power-up at the cluster level. 46 ----------- 50 - DOWN 51 - COMING_UP [all …]
|
| /Documentation/filesystems/ |
| D | proc.rst | 1 .. SPDX-License-Identifier: GPL-2.0 24 1.1 Process-Specific Subdirectories 36 3 Per-Process Parameters 37 3.1 /proc/<pid>/oom_adj & /proc/<pid>/oom_score_adj - Adjust the oom-killer 39 3.2 /proc/<pid>/oom_score - Display current oom-killer score 40 3.3 /proc/<pid>/io - Display the IO accounting fields 41 3.4 /proc/<pid>/coredump_filter - Core dump filtering settings 42 3.5 /proc/<pid>/mountinfo - Information about mounts 44 3.7 /proc/<pid>/task/<tid>/children - Information about task children 45 3.8 /proc/<pid>/fdinfo/<fd> - Information about opened file [all …]
|