| /Linux-v4.19/Documentation/devicetree/bindings/arm/ux500/ |
| D | power_domain.txt | 1 * ST-Ericsson UX500 PM Domains
3 UX500 supports multiple PM domains which are used to gate power to one or
6 The implementation of PM domains for UX500 are based upon the generic PM domain
9 ==PM domain providers==
21 ==PM domain consumers==
24 - power-domains: A phandle and PM domain specifier. Below are the list of
|
| /Linux-v4.19/Documentation/devicetree/bindings/power/ |
| D | power_domain.txt | 1 * Generic PM domains
3 System on chip designs are often divided into multiple PM domains that can be
7 This device tree binding can be used to bind PM domain consumer devices with
8 their PM domains provided by PM domain providers. A PM domain provider can be
9 represented by any node in the device tree and can provide one or more PM
11 phandle arguments (so called PM domain specifiers) of length specified by the
12 #power-domain-cells property in the PM domain provider node.
14 ==PM domain providers==
17 - #power-domain-cells : Number of cells in a PM domain specifier;
18 Typically 0 for nodes representing a single PM domain and 1 for nodes
[all …]
|
| D | renesas,sysc-rmobile.txt | 23 - pm-domains: This node contains a hierarchy of PM domain nodes, which should
28 == PM Domain Nodes ==
30 Each of the PM domain nodes represents a PM domain, as documented by the
31 generic PM domain bindings in
41 - reg: If the PM domain is not always-on, this property must contain the bit
47 If the PM domain is always-on, this property must be omitted.
52 This shows a subset of the r8a7740 PM domain hierarchy, containing the
87 == PM Domain Consumers ==
89 Hardware blocks belonging to a PM domain should contain a "power-domains"
90 property that is a phandle pointing to the corresponding PM domain node.
|
| D | renesas,rcar-sysc.txt | 39 == PM Domain Consumers ==
42 by the generic PM domain bindings in
46 - power-domains: A phandle and symbolic PM domain specifier, as defined in
|
| /Linux-v4.19/Documentation/arm/OMAP/ |
| D | omap_pm | 2 The OMAP PM interface
5 This document describes the temporary OMAP PM interface. Driver
8 Over time, the intention is to merge features from the OMAP PM
9 interface into the Linux PM QoS code.
11 Drivers need to express PM parameters which:
15 - separate the drivers from the underlying PM parameter
16 implementation, whether it is the TI SRF or Linux PM QoS or Linux
19 - specify PM parameters in terms of fundamental units, such as
31 This document proposes the OMAP PM interface, including the following
50 Further documentation for all OMAP PM interface functions can be
[all …]
|
| /Linux-v4.19/Documentation/power/ |
| D | runtime_pm.txt | 9 Support for runtime power management (runtime PM) of I/O devices is provided
10 at the power management core (PM core) level by means of:
13 put their PM-related work items. It is strongly recommended that pm_wq be
14 used for queuing all work items related to runtime PM, because this allows
19 * A number of runtime PM fields in the 'power' member of 'struct device' (which
21 be used for synchronizing runtime PM operations with one another.
23 * Three device runtime PM callbacks in 'struct dev_pm_ops' (defined in
27 used for carrying out runtime PM operations in such a way that the
28 synchronization between them is taken care of by the PM core. Bus types and
31 The runtime PM callbacks present in 'struct dev_pm_ops', the device runtime PM
[all …]
|
| D | pm_qos_interface.txt | 1 PM Quality Of Service Interface.
7 Two different PM QoS frameworks are available:
8 1. PM QoS classes for cpu_dma_latency, network_latency, network_throughput,
10 2. the per-device PM QoS framework provides the API to manage the per-device latency
11 constraints and PM QoS flags.
20 1. PM QoS framework
40 Will insert an element into the list for that identified PM QoS class with the
57 Returns the aggregated value for a given PM QoS class.
61 PM QoS class constraints list.
64 Adds a notification callback function to the PM QoS class. The callback is
[all …]
|
| D | pci.txt | 41 approach, that is referred to as the native PCI power management (native PCI PM)
47 Devices supporting the native PCI PM usually can generate wakeup signals called
62 native PCI PM mechanism, because the method provided by the platform depends on
70 The PCI Bus Power Management Interface Specification (PCI PM Spec) was
75 The implementation of the PCI PM Spec is optional for conventional PCI devices,
76 but it is mandatory for PCI Express devices. If a device supports the PCI PM
81 The PCI PM Spec defines 4 operating states for devices (D0-D3) and for buses
98 regardless of whether or not it implements the PCI PM Spec. In addition to
99 that, if the PCI PM Spec is implemented by the device, it must support D3hot
102 PCI devices supporting the PCI PM Spec can be programmed to go to any of the
[all …]
|
| /Linux-v4.19/Documentation/devicetree/bindings/soc/ti/ |
| D | sci-pm-domain.txt | 11 PM Domain Node
13 The PM domain node represents the global PM domain managed by the PMMC, which
14 in this case is the implementation as documented by the generic PM domain
37 PM Domain Consumers
39 Hardware blocks belonging to a PM domain should contain a "power-domains"
40 property that is a phandle pointing to the corresponding PM domain node
46 - power-domains: phandle pointing to the corresponding PM domain node
|
| /Linux-v4.19/arch/arm/mach-omap2/ |
| D | Kconfig | 15 select ARM_CPU_SUSPEND if PM
17 select PM_OPP if PM
18 select PM if CPU_IDLE
27 select ARM_CPU_SUSPEND if PM
36 select PM_OPP if PM
37 select PM if CPU_IDLE
46 select ARM_CPU_SUSPEND if PM
53 select PM_OPP if PM
60 select ARM_CPU_SUSPEND if PM
75 select ARM_CPU_SUSPEND if PM
[all …]
|
| /Linux-v4.19/arch/arm/mach-at91/ |
| D | Kconfig | 4 select ARM_CPU_SUSPEND if PM && ARCH_MULTI_V7
66 select ATMEL_PM if PM
72 select SRAM if PM
80 select ATMEL_PM if PM
90 select SRAM if PM
145 select ATMEL_PM if PM
149 select SRAM if PM
|
| /Linux-v4.19/Documentation/devicetree/bindings/bus/ |
| D | simple-pm-bus.txt | 7 However, its bus controller is part of a PM domain, or under the control of a
8 functional clock. Hence, the bus controller's PM domain and/or clock must be
24 Optional platform-specific properties for clock or PM domain control (at least
27 - power-domains: Must contain a reference to the PM domain.
28 Please refer to the binding documentation for the clock and/or PM domain
|
| D | renesas,bsc.txt | 9 While the BSC is a fairly simple memory-mapped bus, it may be part of a PM
11 Before a device connected to the BSC can be accessed, the PM domain
31 - power-domains: Must contain a reference to the PM domain, if available.
|
| /Linux-v4.19/Documentation/ABI/testing/ |
| D | sysfs-ata | 20 nr_pmp_links: (RO) If a SATA Port Multiplier (PM) is
40 Behind each port, there is a ata_link. If there is a SATA PM in the topology, 15
44 of the port. If a link is behind a PM, its name is linkX.Y where X is
45 ata_port_id of the parent port and Y the PM port.
70 - Y the port of the PM if any, and
89 gscr: (RO) Cached result of the dump of PM GSCR
101 Only valid if the device is a PM.
108 the device is not a PM.
119 "atapi" for packet device, "pmp" for PM, or
|
| /Linux-v4.19/arch/arm/plat-samsung/ |
| D | Kconfig | 16 depends on PM && (PLAT_S3C24XX || ARCH_S3C64XX)
231 default y if GPIO_SAMSUNG && PM
240 bool "Samsung PM Suspend debug"
241 depends on PM && DEBUG_KERNEL
244 Say Y here if you want verbose debugging from the PM Suspend and
250 depends on PM && (MACH_SMDK6410)
258 bool "S3C2410 PM Suspend Memory CRC"
259 depends on PM
262 Enable the PM code's memory area checksum over sleep. This option
273 int "S3C2410 PM Suspend CRC Chunksize (KiB)"
[all …]
|
| /Linux-v4.19/drivers/soc/imx/ |
| D | Kconfig | 4 bool "i.MX7 PM domains"
6 depends on PM
|
| /Linux-v4.19/kernel/configs/ |
| D | nopm.config | 5 # Triggers PM on OMAP
11 # ARM/ARM64 architectures that select PM unconditionally
|
| /Linux-v4.19/arch/arm/mach-shmobile/ |
| D | Kconfig | 6 select PM
11 select PM
19 select PM
53 select PM
|
| /Linux-v4.19/tools/perf/util/c++/ |
| D | clang.cpp | 148 legacy::PassManager PM; in getBPFObjectFromModule() local
151 NotAdded = TargetMachine->addPassesToEmitFile(PM, ostream, in getBPFObjectFromModule()
154 NotAdded = TargetMachine->addPassesToEmitFile(PM, ostream, nullptr, in getBPFObjectFromModule()
161 PM.run(*Module); in getBPFObjectFromModule()
|
| /Linux-v4.19/arch/arm/mach-mxs/ |
| D | Kconfig | 4 select ARM_CPU_SUSPEND if PM
11 select ARM_CPU_SUSPEND if PM
|
| /Linux-v4.19/Documentation/arm/SA1100/ |
| D | Assabet | 252 PM: Not tested.
253 COM: TX, RX, CTS, DSR, DCD, RTS, DTR, PM
254 PM: Not tested.
257 PM: Not tested.
260 LCD: Fully tested. PM
269 PM: Not tested.
278 PM: Not tested.
287 PM: Not tested.
292 PM: Not tested.
295 PM: Not tested.
[all …]
|
| /Linux-v4.19/Documentation/fault-injection/ |
| D | notifier-error-inject.txt | 9 * PM notifier
14 PM notifier error injection module
19 Possible PM notifier events to be failed are:
25 Example: Inject PM suspend error (-12 = -ENOMEM)
|
| /Linux-v4.19/Documentation/driver-api/pm/ |
| D | devices.rst | 20 management (PM) code is also driver-specific. Most drivers will do very
69 the PM core are involved in runtime power management. As in the system
78 synergies exist, so that several drivers using runtime PM might put the system
127 device drivers whose subsystems (PM domains, device types, device classes and
154 its system wakeup mechanism and for notifying the PM core of system wakeup
262 the device is suspending (i.e. has been chosen by the PM core as the next
281 All phases use PM domain, bus, type, class or driver callbacks (that is, methods
284 PM core as mutually exclusive. Moreover, PM domain callbacks always take
289 1. If ``dev->pm_domain`` is present, the PM core will choose the callback
302 This allows PM domains and device types to override callbacks provided by bus
[all …]
|
| /Linux-v4.19/arch/arm/mach-rockchip/ |
| D | Kconfig | 15 select REGULATOR if PM
20 select PM
|
| /Linux-v4.19/Documentation/devicetree/bindings/memory-controllers/ |
| D | renesas-memory-controllers.txt | 9 Currently memory controller device nodes are used only to reference PM
10 domains, and prevent these PM domains from being powered down, which would
32 - power-domains: Must contain a reference to the PM domain that the memory
|
