| /linux/arch/mips/mm/ |
| A D | cache.c | 177 #define PM(p) __pgprot(_page_cachable_default | (p)) macro
185 protection_map[1] = PM(_PAGE_PRESENT | _PAGE_NO_EXEC); in setup_protection_map()
188 protection_map[4] = PM(_PAGE_PRESENT); in setup_protection_map()
189 protection_map[5] = PM(_PAGE_PRESENT); in setup_protection_map()
190 protection_map[6] = PM(_PAGE_PRESENT); in setup_protection_map()
191 protection_map[7] = PM(_PAGE_PRESENT); in setup_protection_map()
198 protection_map[12] = PM(_PAGE_PRESENT); in setup_protection_map()
199 protection_map[13] = PM(_PAGE_PRESENT); in setup_protection_map()
200 protection_map[14] = PM(_PAGE_PRESENT | _PAGE_WRITE); in setup_protection_map()
201 protection_map[15] = PM(_PAGE_PRESENT | _PAGE_WRITE); in setup_protection_map()
[all …]
|
| /linux/Documentation/devicetree/bindings/power/ |
| A 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==
18 ==PM domain consumers==
21 - power-domains : A list of PM domain specifiers, as defined by bindings of
[all …]
|
| A D | power-domain.yaml | 7 title: Generic PM domains
15 System on chip designs are often divided into multiple PM domains that can be
17 leakage current. Moreover, in some cases the similar PM domains may also be
20 This device tree binding can be used to bind PM domain consumer devices with
21 their PM domains provided by PM domain providers. A PM domain provider can be
22 represented by any node in the device tree and can provide one or more PM
25 \#power-domain-cells property in the PM domain provider node.
41 PM domain and not the idle states of the devices or sub-domains in the PM
56 Number of cells in a PM domain specifier. Typically 0 for nodes
57 representing a single PM domain and 1 for nodes providing multiple PM
[all …]
|
| A D | renesas,sysc-rmobile.yaml | 36 This node contains a hierarchy of PM domain nodes, which should match the
61 PM domain node representing a PM domain. This node should be named by
68 If the PM domain is not always-on, this property must contain the
71 If the PM domain is always-on, this property must be omitted.
90 // This shows a subset of the r8a7740 PM domain hierarchy, containing the
|
| /linux/Documentation/devicetree/bindings/arm/ux500/ |
| A 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/Documentation/arch/arm/omap/ |
| A D | omap_pm.rst | 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
19 - specify PM parameters in terms of fundamental units, such as
59 The OMAP PM layer is intended to be temporary
65 to use the Linux PM QoS code; and the OMAP PM interface can disappear.
68 Driver usage of the OMAP PM functions
[all …]
|
| /linux/Documentation/power/ |
| A D | runtime_pm.rst | 36 The runtime PM callbacks present in 'struct dev_pm_ops', the device runtime PM
38 runtime PM are described below.
40 2. Device Runtime PM Callbacks
57 1. PM domain of the device, if the device's PM domain object, dev->pm_domain,
186 PM status of which is 'suspended').
205 3. Runtime PM Device Fields
306 4. Runtime PM Device Helper Functions
395 runtime PM status is RPM_ACTIVE and the runtime PM usage counter is
643 6. Runtime PM and System Sleep
847 the runtime PM callbacks needs to be implemented, a platform dependent PM
[all …]
|
| A D | pm_qos_interface.rst | 2 PM Quality Of Service Interface
9 Two different PM QoS frameworks are available:
11 * The per-device PM QoS framework provides the API to manage the
12 per-device latency constraints and PM QoS flags.
14 The latency unit used in the PM QoS framework is the microsecond (usec).
17 1. PM QoS framework
36 PM QoS API functions.
68 Only processes can register a PM QoS request. To provide for automatic
87 2. PM QoS per-device latency and flags framework
137 The device's PM QoS structure has not been initialized
[all …]
|
| A D | pci.rst | 314 int pm_cap; /* PM capability offset in the
390 PM capabilities, if supported.
765 after device interrupts have been disabled by the PM core.
856 device interrupts have been enabled by the PM core.
882 interrupts have been enabled by the PM core.
893 PM core.
940 (runtime PM). It is executed by the PM core's runtime PM framework when the
952 by the PM core's runtime PM framework when the device is about to be resumed
965 by the PM core's runtime PM framework whenever it may be desirable to suspend
1067 runtime PM framework provided by the PM core and the PCI subsystem, it needs
[all …]
|
| /linux/drivers/accel/ivpu/ |
| A D | ivpu_pm.c | 198 ivpu_dbg(vdev, PM, "Suspend..\n"); in ivpu_pm_suspend_cb()
214 ivpu_dbg(vdev, PM, "Suspend done.\n"); in ivpu_pm_suspend_cb()
225 ivpu_dbg(vdev, PM, "Resume..\n"); in ivpu_pm_resume_cb()
231 ivpu_dbg(vdev, PM, "Resume done.\n"); in ivpu_pm_resume_cb()
246 ivpu_dbg(vdev, PM, "Runtime suspend..\n"); in ivpu_pm_runtime_suspend_cb()
282 ivpu_dbg(vdev, PM, "Runtime resume..\n"); in ivpu_pm_runtime_resume_cb()
313 ivpu_dbg(vdev, PM, "Pre-reset..\n"); in ivpu_pm_reset_prepare_cb()
325 ivpu_dbg(vdev, PM, "Pre-reset done.\n"); in ivpu_pm_reset_prepare_cb()
333 ivpu_dbg(vdev, PM, "Post-reset..\n"); in ivpu_pm_reset_done_cb()
339 ivpu_dbg(vdev, PM, "Post-reset done.\n"); in ivpu_pm_reset_done_cb()
[all …]
|
| /linux/arch/arm/mach-at91/ |
| A D | Kconfig | 85 select ATMEL_PM if PM
91 select SRAM if PM
99 select ATMEL_PM if PM
108 select SRAM if PM
132 select ATMEL_PM if PM
140 select SRAM if PM
148 select ATMEL_PM if PM
156 select SRAM if PM
229 select ATMEL_PM if PM
232 select SRAM if PM
[all …]
|
| /linux/drivers/pmdomain/bcm/ |
| A D | Kconfig | 2 menu "Broadcom PM Domains"
8 select PM_GENERIC_DOMAINS if PM
20 select PM_GENERIC_DOMAINS if PM
29 select PM_GENERIC_DOMAINS if PM
37 select PM_GENERIC_DOMAINS if PM
|
| /linux/drivers/pmdomain/xilinx/ |
| A D | Kconfig | 4 bool "Enable Zynq MPSoC generic PM domains"
6 depends on PM && ZYNQMP_FIRMWARE
9 Say yes to enable device power management through PM domains
|
| /linux/Documentation/ABI/testing/ |
| A 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.
120 "atapi" for packet device, "pmp" for PM, or
|
| /linux/Documentation/driver-api/media/ |
| A D | camera-sensor.rst | 61 device they otherwise control as well. They shall use runtime PM to manage
62 power states. Runtime PM shall be enabled at probe time and disabled at remove
63 time. Drivers should enable runtime PM autosuspend. Also see
66 The runtime PM handlers shall handle clocks, regulators, GPIOs, and other
69 only), the runtime PM handlers may be left unimplemented.
86 stop streaming in the PM suspend handler and restart it in the resume handler.
87 Drivers should in general not implement the system PM handlers.
92 PM instead. If you feel you need to begin calling ``.s_power()`` from an ISP or
93 a bridge driver, instead add runtime PM support to the sensor driver you are
102 PM ``runtime_resume`` callback, as it has no way to figure out the power state
[all …]
|
| /linux/drivers/pmdomain/imx/ |
| A D | Kconfig | 2 menu "i.MX PM Domains"
5 bool "i.MX GPCv2 PM domains"
7 depends on PM
|
| /linux/drivers/pmdomain/mediatek/ |
| A D | Kconfig | 3 menu "MediaTek PM Domains"
12 select PM_GENERIC_DOMAINS if PM
20 depends on PM
|
| /linux/drivers/pmdomain/amlogic/ |
| A D | Kconfig | 2 menu "Amlogic PM Domains"
7 depends on PM && OF
18 depends on PM && OF
|
| /linux/arch/arm/mach-mmp/ |
| A D | Kconfig | 35 select PM_GENERIC_DOMAINS if PM
36 select PM_GENERIC_DOMAINS_OF if PM && OF
52 select PM_GENERIC_DOMAINS if PM
53 select PM_GENERIC_DOMAINS_OF if PM && OF
|
| /linux/drivers/soc/samsung/ |
| A D | Kconfig | 53 bool "S3C2410 PM Suspend Memory CRC"
54 depends on PM && (ARCH_S3C64XX || ARCH_S5PV210)
57 Enable the PM code's memory area checksum over sleep. This option
66 int "S3C2410 PM Suspend CRC Chunksize (KiB)"
67 depends on PM && SAMSUNG_PM_CHECK
|
| /linux/Documentation/driver-api/pm/ |
| A D | devices.rst | 18 management (PM) code is also driver-specific. Most drivers will do very
282 PM core as mutually exclusive. Moreover, PM domain callbacks always take
341 PM core will skip the ``suspend``, ``suspend_late`` and
349 disabled for runtime PM; only the runtime-PM status matters. It follows
353 runtime PM disabled.
730 IRQ-safe device belongs to a PM domain, the runtime PM of the domain will be
784 Setting that flag causes the PM core and middle-layer code
801 doing this, otherwise the PM core takes care of it.
852 "active" by the PM core. [Hence, the drivers that do not set
861 "active" by the PM core before enabling runtime PM for it. In that case, the
[all …]
|
| /linux/drivers/pmdomain/arm/ |
| A D | Kconfig | 6 select PM_GENERIC_DOMAINS if PM
18 select PM_GENERIC_DOMAINS if PM
31 select PM_GENERIC_DOMAINS if PM
|
| /linux/kernel/configs/ |
| A D | nopm.config | 7 # Triggers PM on OMAP
13 # ARM/ARM64 architectures that select PM unconditionally
|
| /linux/drivers/soc/renesas/ |
| A D | Kconfig | 13 select PM
22 select PM
31 select PM
44 select PM
52 select PM
58 select PM
136 select PM
144 select PM
342 select PM
|
| /linux/Documentation/fault-injection/ |
| A D | notifier-error-inject.rst | 9 * PM notifier
14 PM notifier error injection module
20 Possible PM notifier events to be failed are:
26 Example: Inject PM suspend error (-12 = -ENOMEM)::
|