Searched +full:run +full:- +full:control (Results 1 – 25 of 309) sorted by relevance
12345678910>>...13
| /Documentation/hwmon/ |
| D | g762.rst | 5 and performs closed-loop or open-loop control of the fan speed. Two 6 modes - PWM or DC - are supported by the device. 9 http://natisbad.org/NAS/ref/GMT_EDS-762_763-080710-0.2.pdf. sysfs 10 bindings are described in Documentation/hwmon/sysfs-interface.rst. 13 /sys/bus/i2c/drivers/g762/ to control the operation of the device. 25 set desired fan speed. This only makes sense in closed-loop 26 fan speed control (i.e. when pwm1_enable is set to 2). 44 in closed-loop control mode, if fan RPM value is 25% out 49 set current fan speed control mode i.e. 1 for manual fan 50 speed control (open-loop) via pwm1 described below, 2 for [all …]
|
| D | adt7470.rst | 17 ----------- 22 The ADT7470 uses the 2-wire interface compatible with the SMBus 2.0 24 external temperatures. It has four (4) 16-bit counters for measuring fan speed. 25 There are four (4) PWM outputs that can be used to control fan speed. 27 A sophisticated control system for the PWM outputs is designed into the ADT7470 32 feature can also be disabled for manual control of the PWM's. 40 automatic fan pwm control to set the fan speed. The driver will not read the 45 ---------------- 47 The ADT7470 has a 8-bit ADC and is capable of measuring temperatures with 1 51 determining an optimal configuration for the automatic PWM control. [all …]
|
| /Documentation/scheduler/ |
| D | sched-rt-group.rst | 2 Real-Time group scheduling 12 2.1 System-wide settings 33 are real-time processes). 40 --------------- 42 Real-time scheduling is all about determinism, a group has to be able to rely on 44 multiple groups of real-time tasks, each group must be assigned a fixed portion 45 of the CPU time available. Without a minimum guarantee a real-time group can 50 ---------------- 53 in a given period. We allocate this "run time" for each real-time group which 54 the other real-time groups will not be permitted to use. [all …]
|
| D | sched-bwc.rst | 2 CFS Bandwidth Control 6 This document only discusses CPU bandwidth control for SCHED_NORMAL. 7 The SCHED_RT case is covered in Documentation/scheduler/sched-rt-group.rst 9 CFS bandwidth control is a CONFIG_FAIR_GROUP_SCHED extension which allows the 14 microseconds of CPU time. That quota is assigned to per-cpu run queues in 17 throttled. Throttled threads will not be able to run again until the next 22 is transferred to cpu-local "silos" on a demand basis. The amount transferred 26 ------------- 30 Traditional (UP-EDF) bandwidth control is something like: 36 we'd have to run more than a second of program time, and obviously miss [all …]
|
| /Documentation/leds/ |
| D | leds-lp5521.rst | 10 Contact: Samu Onkalo (samu.p.onkalo-at-nokia.com) 13 ----------- 16 the led class control interface. Channels have generic names: 23 There are two ways to run LED patterns. 25 1) Legacy interface - enginex_mode and enginex_load 26 Control interface for the engines: 31 disabled, load, run 40 echo "run" > engine3_mode 46 2) Firmware interface - LP55xx common interface 48 For the details, please refer to 'firmware' section in leds-lp55xx.txt [all …]
|
| D | leds-lp5523.rst | 9 Contact: Samu Onkalo (samu.p.onkalo-at-nokia.com) 12 ----------- 14 the led class control interface. 15 The name of each channel is configurable in the platform data - name and label. 22 - /sys/class/leds/R1 (name: 'R1') 23 - /sys/class/leds/B1 (name: 'B1') 28 - /sys/class/leds/RGB:channelN (label: 'RGB', N: 0 ~ 8) 33 - /sys/class/leds/lp5523:channelN (N: 0 ~ 8) 36 There are two ways to run LED patterns. 38 1) Legacy interface - enginex_mode, enginex_load and enginex_leds [all …]
|
| D | leds-lp55xx.rst | 8 ----------- 14 Device attributes for user-space interface 28 control multi output LED channels such as led current, channel index. 30 general chip control such like the I2C and platform data. 50 - Maximum number of channels 51 - Reset command, chip enable command 52 - Chip specific initialization 53 - Brightness control register access 54 - Setting LED output current 55 - Program memory address access for running patterns [all …]
|
| D | ledtrig-transient.rst | 36 that are active at the time driver gets suspended, continue to run, without 56 non-transient state. When driver gets suspended, irrespective of the transient 66 Add a new property trigger state to control the state. 71 - duration allows setting timer value in msecs. The initial value is 0. 72 - activate allows activating and deactivating the timer specified by 75 - state allows user to specify a transient state to be held for the specified 79 - one shot timer activate mechanism. 90 - one shot timer value. When activate is set, duration value 96 - transient state to be held. It has two values 0 or 1. 0 maps 99 state gets changed to the non-transient state which is the [all …]
|
| /Documentation/devicetree/bindings/pinctrl/ |
| D | sprd,pinctrl.txt | 5 The first block comprises some global control registers, and each 8 pad driving level, system control select and so on ("domain pad 11 select 3.0v, then the pin can output 3.0v. "system control" is used 16 of them, so we can not make every Spreadtrum-special configuration 18 global configuration in future. Then we add one "sprd,control" to 19 set these various global control configuration, and we need use 23 bits in one global control register as one pin, thus we should 35 - input-enable 36 - input-disable 37 - output-high [all …]
|
| /Documentation/dev-tools/kunit/ |
| D | faq.rst | 1 .. SPDX-License-Identifier: GPL-2.0 17 the test's control like hardware. 21 testing frameworks require tests to be written in userspace and run on the 35 (see :ref:`kunit-on-qemu`). 37 In short, yes, you can run KUnit on other architectures, but it might require 40 For more information, see :ref:`kunit-on-non-uml`. 42 .. _kinds-of-tests: 47 test, or an end-to-end test. 49 - A unit test is supposed to test a single unit of code in isolation. A unit 53 outside of the test's control like hardware. [all …]
|
| /Documentation/arch/powerpc/ |
| D | dexcr.rst | 1 .. SPDX-License-Identifier: GPL-2.0-or-later 4 DEXCR (Dynamic Execution Control Register) 11 PowerPC ISA 3.1B (Power10) that allows per-cpu control over several dynamic 13 branch target prediction) and enabling return-oriented programming (ROP) 16 The execution control is exposed in hardware as up to 32 bits ('aspects') in 22 A privileged SPR that can control aspects for userspace and kernel space 24 A hypervisor-privileged SPR that can control aspects for the hypervisor and 27 An optional ultravisor-privileged SPR that can control aspects for the ultravisor. 30 provides a non-privileged read-only view of the userspace DEXCR aspects. 31 There is also an SPR that provides a read-only view of the hypervisor enforced [all …]
|
| /Documentation/devicetree/bindings/soc/fsl/ |
| D | fsl,rcpm.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: Run Control and Power Management 10 The RCPM performs all device-level tasks associated with device run control 14 - Frank Li <Frank.Li@nxp.com> 19 - items: 20 - enum: 21 - fsl,p2041-rcpm 22 - fsl,p3041-rcpm [all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-lm3532.txt | 1 * Texas Instruments - lm3532 White LED driver with ambient light sensing 4 The LM3532 provides the 3 high-voltage, low-side current sinks. The device is 5 programmable over an I2C-compatible interface and has independent 6 current control for all three channels. The adaptive current regulation 11 each with 32 internal voltage setting resistors, 8-bit logarithmic and linear 12 brightness control, dual external PWM brightness control inputs, and up to 16 - compatible : "ti,lm3532" 17 - reg : I2C slave address 18 - #address-cells : 1 19 - #size-cells : 0 [all …]
|
| /Documentation/devicetree/bindings/regulator/ |
| D | rohm,bd71815-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/regulator/rohm,bd71815-regulator.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Matti Vaittinen <mazziesaccount@gmail.com> 14 see Documentation/devicetree/bindings/mfd/rohm,bd71815-pmic.yaml. 16 The regulator controller is represented as a sub-node of the PMIC node 33 regulator-name: 37 "^((ldo|buck)[1-5]|ldolpsr|ldodvref)$": 44 regulator-name: [all …]
|
| D | rohm,bd71847-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/regulator/rohm,bd71847-regulator.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Matti Vaittinen <mazziesaccount@gmail.com> 15 Documentation/devicetree/bindings/mfd/rohm,bd71847-pmic.yaml 20 Note that if BD71847 starts at RUN state you probably want to use 21 regulator-boot-on at least for BUCK5. LDO6 is supplied by it and it must 30 "^LDO[1-6]$": 37 regulator-name: [all …]
|
| D | rohm,bd71837-regulator.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/regulator/rohm,bd71837-regulator.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Matti Vaittinen <mazziesaccount@gmail.com> 15 Documentation/devicetree/bindings/mfd/rohm,bd71837-pmic.yaml 20 Note that if BD71837 starts at RUN state you probably want to use 21 regulator-boot-on at least for BUCK6 and BUCK7 so that those are not 31 "^LDO[1-7]$": 38 regulator-name: [all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-kernel-mm-ksm | 4 Contact: Linux memory management mailing list <linux-mm@kvack.org> 13 What: /sys/kernel/mm/ksm/run 16 Contact: Linux memory management mailing list <linux-mm@kvack.org> 36 run: write 0 to disable ksm, read 0 while ksm is disabled. 38 - write 1 to run ksm, read 1 while ksm is running. 39 - write 2 to disable ksm and unmerge all its pages. 49 Contact: Linux memory management mailing list <linux-mm@kvack.org> 50 Description: Control merging pages across different NUMA nodes. 58 Contact: Linux memory management mailing list <linux-mm@kvack.org> 61 calculation is in Documentation/admin-guide/mm/ksm.rst.
|
| D | sysfs-platform-dell-laptop | 7 This file allows to control the automatic keyboard 27 This file allows to control the input triggers that 31 enabled are preceded by '+', those disabled by '-'. 35 by '-' instead. 37 For example, to enable the keyboard as trigger run:: 43 echo -keyboard > /sys/class/leds/dell::kbd_backlight/start_triggers 63 For example, to set the timeout to 10 minutes run::
|
| D | sysfs-devices-power | 35 What: /sys/devices/.../power/control 39 The /sys/devices/.../power/control attribute allows the user 40 space to control the run-time power management of the device. 43 power/control file: 45 + "auto\n" to allow the device to be power managed at run time; 51 from power managing the device at run time. Doing that while 61 with the main suspend/resume thread) during system-wide power 86 attribute is read-only. If the device is not capable to wake up 98 is read-only. If the device is not capable to wake up the 110 state in progress. This attribute is read-only. If the device [all …]
|
| /Documentation/devicetree/bindings/dvfs/ |
| D | performance-domain.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/dvfs/performance-domain.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Sudeep Holla <sudeep.holla@arm.com> 14 CPUs that run in the same performance domain. Performance domains must not 16 of devices that always have to run at the same performance level. For a given 17 performance domain, there is a single point of control that affects all the 21 have a common frequency control, is said to be in the same performance 30 \#performance-domain-cells property in the performance domain provider node. [all …]
|
| /Documentation/admin-guide/hw-vuln/ |
| D | l1tf.rst | 1 L1TF - L1 Terminal Fault 10 ------------------- 15 - Processors from AMD, Centaur and other non Intel vendors 17 - Older processor models, where the CPU family is < 6 19 - A range of Intel ATOM processors (Cedarview, Cloverview, Lincroft, 22 - The Intel XEON PHI family 24 - Intel processors which have the ARCH_CAP_RDCL_NO bit set in the 33 ------------ 38 CVE-2018-3615 L1 Terminal Fault SGX related aspects 39 CVE-2018-3620 L1 Terminal Fault OS, SMM related aspects [all …]
|
| D | vmscape.rst | 1 .. SPDX-License-Identifier: GPL-2.0 10 guest-userspace may be able to attack the guest-kernel using the hypervisor as 14 ------------------- 19 - Skylake generation (Parts without Enhanced-IBRS) 20 - Cascade Lake generation - (Parts affected by ITS guest/host separation) 21 - Alder Lake and newer (Parts affected by BHI) 27 - Zen series (families 0x17, 0x19, 0x1a) 30 - Family 0x18 33 ---------- 36 ---------------- [all …]
|
| /Documentation/arch/x86/ |
| D | sgx.rst | 1 .. SPDX-License-Identifier: GPL-2.0 13 * Privileged (ring-0) ENCLS functions orchestrate the construction of the 15 * Unprivileged (ring-3) ENCLU functions allow an application to enter and 38 with an enclave. It is contained in a BIOS-reserved region of physical memory. 49 ------------------ 51 **SGX Enclave Control Structure (SECS)** 58 **Thread Control Structure (TCS)** 59 Thread Control Structure pages define the entry points to an enclave and 67 ---------------------- 76 remain read-only. EPCM permissions may only impose additional restrictions on [all …]
|
| /Documentation/networking/devlink/ |
| D | mlx5.rst | 1 .. SPDX-License-Identifier: GPL-2.0 13 .. list-table:: Generic parameters implemented 15 * - Name 16 - Mode 17 - Validation 18 * - ``enable_roce`` 19 - driverinit 20 - Type: Boolean 23 device support for RoCE capability. Otherwise, the control occurs in the 26 * - ``io_eq_size`` [all …]
|
| /Documentation/driver-api/dmaengine/ |
| D | dmatest.rst | 21 capability of the following: DMA_MEMCPY (memory-to-memory), DMA_MEMSET 22 (const-to-memory or memory-to-memory, when emulated), DMA_XOR, DMA_PQ. 28 Part 1 - How to build the test module 33 Device Drivers -> DMA Engine support -> DMA Test client 38 Part 2 - When dmatest is built as a module 43 % modprobe dmatest timeout=2000 iterations=1 channel=dma0chan0 run=1 51 % echo 1 > /sys/module/dmatest/parameters/run 55 dmatest.timeout=2000 dmatest.iterations=1 dmatest.channel=dma0chan0 dmatest.run=1 57 Example of multi-channel test usage (new in the 5.0 kernel):: 65 % echo 1 > /sys/module/dmatest/parameters/run [all …]
|
12345678910>>...13