/linux/arch/mips/mm/ |
A D | cache.c | 160 #define PM(p) __pgprot(_page_cachable_default | (p)) macro 165 protection_map[1] = PM(_PAGE_PRESENT | _PAGE_NO_EXEC); in setup_protection_map() 168 protection_map[4] = PM(_PAGE_PRESENT); in setup_protection_map() 169 protection_map[5] = PM(_PAGE_PRESENT); in setup_protection_map() 170 protection_map[6] = PM(_PAGE_PRESENT); in setup_protection_map() 171 protection_map[7] = PM(_PAGE_PRESENT); in setup_protection_map() 178 protection_map[12] = PM(_PAGE_PRESENT); in setup_protection_map() 179 protection_map[13] = PM(_PAGE_PRESENT); in setup_protection_map() 180 protection_map[14] = PM(_PAGE_PRESENT | _PAGE_WRITE); in setup_protection_map() 181 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 19 This device tree binding can be used to bind PM domain consumer devices with 20 their PM domains provided by PM domain providers. A PM domain provider can be 21 represented by any node in the device tree and can provide one or more PM 24 \#power-domain-cells property in the PM domain provider node. 38 PM domain and not the idle states of the devices or sub-domains in the PM 54 Number of cells in a PM domain specifier. Typically 0 for nodes 55 representing a single PM domain and 1 for nodes providing multiple PM 61 A phandle and PM domain specifier as defined by bindings of the power [all …]
|
A D | xlnx,zynqmp-genpd.txt | 2 Device Tree Bindings for the Xilinx Zynq MPSoC PM domains 5 generic PM domain binding[1]. 9 == Zynq MPSoC Generic PM Domain Node == 13 - #power-domain-cells: Number of cells in a PM domain specifier. Must be 1.
|
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 hould 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/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 302 4. Runtime PM Device Helper Functions 389 runtime PM status is RPM_ACTIVE and the runtime PM usage counter is 633 6. Runtime PM and System Sleep 836 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 1068 runtime PM framework provided by the PM core and the PCI subsystem, it needs [all …]
|
/linux/Documentation/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/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/drivers/soc/samsung/ |
A D | Kconfig | 38 bool "Exynos PM domains" if COMPILE_TEST 42 bool "Samsung PM Suspend debug" 43 depends on PM && DEBUG_KERNEL 48 Say Y here if you want verbose debugging from the PM Suspend and 54 depends on PM && (MACH_SMDK6410) 62 bool "S3C2410 PM Suspend Memory CRC" 63 depends on PM && (PLAT_S3C24XX || ARCH_S3C64XX || ARCH_S5PV210) 66 Enable the PM code's memory area checksum over sleep. This option 77 int "S3C2410 PM Suspend CRC Chunksize (KiB)" 78 depends on PM && SAMSUNG_PM_CHECK
|
/linux/arch/arm/mach-at91/ |
A D | Kconfig | 5 select ARM_CPU_SUSPEND if PM && ARCH_MULTI_V7 83 select ATMEL_PM if PM 89 select SRAM if PM 97 select ATMEL_PM if PM 107 select SRAM if PM 131 select ATMEL_PM if PM 140 select SRAM if PM 204 select ATMEL_PM if PM 208 select SRAM if PM 216 select ATMEL_PM if PM [all …]
|
/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. 119 "atapi" for packet device, "pmp" for PM, or
|
A D | sysfs-devices-power | 74 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, 254 is used for manipulating the PM QoS "no power off" flag. If 269 the current runtime PM status of the device, which may be 271 error), or "unsupported" (runtime PM is disabled). 278 Used for runtime PM statistics. 285 Used for runtime PM statistics. 291 Reports the runtime PM usage count of a device. 297 Is runtime PM enabled for this device? [all …]
|
A D | sysfs-devices-lpss_ltr | 18 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
|
/linux/drivers/soc/xilinx/ |
A D | Kconfig | 6 depends on PM && ZYNQMP_FIRMWARE 20 bool "Enable Zynq MPSoC generic PM domains" 22 depends on PM && ZYNQMP_FIRMWARE 25 Say yes to enable device power management through PM domains
|
/linux/Documentation/devicetree/bindings/soc/bcm/ |
A D | brcm,bcm2835-pm.txt | 1 BCM2835 PM (Power domains, watchdog) 3 The PM block controls power domains and some reset lines, and includes 5 binding which covered some of PM's register range and functionality. 11 register ranges ("PM" and "ASYNC_BRIDGE" in that
|
/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/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)::
|
/linux/Documentation/arm/sa1100/ |
A D | assabet.rst | 254 - PM: Not tested. 255 - COM: TX, RX, CTS, DSR, DCD, RTS, DTR, PM 256 - PM: Not tested. 259 - PM: Not tested. 262 - LCD: Fully tested. PM 272 - PM: Not tested. 281 - PM: Not tested. 290 - PM: Not tested. 295 - PM: Not tested. 299 - PM: Not tested.
|
/linux/kernel/configs/ |
A D | nopm.config | 5 # Triggers PM on OMAP 11 # ARM/ARM64 architectures that select PM unconditionally
|
/linux/arch/arm/mach-mxs/ |
A D | Kconfig | 5 select ARM_CPU_SUSPEND if PM 12 select ARM_CPU_SUSPEND if PM
|
/linux/arch/arm/mach-rockchip/ |
A D | Kconfig | 16 select REGULATOR if PM 21 select PM
|
/linux/drivers/soc/amlogic/ |
A D | Kconfig | 32 depends on PM && OF 43 depends on PM && OF 54 depends on PM && OF
|
/linux/drivers/soc/bcm/bcm63xx/ |
A D | Kconfig | 7 select PM_GENERIC_DOMAINS if PM 18 select PM_GENERIC_DOMAINS if PM
|