| /kernel/linux/linux-5.10/Documentation/trace/ |
| D | events-power.rst | 5 The power tracing system captures events related to power transitions
8 - Power state switch which reports events related to suspend (S-states),
9 cpuidle (C-states) and cpufreq (P-states)
10 - System clock related changes
11 - Power domains related changes and transitions
22 -----------------
24 A 'cpu' event class gathers the CPU-related events: cpuidle and
39 Note: the value of '-1' or '4294967295' for state means an exit from the current state,
72 4. PM QoS events
74 The PM QoS events are used for QoS add/update/remove request and for
[all …]
|
| /kernel/linux/linux-6.6/Documentation/trace/ |
| D | events-power.rst | 5 The power tracing system captures events related to power transitions
8 - Power state switch which reports events related to suspend (S-states),
9 cpuidle (C-states) and cpufreq (P-states)
10 - System clock related changes
11 - Power domains related changes and transitions
22 -----------------
24 A 'cpu' event class gathers the CPU-related events: cpuidle and
39 Note: the value of '-1' or '4294967295' for state means an exit from the current state,
72 4. PM QoS events
74 The PM QoS events are used for QoS add/update/remove request and for
[all …]
|
| /kernel/linux/linux-6.6/Documentation/power/ |
| D | drivers-testing.rst | 10 Unfortunately, to effectively test the support for the system-wide suspend and
20 resolve all suspend/resume-related problems in the test system before you start
21 testing the new driver. Please see Documentation/power/basic-pm-debugging.rst
27 Once you have resolved the suspend/resume-related problems with your test system
31 (see: Documentation/power/basic-pm-debugging.rst, 1).
34 "platform" modes (see: Documentation/power/basic-pm-debugging.rst, 1).
43 Documentation/power/basic-pm-debugging.rst, 2). [As far as the STR tests are
48 (see: Documentation/power/basic-pm-debugging.rst, 2).
52 regarded as suspend/resume-safe.
|
| D | pci.rst | 7 An overview of concepts and the Linux kernel's interfaces related to PCI power
12 devices. For general description of the kernel's interfaces related to device
13 power management refer to Documentation/driver-api/pm/devices.rst and
27 1.1. Native and Platform-Based Power Management
28 -----------------------------------------------
31 devices into states in which they draw less power (low-power states) at the
34 Usually, a device is put into a low-power state when it is underutilized or
36 again, it has to be put back into the "fully functional" state (full-power
41 PCI devices may be put into low-power states in two ways, by using the device
44 approach, that is referred to as the native PCI power management (native PCI PM)
[all …]
|
| D | freezing-of-tasks.rst | 11 kernel threads are controlled during hibernation or system-wide suspend (on some
17 There are three per-task flags used for that, PF_NOFREEZE, PF_FROZEN
25 freeze_processes() (defined in kernel/power/process.c) is called. A system-wide
26 variable system_freezing_cnt (as opposed to a per-task flag) is used to indicate
44 signal-handling code, but the freezable kernel threads need to call it
74 -------------------------------------------------------------------------
77 - freezes only userspace tasks
80 - freezes all tasks (including kernel threads) because we can't freeze
84 - thaws only kernel threads; this is particularly useful if we need to do
89 - thaws all tasks (including kernel threads) because we can't thaw userspace
[all …]
|
| /kernel/linux/linux-5.10/Documentation/power/ |
| D | drivers-testing.rst | 10 Unfortunately, to effectively test the support for the system-wide suspend and
20 resolve all suspend/resume-related problems in the test system before you start
21 testing the new driver. Please see Documentation/power/basic-pm-debugging.rst
27 Once you have resolved the suspend/resume-related problems with your test system
31 (see: Documentation/power/basic-pm-debugging.rst, 1).
34 "platform" modes (see: Documentation/power/basic-pm-debugging.rst, 1).
43 Documentation/power/basic-pm-debugging.rst, 2). [As far as the STR tests are
48 (see: Documentation/power/basic-pm-debugging.rst, 2).
52 regarded as suspend/resume-safe.
|
| D | pci.rst | 7 An overview of concepts and the Linux kernel's interfaces related to PCI power
12 devices. For general description of the kernel's interfaces related to device
13 power management refer to Documentation/driver-api/pm/devices.rst and
27 1.1. Native and Platform-Based Power Management
28 -----------------------------------------------
31 devices into states in which they draw less power (low-power states) at the
34 Usually, a device is put into a low-power state when it is underutilized or
36 again, it has to be put back into the "fully functional" state (full-power
41 PCI devices may be put into low-power states in two ways, by using the device
44 approach, that is referred to as the native PCI power management (native PCI PM)
[all …]
|
| D | freezing-of-tasks.rst | 11 kernel threads are controlled during hibernation or system-wide suspend (on some
17 There are three per-task flags used for that, PF_NOFREEZE, PF_FROZEN
25 freeze_processes() (defined in kernel/power/process.c) is called. A system-wide
26 variable system_freezing_cnt (as opposed to a per-task flag) is used to indicate
44 signal-handling code, but the freezable kernel threads need to call it
74 -------------------------------------------------------------------------
77 - freezes only userspace tasks
80 - freezes all tasks (including kernel threads) because we can't freeze
84 - thaws only kernel threads; this is particularly useful if we need to do
89 - thaws all tasks (including kernel threads) because we can't thaw userspace
[all …]
|
| D | runtime_pm.rst | 5 (C) 2009-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
14 Support for runtime power management (runtime PM) of I/O devices is provided
15 at the power management core (PM core) level by means of:
18 put their PM-related work items. It is strongly recommended that pm_wq be
19 used for queuing all work items related to runtime PM, because this allows
20 them to be synchronized with system-wide power transitions (suspend to RAM,
24 * A number of runtime PM fields in the 'power' member of 'struct device' (which
25 is of the type 'struct dev_pm_info', defined in include/linux/pm.h) that can
26 be used for synchronizing runtime PM operations with one another.
28 * Three device runtime PM callbacks in 'struct dev_pm_ops' (defined in
[all …]
|
| /kernel/linux/linux-6.6/drivers/gpu/drm/msm/dp/ |
| D | dp_power.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * Copyright (c) 2012-2020, The Linux Foundation. All rights reserved.
12 * sruct dp_power - DisplayPort's power related data
26 * dp_power_init() - enable power supplies for display controller
37 * dp_power_deinit() - turn off regulators and gpios.
47 * dp_power_clk_status() - display controller clocks status
50 * @pm_type: type of pm, core/ctrl/phy
59 * dp_power_clk_enable() - enable display controller clocks
62 * @pm_type: type of pm, core/ctrl/phy
73 * dp_power_client_init() - initialize clock and regulator modules
[all …]
|
| /kernel/linux/linux-5.10/drivers/gpu/drm/msm/dp/ |
| D | dp_power.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
3 * Copyright (c) 2012-2020, The Linux Foundation. All rights reserved.
12 * sruct dp_power - DisplayPort's power related data
26 * dp_power_init() - enable power supplies for display controller
38 * dp_power_deinit() - turn off regulators and gpios.
48 * dp_power_clk_status() - display controller clocks status
51 * @pm_type: type of pm, core/ctrl/phy
60 * dp_power_clk_enable() - enable display controller clocks
63 * @pm_type: type of pm, core/ctrl/phy
74 * dp_power_client_init() - initialize clock and regulator modules
[all …]
|
| /kernel/linux/linux-6.6/Documentation/trace/coresight/ |
| D | coresight-cpu-debug.rst | 9 ------------
11 Coresight CPU debug module is defined in ARMv8-a architecture reference manual
13 debug module and it is mainly used for two modes: self-hosted debug and
16 explore debugging method which rely on self-hosted debug mode, this document
19 The debug module provides sample-based profiling extension, which can be used
21 every CPU has one dedicated debug module to be connected. Based on self-hosted
22 debug mechanism, Linux kernel can access these related registers from mmio
24 will dump related registers for every CPU; finally this is good for assistant
29 --------------
31 - During driver registration, it uses EDDEVID and EDDEVID1 - two device ID
[all …]
|
| /kernel/linux/linux-5.10/Documentation/trace/coresight/ |
| D | coresight-cpu-debug.rst | 9 ------------
11 Coresight CPU debug module is defined in ARMv8-a architecture reference manual
13 debug module and it is mainly used for two modes: self-hosted debug and
16 explore debugging method which rely on self-hosted debug mode, this document
19 The debug module provides sample-based profiling extension, which can be used
21 every CPU has one dedicated debug module to be connected. Based on self-hosted
22 debug mechanism, Linux kernel can access these related registers from mmio
24 will dump related registers for every CPU; finally this is good for assistant
29 --------------
31 - During driver registration, it uses EDDEVID and EDDEVID1 - two device ID
[all …]
|
| /kernel/liteos_m/components/power/ |
| D | los_pm.h | 2 * Copyright (c) 2013-2019 Huawei Technologies Co., Ltd. All rights reserved.
3 * Copyright (c) 2020-2021 Huawei Device Co., Ltd. All rights reserved.
42 * Pm error code: Invalid low-power mode.
51 * Pm error code: Invalid input parameter.
60 * Pm error code: The current mode is unlocked.
69 * Pm error code: The lock limit has been exceeded.
78 * Pm error code: Invalid device node.
87 * Pm error code: Invalid type.
96 * Pm error code: The hook for mode is not implemented.
105 * Pm error code: Deep and shutdown must implement the Tick Timer related interface.
[all …]
|
| /kernel/linux/linux-6.6/arch/arm/mach-omap2/ |
| D | pm.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * pm.c - Common OMAP2+ power management-related code
25 #include "prcm-common.h"
29 #include "pm.h"
35 * omap_pm_suspend: points to a function that does the SoC-specific
43 * struct omap2_oscillator - Describe the board main oscillator latencies
79 return -ENOENT; /* XXX doublecheck */ in omap_pm_enter()
86 ret = -EINVAL; in omap_pm_enter()
120 * omap_common_suspend_init - Set common suspend routines for OMAP SoCs
155 pr_warn("%s: pm soc init failed: %i\n", __func__, error); in omap2_common_pm_late_init()
|
| /kernel/linux/linux-6.6/drivers/soc/mediatek/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
58 select PM_GENERIC_DOMAINS if PM
66 depends on PM
72 Control Processor System (SCPSYS) has several power management related
|
| /kernel/linux/linux-6.6/block/ |
| D | blk-pm.c | 1 // SPDX-License-Identifier: GPL-2.0
3 #include <linux/blk-pm.h>
6 #include "blk-mq.h"
9 * blk_pm_runtime_init - Block layer runtime PM initialization routine
14 * Initialize runtime-PM-related fields for @q and start auto suspend for
15 * @dev. Drivers that want to take advantage of request-based runtime PM
17 * request queue @q has been allocated, and runtime PM for it can not happen
22 * the autosuspend delay is set to -1 to make runtime suspend impossible
26 * The block layer runtime PM is request based, so only works for drivers
31 q->dev = dev; in blk_pm_runtime_init()
[all …]
|
| /kernel/linux/linux-5.10/Documentation/sound/soc/ |
| D | machine.rst | 12 the following struct:-
24 /* the pre and post PM functions are used to do any PM work before and
25 * after the codec and DAIs do any PM work. */
33 /* CPU <--> Codec DAI links */
41 ----------------
46 ------------------
53 -------------------------
55 also be used to set up the DAI system clock and for any machine related DAI
62 /* corgi digital audio interface glue - connects codec <--> CPU */
66 .cpu_dai_name = "pxa-is2-dai",
[all …]
|
| /kernel/linux/linux-6.6/Documentation/sound/soc/ |
| D | machine.rst | 12 the following struct:-
24 /* the pre and post PM functions are used to do any PM work before and
25 * after the codec and DAIs do any PM work. */
33 /* CPU <--> Codec DAI links */
41 ----------------
46 ------------------
53 -------------------------
55 also be used to set up the DAI system clock and for any machine related DAI
62 /* corgi digital audio interface glue - connects codec <--> CPU */
66 .cpu_dai_name = "pxa-is2-dai",
[all …]
|
| /kernel/linux/linux-5.10/arch/arm/mach-omap2/ |
| D | pm.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * pm.c - Common OMAP2+ power management-related code
25 #include "prcm-common.h"
29 #include "pm.h"
35 * omap_pm_suspend: points to a function that does the SoC-specific
43 * struct omap2_oscillator - Describe the board main oscillator latencies
85 return -ENOENT; /* XXX doublecheck */ in omap_pm_enter()
92 ret = -EINVAL; in omap_pm_enter()
126 * omap_common_suspend_init - Set common suspend routines for OMAP SoCs
161 pr_warn("%s: pm soc init failed: %i\n", __func__, error); in omap2_common_pm_late_init()
|
| /kernel/linux/linux-5.10/block/ |
| D | blk-pm.c | 1 // SPDX-License-Identifier: GPL-2.0
3 #include <linux/blk-mq.h>
4 #include <linux/blk-pm.h>
7 #include "blk-mq.h"
8 #include "blk-mq-tag.h"
11 * blk_pm_runtime_init - Block layer runtime PM initialization routine
16 * Initialize runtime-PM-related fields for @q and start auto suspend for
17 * @dev. Drivers that want to take advantage of request-based runtime PM
19 * request queue @q has been allocated, and runtime PM for it can not happen
24 * the autosuspend delay is set to -1 to make runtime suspend impossible
[all …]
|
| /kernel/linux/linux-6.6/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
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").
42 by implementing various role-specific suspend and resume methods to
[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
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").
42 by implementing various role-specific suspend and resume methods to
[all …]
|
| /kernel/linux/linux-6.6/kernel/power/ |
| D | qos.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * Power Management Quality of Service (PM QoS) support base.
11 * Provided here is an interface for specifying PM QoS dependencies. It allows
15 * or through a built-in notification mechanism.
50 * pm_qos_read_value - Return the current effective constraint value.
51 * @c: List of PM QoS constraint requests.
55 return READ_ONCE(c->target_value); in pm_qos_read_value()
60 if (plist_head_empty(&c->list)) in pm_qos_get_value()
61 return c->no_constraint_value; in pm_qos_get_value()
63 switch (c->type) { in pm_qos_get_value()
[all …]
|
| /kernel/linux/linux-5.10/kernel/power/ |
| D | qos.c | 1 // SPDX-License-Identifier: GPL-2.0-only
3 * Power Management Quality of Service (PM QoS) support base.
11 * Provided here is an interface for specifying PM QoS dependencies. It allows
15 * or through a built-in notification mechanism.
50 * pm_qos_read_value - Return the current effective constraint value.
51 * @c: List of PM QoS constraint requests.
55 return READ_ONCE(c->target_value); in pm_qos_read_value()
60 if (plist_head_empty(&c->list)) in pm_qos_get_value()
61 return c->no_constraint_value; in pm_qos_get_value()
63 switch (c->type) { in pm_qos_get_value()
[all …]
|