Home
last modified time | relevance | path

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

1234567891011

/linux-6.15/arch/mips/mm/
H A Dcache.c177 #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-6.15/Documentation/devicetree/bindings/power/
H A 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==
18 ==PM domain consumers==
21 - power-domains : A list of PM domain specifiers, as defined by bindings of
[all …]
H A Dpower-domain.yaml7 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 …]
H A Drenesas,sysc-rmobile.yaml36 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-6.15/Documentation/devicetree/bindings/arm/ux500/
H A 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-6.15/Documentation/arch/arm/omap/
H A Domap_pm.rst2 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-6.15/Documentation/power/
H A Druntime_pm.rst36 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
397 runtime PM status is RPM_ACTIVE and the runtime PM usage counter is
645 6. Runtime PM and System Sleep
849 the runtime PM callbacks needs to be implemented, a platform dependent PM
[all …]
H A Dpm_qos_interface.rst2 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 …]
H A Dpci.rst314 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-6.15/drivers/accel/ivpu/
H A Divpu_pm.c216 ivpu_dbg(vdev, PM, "Suspend..\n"); in ivpu_pm_suspend_cb()
232 ivpu_dbg(vdev, PM, "Suspend done.\n"); in ivpu_pm_suspend_cb()
245 ivpu_dbg(vdev, PM, "Resume..\n"); in ivpu_pm_resume_cb()
251 ivpu_dbg(vdev, PM, "Resume done.\n"); in ivpu_pm_resume_cb()
268 ivpu_dbg(vdev, PM, "Runtime suspend..\n"); in ivpu_pm_runtime_suspend_cb()
306 ivpu_dbg(vdev, PM, "Runtime resume..\n"); in ivpu_pm_runtime_resume_cb()
312 ivpu_dbg(vdev, PM, "Runtime resume done.\n"); in ivpu_pm_runtime_resume_cb()
341 ivpu_dbg(vdev, PM, "Pre-reset..\n"); in ivpu_pm_reset_prepare_cb()
350 ivpu_dbg(vdev, PM, "Pre-reset done.\n"); in ivpu_pm_reset_prepare_cb()
357 ivpu_dbg(vdev, PM, "Post-reset..\n"); in ivpu_pm_reset_done_cb()
[all …]
/linux-6.15/arch/arm/mach-at91/
H A DKconfig96 select ATMEL_PM if PM
102 select SRAM if PM
110 select ATMEL_PM if PM
119 select SRAM if PM
143 select ATMEL_PM if PM
151 select SRAM if PM
159 select ATMEL_PM if PM
167 select SRAM if PM
240 select ATMEL_PM if PM
243 select SRAM if PM
[all …]
/linux-6.15/drivers/pmdomain/bcm/
H A DKconfig2 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-6.15/drivers/pmdomain/xilinx/
H A DKconfig4 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-6.15/drivers/pmdomain/mediatek/
H A DKconfig3 menu "MediaTek PM Domains"
12 select PM_GENERIC_DOMAINS if PM
20 depends on PM
33 depends on PM
/linux-6.15/Documentation/ABI/testing/
H A Dsysfs-ata20 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-6.15/Documentation/driver-api/media/
H A Dcamera-sensor.rst61 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.
85 therefore **not** keep track of the streaming state to stop streaming in the PM
87 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-6.15/drivers/pmdomain/imx/
H A DKconfig2 menu "i.MX PM Domains"
5 bool "i.MX GPCv2 PM domains"
7 depends on PM
/linux-6.15/drivers/pmdomain/amlogic/
H A DKconfig2 menu "Amlogic PM Domains"
7 depends on PM && OF
18 depends on PM && OF
/linux-6.15/arch/arm/mach-mmp/
H A DKconfig35 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-6.15/drivers/soc/samsung/
H A DKconfig53 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-6.15/Documentation/driver-api/pm/
H A Ddevices.rst18 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-6.15/drivers/pmdomain/arm/
H A DKconfig6 select PM_GENERIC_DOMAINS if PM
18 select PM_GENERIC_DOMAINS if PM
31 select PM_GENERIC_DOMAINS if PM
/linux-6.15/kernel/configs/
H A Dnopm.config7 # Triggers PM on OMAP
13 # ARM/ARM64 architectures that select PM unconditionally
/linux-6.15/Documentation/fault-injection/
H A Dnotifier-error-inject.rst9 * 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-6.15/arch/arm/mach-mxs/
H A DKconfig5 select ARM_CPU_SUSPEND if PM
12 select ARM_CPU_SUSPEND if PM

1234567891011