Searched +full:sleep +full:- +full:hardware +full:- +full:state (Results 1 – 25 of 1017) sorted by relevance
12345678910>>...41
| /kernel/linux/linux-4.19/tools/power/cpupower/man/ |
| D | cpupower-idle-info.1 | 1 .TH "CPUPOWER-IDLE-INFO" "1" "0.1" "" "cpupower Manual"
4 cpupower\-idle\-info \- Utility to retrieve cpu idle kernel information
7 cpupower [ \-c cpulist ] idle\-info [\fIoptions\fP]
14 \fB\-f\fR \fB\-\-silent\fR
15 Only print a summary of all available C-states in the system.
17 \fB\-e\fR \fB\-\-proc\fR
23 .SH IDLE\-INFO DESCRIPTIONS
24 CPU sleep state statistics and descriptions are retrieved from sysfs files,
26 statistics when it enters or leaves an idle state, therefore on a very idle or
28 good overview about the usage and availability of processor sleep states on
[all …]
|
| D | cpupower-monitor.1 | 1 .TH CPUPOWER\-MONITOR "1" "22/02/2011" "" "cpupower Manual"
3 cpupower\-monitor \- Report processor frequency and idle statistics
7 .RB "\-l"
10 .RB [ -c ] [ "\-m <mon1>," [ "<mon2>,..." ] ]
11 .RB [ "\-i seconds" ]
14 .RB [ -c ][ "\-m <mon1>," [ "<mon2>,..." ] ]
18 \fBcpupower-monitor \fP reports processor topology, frequency and idle power
19 state statistics. Either \fBcommand\fP is forked and
22 \fBcpupower-monitor \fP implements independent processor sleep state and
24 directly reading out hardware registers. Use \-l to get an overview which are
[all …]
|
| /kernel/linux/linux-5.10/tools/power/cpupower/man/ |
| D | cpupower-idle-info.1 | 1 .TH "CPUPOWER-IDLE-INFO" "1" "0.1" "" "cpupower Manual"
4 cpupower\-idle\-info \- Utility to retrieve cpu idle kernel information
7 cpupower [ \-c cpulist ] idle\-info [\fIoptions\fP]
14 \fB\-f\fR \fB\-\-silent\fR
15 Only print a summary of all available C-states in the system.
17 \fB\-e\fR \fB\-\-proc\fR
23 .SH IDLE\-INFO DESCRIPTIONS
24 CPU sleep state statistics and descriptions are retrieved from sysfs files,
26 statistics when it enters or leaves an idle state, therefore on a very idle or
28 good overview about the usage and availability of processor sleep states on
[all …]
|
| D | cpupower-monitor.1 | 1 .TH CPUPOWER\-MONITOR "1" "22/02/2011" "" "cpupower Manual"
3 cpupower\-monitor \- Report processor frequency and idle statistics
7 .RB "\-l"
10 .RB [ -c ] [ "\-m <mon1>," [ "<mon2>,..." ] ]
11 .RB [ "\-i seconds" ]
14 .RB [ -c ][ "\-m <mon1>," [ "<mon2>,..." ] ]
18 \fBcpupower-monitor \fP reports processor topology, frequency and idle power
19 state statistics. Either \fBcommand\fP is forked and
22 \fBcpupower-monitor \fP implements independent processor sleep state and
24 directly reading out hardware registers. Use \-l to get an overview which are
[all …]
|
| /kernel/linux/linux-5.10/Documentation/admin-guide/pm/ |
| D | cpuidle.rst | 1 .. SPDX-License-Identifier: GPL-2.0
23 Since part of the processor hardware is not used in idle states, entering them
27 CPU idle time management is an energy-efficiency feature concerned about using
31 ------------
37 software as individual single-core processors. In other words, a CPU is an
43 program) at a time, it is a CPU. In that case, if the hardware is asked to
44 enter an idle state, that applies to the processor as a whole.
46 Second, if the processor is multi-core, each core in it is able to follow at
51 time. The entire cores are CPUs in that case and if the hardware is asked to
52 enter an idle state, that applies to the core that asked for it in the first
[all …]
|
| D | suspend-flows.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 At least one global system-wide transition needs to be carried out for the
13 system to get from the working state into one of the supported
14 :doc:`sleep states <sleep-states>`. Hibernation requires more than one
15 transition to occur for this purpose, but the other sleep states, commonly
16 referred to as *system-wide suspend* (or simply *system suspend*) states, need
19 For those sleep states, the transition from the working state of the system into
20 the target sleep state is referred to as *system suspend* too (in the majority
21 of cases, whether this means a transition or a sleep state of the system should
22 be clear from the context) and the transition back from the sleep state into the
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/pinctrl/ |
| D | sprd,sc9860-pinctrl.txt | 7 - compatible: Must be "sprd,sc9860-pinctrl".
8 - reg: The register address of pin controller device.
9 - pins : An array of strings, each string containing the name of a pin.
12 - function: A string containing the name of the function, values must be
14 - drive-strength: Drive strength in mA. Supported values: 2, 4, 6, 8, 10,
16 - input-schmitt-disable: Enable schmitt-trigger mode.
17 - input-schmitt-enable: Disable schmitt-trigger mode.
18 - bias-disable: Disable pin bias.
19 - bias-pull-down: Pull down on pin.
20 - bias-pull-up: Pull up on pin. Supported values: 20000 for pull-up resistor
[all …]
|
| D | sprd,pinctrl.txt | 16 of them, so we can not make every Spreadtrum-special configuration
29 to configure the pin sleep mode, function select and sleep related
32 Now we have 4 systems for sleep mode on SC9860 SoC: AP system,
33 PUBCP system, TGLDSP system and AGDSP system. And the pin sleep
35 - input-enable
36 - input-disable
37 - output-high
38 - output-low
39 - bias-pull-up
40 - bias-pull-down
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | sprd,sc9860-pinctrl.txt | 7 - compatible: Must be "sprd,sc9860-pinctrl".
8 - reg: The register address of pin controller device.
9 - pins : An array of strings, each string containing the name of a pin.
12 - function: A string containing the name of the function, values must be
14 - drive-strength: Drive strength in mA. Supported values: 2, 4, 6, 8, 10,
16 - input-schmitt-disable: Enable schmitt-trigger mode.
17 - input-schmitt-enable: Disable schmitt-trigger mode.
18 - bias-disable: Disable pin bias.
19 - bias-pull-down: Pull down on pin.
20 - bias-pull-up: Pull up on pin. Supported values: 20000 for pull-up resistor
[all …]
|
| D | sprd,pinctrl.txt | 16 of them, so we can not make every Spreadtrum-special configuration
29 to configure the pin sleep mode, function select and sleep related
32 Now we have 4 systems for sleep mode on SC9860 SoC: AP system,
33 PUBCP system, TGLDSP system and AGDSP system. And the pin sleep
35 - input-enable
36 - input-disable
37 - output-high
38 - output-low
39 - bias-pull-up
40 - bias-pull-down
[all …]
|
| D | pincfg-node.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only
3 ---
4 $id: http://devicetree.org/schemas/pinctrl/pincfg-node.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
16 for all hardware or binding structures. Each individual binding document
17 should state which of these generic properties, if any, are used, and the
21 bias-disable:
25 bias-high-impedance:
27 description: high impedance mode ("third-state", "floating")
[all …]
|
| /kernel/linux/linux-4.19/Documentation/serial/ |
| D | driver | 3 --------------------
14 Low Level Serial Hardware Driver
15 --------------------------------
17 The low level serial hardware driver is responsible for supplying port
25 ---------------
38 -------
40 It is the responsibility of the low level hardware driver to perform the
41 necessary locking using port->lock. There are some exceptions (which
44 There are two locks. A per-port spinlock, and an overall semaphore.
46 From the core driver perspective, the port->lock locks the following
[all …]
|
| /kernel/linux/linux-4.19/Documentation/driver-api/pm/ |
| D | devices.rst | 15 Copyright (c) 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
20 management (PM) code is also driver-specific. Most drivers will do very
24 This writeup gives an overview of how drivers interact with system-wide
27 background for the domain-specific work you'd do with any specific driver.
33 Drivers will use one or both of these models to put devices into low-power
36 System Sleep model:
38 Drivers can enter low-power states as part of entering system-wide
39 low-power states like "suspend" (also known as "suspend-to-RAM"), or
41 "suspend-to-disk").
44 by implementing various role-specific suspend and resume methods to
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/serial/ |
| D | driver.rst | 10 The reference implementation is contained within amba-pl011.c.
14 Low Level Serial Hardware Driver
15 --------------------------------
17 The low level serial hardware driver is responsible for supplying port
25 ---------------
38 -------
40 It is the responsibility of the low level hardware driver to perform the
41 necessary locking using port->lock. There are some exceptions (which
44 There are two locks. A per-port spinlock, and an overall semaphore.
46 From the core driver perspective, the port->lock locks the following
[all …]
|
| /kernel/linux/linux-5.10/Documentation/driver-api/pm/ |
| D | devices.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 :Copyright: |copy| 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
18 management (PM) code is also driver-specific. Most drivers will do very
22 This writeup gives an overview of how drivers interact with system-wide
25 background for the domain-specific work you'd do with any specific driver.
31 Drivers will use one or both of these models to put devices into low-power
34 System Sleep model:
36 Drivers can enter low-power states as part of entering system-wide
37 low-power states like "suspend" (also known as "suspend-to-RAM"), or
39 "suspend-to-disk").
[all …]
|
| /kernel/linux/linux-4.19/include/linux/ |
| D | hwspinlock.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Hardware spinlock public header
5 * Copyright (C) 2010 Texas Instruments Incorporated - http://www.ti.com
7 * Contact: Ohad Ben-Cohen <ohad@wizery.com>
17 #define HWLOCK_IRQSTATE 0x01 /* Disable interrupts, save state */
18 #define HWLOCK_IRQ 0x02 /* Disable interrupts, don't save state */
28 * struct hwspinlock_pdata - platform data for hwspinlock drivers
31 * hwspinlock devices provide system-wide hardware locks that are used
34 * To achieve that, each physical lock must have a system-wide id number
36 * they're using the same hardware lock.
[all …]
|
| /kernel/linux/linux-5.10/Documentation/locking/ |
| D | hwspinlock.rst | 2 Hardware Spinlock Framework
8 Hardware spinlock modules provide hardware assistance for synchronization
12 For example, OMAP4 has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP,
17 A generic hwspinlock framework allows platform-independent drivers to use
22 This is necessary, for example, for Inter-processor communications:
23 on OMAP4, cpu-intensive multimedia tasks are offloaded by the host to the
26 To achieve fast message-based communications, a minimal kernel support
35 A common hwspinlock interface makes it possible to have generic, platform-
50 Should be called from a process context (might sleep).
61 Should be called from a process context (might sleep).
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ |
| D | hwspinlock.txt | 2 Hardware Spinlock Framework
8 Hardware spinlock modules provide hardware assistance for synchronization
12 For example, OMAP4 has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP,
17 A generic hwspinlock framework allows platform-independent drivers to use
22 This is necessary, for example, for Inter-processor communications:
23 on OMAP4, cpu-intensive multimedia tasks are offloaded by the host to the
26 To achieve fast message-based communications, a minimal kernel support
35 A common hwspinlock interface makes it possible to have generic, platform-
50 Should be called from a process context (might sleep).
61 Should be called from a process context (might sleep).
[all …]
|
| /kernel/linux/linux-5.10/include/linux/ |
| D | hwspinlock.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
3 * Hardware spinlock public header
5 * Copyright (C) 2010 Texas Instruments Incorporated - http://www.ti.com
7 * Contact: Ohad Ben-Cohen <ohad@wizery.com>
17 #define HWLOCK_IRQSTATE 0x01 /* Disable interrupts, save state */
18 #define HWLOCK_IRQ 0x02 /* Disable interrupts, don't save state */
29 * struct hwspinlock_pdata - platform data for hwspinlock drivers
32 * hwspinlock devices provide system-wide hardware locks that are used
35 * To achieve that, each physical lock must have a system-wide id number
37 * they're using the same hardware lock.
[all …]
|
| /kernel/linux/linux-4.19/arch/arm/mach-omap2/ |
| D | clockdomain.c | 4 * Copyright (C) 2008-2011 Texas Instruments, Inc.
5 * Copyright (C) 2008-2011 Nokia Corporation
25 #include <linux/clk-provider.h>
59 if (!strcmp(name, temp_clkdm->name)) { in _clkdm_lookup()
69 * _clkdm_register - register a clockdomain
73 * Returns -EINVAL if given a null pointer, -EEXIST if a clockdomain is
80 if (!clkdm || !clkdm->name) in _clkdm_register()
81 return -EINVAL; in _clkdm_register()
83 pwrdm = pwrdm_lookup(clkdm->pwrdm.name); in _clkdm_register()
86 clkdm->name, clkdm->pwrdm.name); in _clkdm_register()
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-omap2/ |
| D | clockdomain.c | 1 // SPDX-License-Identifier: GPL-2.0-only
5 * Copyright (C) 2008-2011 Texas Instruments, Inc.
6 * Copyright (C) 2008-2011 Nokia Corporation
22 #include <linux/clk-provider.h>
56 if (!strcmp(name, temp_clkdm->name)) { in _clkdm_lookup()
66 * _clkdm_register - register a clockdomain
70 * Returns -EINVAL if given a null pointer, -EEXIST if a clockdomain is
77 if (!clkdm || !clkdm->name) in _clkdm_register()
78 return -EINVAL; in _clkdm_register()
80 pwrdm = pwrdm_lookup(clkdm->pwrdm.name); in _clkdm_register()
[all …]
|
| /kernel/linux/linux-4.19/Documentation/ABI/testing/ |
| D | sysfs-devices-power | 15 from sleep states, such as the memory sleep state (suspend to
19 Some devices support "wakeup" events, which are hardware signals
20 used to activate the system from a sleep state. Such devices
33 be enabled to wake up the system from sleep states.
40 space to control the run-time power management of the device.
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
87 the system from sleep states, this attribute is not present.
88 If the device is not enabled to wake up the system from sleep
98 is read-only. If the device is not capable to wake up the
[all …]
|
| /kernel/linux/linux-5.10/Documentation/ABI/testing/ |
| D | sysfs-devices-power | 15 from sleep states, such as the memory sleep state (suspend to
19 Some devices support "wakeup" events, which are hardware signals
20 used to activate the system from a sleep state. Such devices
33 be enabled to wake up the system from sleep states.
40 space to control the run-time power management of the device.
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
87 the system from sleep states, this attribute is not present.
88 If the device is not enabled to wake up the system from sleep
98 is read-only. If the device is not capable to wake up the
[all …]
|
| /kernel/linux/linux-4.19/Documentation/devicetree/bindings/mfd/ |
| D | max77620.txt | 4 -------------------
5 - compatible: Must be one of
8 - reg: I2C device address.
11 -------------------
12 - interrupts: The interrupt on the parent the controller is
14 - interrupt-controller: Marks the device node as an interrupt controller.
15 - #interrupt-cells: is <2> and their usage is compliant to the 2 cells
16 variant of <../interrupt-controller/interrupts.txt>
18 are defined at dt-bindings/mfd/max77620.h.
24 --------------------------------------
[all …]
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/ |
| D | max77620.txt | 4 -------------------
5 - compatible: Must be one of
9 - reg: I2C device address.
12 -------------------
13 - interrupts: The interrupt on the parent the controller is
15 - interrupt-controller: Marks the device node as an interrupt controller.
16 - #interrupt-cells: is <2> and their usage is compliant to the 2 cells
17 variant of <../interrupt-controller/interrupts.txt>
19 are defined at dt-bindings/mfd/max77620.h.
21 - system-power-controller: Indicates that this PMIC is controlling the
[all …]
|
12345678910>>...41