Home
last modified time | relevance | path

Searched refs:PM (Results 1 – 102 of 102) sorted by relevance

/linux-4.1.27/Documentation/devicetree/bindings/power/
Dpower_domain.txt1 * 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 …]
Drenesas,sysc-rmobile.txt23 - 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.
/linux-4.1.27/Documentation/devicetree/bindings/arm/ux500/
Dpower_domain.txt1 * 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-4.1.27/Documentation/arm/OMAP/
Domap_pm2 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-4.1.27/Documentation/power/
Druntime_pm.txt9 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 …]
Dpm_qos_interface.txt1 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 …]
Dpci.txt41 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 …]
Ddevices.txt9 management (PM) code is also driver-specific. Most drivers will do very
55 the PM core are involved in runtime power management. As in the system
64 synergies exist, so that several drivers using runtime PM might put the system
137 writers of device drivers whose subsystems (PM domains, device types, device
162 its system wakeup mechanism and for notifying the PM core of system wakeup
263 the device is suspending (i.e. has been chosen by the PM core as the next
280 All phases use PM domain, bus, type, class or driver callbacks (that is, methods
282 dev->driver->pm). These callbacks are regarded by the PM core as mutually
283 exclusive. Moreover, PM domain callbacks always take precedence over all of the
288 1. If dev->pm_domain is present, the PM core will choose the callback
[all …]
Dinterface.txt62 /sys/power/pm_trace controls the code which saves the last PM event point in
65 used to save the last PM event point if this file contains '1'. Initially it
D00-INDEX24 - info on Linux PM Quality of Service interface
Dnotifiers.txt16 will be called upon the following events by the PM core:
Dsuspend-and-interrupts.txt82 the PM core is notified about the event which causes the system suspend in
Dbasic-pm-debugging.txt17 modes causes the PM core to skip some platform-related callbacks which on ACPI
/linux-4.1.27/Documentation/ABI/testing/
Dsysfs-ata21 If a SATA Port Multiplier (PM) is connected, number of link behind it.
26 Behind each port, there is a ata_link. If there is a SATA PM in the
31 If a link is behind a PM, its name is linkX.Y where X is ata_port_id
32 of the parent port and Y the PM port.
52 - Y the port of the PM if any, and
58 "pmp" for PM, or "none" if no device was found behind the link.
77 Only valid if the device is not a PM.
81 Cached result of the dump of PM GSCR register.
91 Only valid if the device is a PM.
Dsysfs-devices-lpss_ltr18 This attribute is read-only. If the device's runtime PM status
30 This attribute is read-only. If the device's runtime PM status
42 This attribute is read-only. If the device's runtime PM status
Dsysfs-devices-power74 of a device unless it is certain that all of the PM dependencies
75 of the device are known to the PM core. However, for some
209 contains the PM QoS resume latency limit for the given device,
214 the PM QoS resume latency may be arbitrary.
227 contains the PM QoS active state latency tolerance limit for the
252 is used for manipulating the PM QoS "no power off" flag. If
267 is used for manipulating the PM QoS "remote wakeup required"
Dsysfs-power48 ACPI or other PM registers).
102 last PM event point in the RTC across reboots, so that you can
105 the last PM event point if this file contains '1'. Initially
115 positives), it is possible that the last PM event point
128 device associated with the last PM event point saved in the RTC
Dsysfs-firmware-acpi142 ff_pmtimer - PM Timer
Dsysfs-bus-usb108 in to a xHCI host which support link PM, it will perform a LPM
/linux-4.1.27/Documentation/frv/
Dclock.txt40 PM-Controls: cmode=0xd31f, cm=0x3, p0=0x3, suspend=0x9
41 PM-Status: cmode=3, cm=0, p0=0
51 And on the PDK, the PM lines look like the following:
53 PM-Controls: cm=0x3, p0=0x3, suspend=0x9
54 PM-Status: cmode=9, cm=0, p0=0
56 The PM-Controls line, if present, will indicate which /proc/sys/pm files can
61 The PM-Controls line will only be present if CONFIG_PM is configured to Y.
63 The PM-Status line indicates which clock controls are set to which value. If
/linux-4.1.27/Documentation/devicetree/bindings/bus/
Dsimple-pm-bus.txt7 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
Drenesas,bsc.txt9 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-4.1.27/arch/arm/mach-omap2/
DKconfig15 select ARM_CPU_SUSPEND if PM
17 select PM_OPP if PM
18 select PM if CPU_IDLE
26 select ARM_CPU_SUSPEND if PM
34 select PM_OPP if PM
35 select PM if CPU_IDLE
43 select ARM_CPU_SUSPEND if PM
54 select ARM_CPU_SUSPEND if PM
68 select ARM_CPU_SUSPEND if PM
108 select PM
/linux-4.1.27/arch/arm/plat-samsung/
DKconfig18 depends on PM && (PLAT_S3C24XX || ARCH_S3C64XX)
241 default y if GPIO_SAMSUNG && PM
256 bool "Samsung PM Suspend debug"
257 depends on PM && DEBUG_KERNEL
260 Say Y here if you want verbose debugging from the PM Suspend and
266 depends on PM && (MACH_SMDK6410)
274 bool "S3C2410 PM Suspend Memory CRC"
275 depends on PM
278 Enable the PM code's memory area checksum over sleep. This option
289 int "S3C2410 PM Suspend CRC Chunksize (KiB)"
[all …]
/linux-4.1.27/arch/arm/mach-mxs/
DKconfig4 select ARM_CPU_SUSPEND if PM
11 select ARM_CPU_SUSPEND if PM
/linux-4.1.27/Documentation/arm/SA1100/
DAssabet252 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-4.1.27/Documentation/devicetree/bindings/memory-controllers/
Drenesas-memory-controllers.txt9 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
/linux-4.1.27/arch/arm/mach-at91/
DKconfig42 select SRAM if PM
57 select SRAM if PM
105 select SRAM if PM
/linux-4.1.27/kernel/power/
DKconfig97 select PM
133 config PM config
148 depends on PM
151 code. This is helpful when debugging and reporting PM bugs, like
155 bool "Extra PM attributes in sysfs for low-level debugging/testing"
196 This enables code to save the last PM event point across
214 This enables some cheesy code to save the last PM event point in the
228 depends on PM && SYS_SUPPORTS_APM_EMULATION
268 depends on PM && HAVE_CLK
272 depends on PM
[all …]
/linux-4.1.27/Documentation/fault-injection/
Dnotifier-error-inject.txt10 * PM notifier
43 PM notifier error injection module
48 Possible PM notifier events to be failed are:
54 Example: Inject PM suspend error (-12 = -ENOMEM)
/linux-4.1.27/drivers/bus/
DKconfig96 depends on OF && PM
100 where the bus controller is part of a PM domain, or under the control
101 of a functional clock, and thus relies on runtime PM for managing
102 this PM domain and/or clock.
/linux-4.1.27/arch/arm/mach-exynos/
DKconfig24 select PM_GENERIC_DOMAINS if PM
35 select ARM_CPU_SUSPEND if PM
124 bool "Exynos5420 Multi-Cluster PM support"
/linux-4.1.27/drivers/ata/
Dpata_sch.c44 PM = 0x07, /* PIO Mode Bit Mask */ enumerator
119 data &= ~(PM | PPE); in sch_set_piomode()
DKconfig64 depends on ATA_ACPI && PM
/linux-4.1.27/Documentation/arm/Samsung-S3C24XX/
DSuspend.txt84 There are several important things to remember when using PM suspend:
107 `S3C2410 PM Suspend debug`
114 `S3C2410 PM Suspend Memory CRC`
126 `S3C2410 PM Suspend CRC Chunksize (KiB)`
/linux-4.1.27/arch/arm/mach-s3c24xx/
DKconfig33 select S3C2410_PM if PM
184 select S3C24XX_SIMTEC_PM if PM
197 select S3C24XX_SIMTEC_PM if PM
216 select PM_H1940 if PM
273 select S3C24XX_SIMTEC_PM if PM
443 select S3C24XX_SIMTEC_PM if PM
483 select S3C24XX_SIMTEC_PM if PM
505 select PM_H1940 if PM
550 select PM_H1940 if PM
586 Internal node for H1940 and related PM
/linux-4.1.27/Documentation/sound/alsa/soc/
Dmachine.txt22 /* the pre and post PM functions are used to do any PM work before and
23 * after the codec and DAIs do any PM work. */
Dcodec.txt140 This function is a callback that handles codec domain PM calls and system
141 domain PM calls (e.g. suspend and resume). It is used to put the codec
Ddapm.txt9 subsystem at all times. It is independent of other kernel PM and as
10 such, can easily co-exist with the other PM systems.
171 to any stream event or by kernel PM events.
276 Some widgets can register their interest with the DAPM core in PM events.
DDPCM.txt195 The BE has also flags set for ignoring suspend and PM down time. This allows
/linux-4.1.27/Documentation/usb/
Dpower-management.txt13 * Forms of dynamic PM
14 * The user interface for dynamic PM
21 * Interaction between dynamic PM and system PM
22 * xHCI hardware link PM
31 Power Management (PM) is the practice of saving energy by suspending
36 needs to use it. (There also are forms of PM in which components are
46 dynamic PM is implemented in the USB subsystem, although system PM is
48 information about system PM).
50 System PM support is present only if the kernel was built with CONFIG_SUSPEND
51 or CONFIG_HIBERNATION enabled. Dynamic PM support for USB is present whenever
[all …]
Dcallbacks.txt27 3. Power management (PM) callbacks:
40 reason. Sysfs is preferred these days. The PM callbacks are covered
/linux-4.1.27/arch/arm/plat-omap/
DKconfig25 depends on POWER_AVS && (ARCH_OMAP3 || ARCH_OMAP4) && PM
119 depends on ARCH_OMAP3 && PM
150 prompt "OMAP PM layer selection"
155 bool "No-op/debug PM layer"
/linux-4.1.27/Documentation/trace/
Devents-power.txt66 4. PM QoS events
68 The PM QoS events are used for QoS add/update/remove request and for
87 And, there are also events used for device PM QoS add/update/remove request.
/linux-4.1.27/drivers/gpu/drm/nouveau/nvkm/engine/pm/
Dnv50.c49 .base.handle = NV_ENGINE(PM, 0x50),
Dg84.c57 .base.handle = NV_ENGINE(PM, 0x84),
Dgk110.c50 .handle = NV_ENGINE(PM, 0xf0),
Dgt215.c75 .base.handle = NV_ENGINE(PM, 0xa3),
Dgk104.c141 .handle = NV_ENGINE(PM, 0xe0),
Dnv40.c122 .base.handle = NV_ENGINE(PM, 0x40),
Dgf100.c152 .handle = NV_ENGINE(PM, 0xc0),
Dbase.c368 .handle = NV_ENGCTX(PM, 0x00),
/linux-4.1.27/drivers/thermal/ti-soc-thermal/
DTODO4 - Revisit PM support
/linux-4.1.27/arch/arm/mach-shmobile/
DKconfig14 select PM_RCAR if PM || SMP
20 select PM_RCAR if PM || SMP
27 select PM_RMOBILE if PM
/linux-4.1.27/arch/arm/mach-rockchip/
DKconfig14 select REGULATOR if PM
/linux-4.1.27/drivers/cpuidle/
DKconfig4 bool "CPU idle PM support"
/linux-4.1.27/arch/arm/mach-u300/
DKconfig27 depends on PM
/linux-4.1.27/drivers/staging/gdm72xx/
DKconfig56 depends on PM
/linux-4.1.27/arch/arm/mach-ux500/
DKconfig35 select PM_GENERIC_DOMAINS if PM
/linux-4.1.27/arch/blackfin/
DKconfig1255 depends on PM && !BF60x
1289 depends on PM
1293 depends on PM && (BF51x || BF52x || BF534 || BF536 || BF537)
1300 depends on PM && BF54x
1312 depends on PM && BF60x
1326 depends on PM && BF60x
1340 depends on PM && BF60x
1354 depends on PM && BF60x
1368 depends on PM && BF60x
1382 depends on PM && BF60x
[all …]
/linux-4.1.27/drivers/pci/pcie/
DKconfig82 depends on PCIEPORTBUS && PM
/linux-4.1.27/drivers/media/platform/s5p-tv/
DKconfig11 depends on PM
/linux-4.1.27/Documentation/sound/alsa/
Dhda_codec.txt117 register states for the power-management resume. When no PM is needed,
220 Call snd_hda_suspend() in the PM suspend callback.
221 Call snd_hda_resume() in the PM resume callback.
DHD-Audio.txt591 The recent kernel supports the runtime PM for the HD-audio controller
/linux-4.1.27/Documentation/
Dphy.txt120 7. PM Runtime
134 phy_pm_runtime_forbid for performing PM operations.
DSubmittingDrivers89 PM support: Since Linux is used on many portable and desktop systems, your
Dhwspinlock.txt254 * @dev: underlying device, will be used to invoke runtime PM api
Dkernel-parameters.txt2826 pcie_pme= [PCIE,PM] Native PCIe PME signaling options:
2833 [PM]
/linux-4.1.27/drivers/usb/phy/
DKconfig23 depends on USB_EHCI_FSL && USB_FSL_USB2 && USB_OTG_FSM && PM
156 depends on USB_EHCI_MV && USB_MV_UDC && PM
/linux-4.1.27/arch/unicore32/kernel/
Dsleep.S81 @ PM BaseAddr
/linux-4.1.27/arch/m68k/
DKconfig148 config PM config
/linux-4.1.27/arch/arm/mach-imx/
DKconfig4 select ARM_CPU_SUSPEND if PM
8 select PM_OPP if PM
54 select PM_GENERIC_DOMAINS if PM
/linux-4.1.27/drivers/usb/core/
DKconfig46 depends on PM
/linux-4.1.27/Documentation/devicetree/bindings/pinctrl/
Dmarvell,dove-pinctrl.txt64 pmu-nc Pin not driven by any PM function
/linux-4.1.27/Documentation/devicetree/bindings/arm/omap/
Domap.txt22 - ti,no_idle_on_suspend: When present, it prevents the PM to idle the module
/linux-4.1.27/Documentation/ABI/stable/
Dsysfs-bus-usb74 USB PM tool
/linux-4.1.27/Documentation/devicetree/bindings/arm/
Didle-states.txt11 wfi to power gating) according to OS PM policies. The CPU states representing
27 PM implementation to put the processor in different idle states (which include
32 characterized with bindings that provide the required information to OS PM
/linux-4.1.27/drivers/net/wireless/ath/ath9k/
DKconfig128 depends on ATH9K && PM
/linux-4.1.27/Documentation/input/
Dyealink.txt104 '.' : For example like AM, PM, SU, a 'dot' .. or other single segment
/linux-4.1.27/Documentation/video4linux/
Dfimc.txt29 - runtime PM and system wide suspend/resume
/linux-4.1.27/drivers/media/platform/
DKconfig106 depends on PM
/linux-4.1.27/arch/ia64/
DKconfig240 depends on !PM
576 if PM
/linux-4.1.27/sound/pci/hda/
DKconfig245 depends on PM
/linux-4.1.27/arch/parisc/
DKconfig86 config PM config
/linux-4.1.27/drivers/usb/storage/
DKconfig44 depends on USB_STORAGE_REALTEK && PM
/linux-4.1.27/arch/m68k/include/asm/
DMC68328.h638 #define PM(x) (1 << (x)) macro
DMC68VZ328.h588 #define PM(x) (1 << (x)) macro
/linux-4.1.27/drivers/net/fddi/skfp/h/
Dcmtdef.h116 #define PM 2 /* PM .. PA+NUM_PHYS-1 */ macro
/linux-4.1.27/drivers/net/fddi/skfp/
Dpcmplc.c385 if (np >= PM) in pcm_init()
386 phy->phy_name = '0' + np - PM ; in pcm_init()
/linux-4.1.27/drivers/mfd/
DKconfig1133 PM chips.
1142 PM chips with I2C interface.
1151 PM chips with SPI interface.
1217 bool "TI TWL92330/Menelaus PM chip"
/linux-4.1.27/arch/powerpc/platforms/
DKconfig97 depends on FSL_SOC && MPIC_TIMER && PM
/linux-4.1.27/drivers/macintosh/
DKconfig124 depends on ADB_PMU && PM && PPC32
/linux-4.1.27/lib/
DKconfig.debug1390 tristate "PM notifier error injection module"
1391 depends on PM && NOTIFIER_ERROR_INJECTION
1395 PM notifier chain callbacks. It is controlled through debugfs
1401 Example: Inject PM suspend error (-12 = -ENOMEM)
/linux-4.1.27/drivers/net/ethernet/amd/xgbe/
Dxgbe-dev.c724 if (XGMAC_IOREAD_BITS(pdata, MAC_PFR, PM) == val) in xgbe_set_all_multicast_mode()
728 XGMAC_IOWRITE_BITS(pdata, MAC_PFR, PM, val); in xgbe_set_all_multicast_mode()
/linux-4.1.27/Documentation/hid/
Dhid-transport.txt264 Called by HID core to give PM hints to transport drivers. Usually this is
/linux-4.1.27/arch/sh/
DKconfig230 select PM
/linux-4.1.27/Documentation/networking/
De1000.txt429 Intel(R) PRO/1000 PM Network Connection
/linux-4.1.27/arch/arm/
DKconfig608 select ARM_CPU_SUSPEND if PM
637 select PM_GENERIC_DOMAINS if PM
720 select PM_GENERIC_DOMAINS if PM
/linux-4.1.27/Documentation/scsi/
DChangeLog.megaraid30 > Sent: Thursday, May 04, 2006 2:49 PM
DChangeLog.sym53c8xx475 driver to handle PM from SCRIPTS.
/linux-4.1.27/arch/x86/
DKconfig2158 bool "Enable PM at boot time"
/linux-4.1.27/
DMAINTAINERS4357 GENERIC PM DOMAINS