| /linux-6.12.1/arch/mips/mm/ |
| D | cache.c | 177 #define PM(p) __pgprot(_page_cachable_default | (p)) macro
184 protection_map[0] = PM(_PAGE_PRESENT | _PAGE_NO_EXEC | _PAGE_NO_READ); in setup_protection_map()
185 protection_map[1] = PM(_PAGE_PRESENT | _PAGE_NO_EXEC); in setup_protection_map()
186 protection_map[2] = PM(_PAGE_PRESENT | _PAGE_NO_EXEC | _PAGE_NO_READ); in setup_protection_map()
187 protection_map[3] = 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()
193 protection_map[8] = PM(_PAGE_PRESENT | _PAGE_NO_EXEC | _PAGE_NO_READ); in setup_protection_map()
[all …]
|
| /linux-6.12.1/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==
18 ==PM domain consumers==
21 - power-domains : A list of PM domain specifiers, as defined by bindings of
[all …]
|
| /linux-6.12.1/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-6.12.1/Documentation/arch/arm/omap/ |
| 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
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
55 Further documentation for all OMAP PM interface functions can be
[all …]
|
| /linux-6.12.1/Documentation/power/ |
| D | runtime_pm.rst | 14 Support for runtime power management (runtime PM) of I/O devices is provided
15 at the power management core (PM core) level by means of:
18 put their PM-related work items. It is strongly recommended that pm_wq be
19 used for queuing all work items related to runtime PM, because this allows
24 * A number of runtime PM fields in the 'power' member of 'struct device' (which
26 be used for synchronizing runtime PM operations with one another.
28 * Three device runtime PM callbacks in 'struct dev_pm_ops' (defined in
32 used for carrying out runtime PM operations in such a way that the
33 synchronization between them is taken care of by the PM core. Bus types and
36 The runtime PM callbacks present in 'struct dev_pm_ops', the device runtime PM
[all …]
|
| 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
35 Clients of PM QoS need to save the returned handle for future use in other
36 PM QoS API functions.
68 Only processes can register a PM QoS request. To provide for automatic
72 To register the default PM QoS target for the CPU latency QoS, the process must
[all …]
|
| D | pci.rst | 44 approach, that is referred to as the native PCI power management (native PCI PM)
50 Devices supporting the native PCI PM usually can generate wakeup signals called
65 native PCI PM mechanism, because the method provided by the platform depends on
74 The PCI Bus Power Management Interface Specification (PCI PM Spec) was
79 The implementation of the PCI PM Spec is optional for conventional PCI devices,
80 but it is mandatory for PCI Express devices. If a device supports the PCI PM
85 The PCI PM Spec defines 4 operating states for devices (D0-D3) and for buses
102 regardless of whether or not it implements the PCI PM Spec. In addition to
103 that, if the PCI PM Spec is implemented by the device, it must support D3hot
106 PCI devices supporting the PCI PM Spec can be programmed to go to any of the
[all …]
|
| /linux-6.12.1/drivers/accel/ivpu/ |
| 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()
271 ivpu_dbg(vdev, PM, "Runtime suspend done.\n"); in ivpu_pm_runtime_suspend_cb()
282 ivpu_dbg(vdev, PM, "Runtime resume..\n"); in ivpu_pm_runtime_resume_cb()
288 ivpu_dbg(vdev, PM, "Runtime resume done.\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()
[all …]
|
| /linux-6.12.1/arch/arm/mach-at91/ |
| D | Kconfig | 6 select ARM_CPU_SUSPEND if PM && ARCH_MULTI_V7
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
[all …]
|
| /linux-6.12.1/drivers/pmdomain/bcm/ |
| 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-6.12.1/drivers/pmdomain/xilinx/ |
| 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-6.12.1/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.
120 "atapi" for packet device, "pmp" for PM, or
|
| /linux-6.12.1/Documentation/driver-api/media/ |
| 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-6.12.1/drivers/pmdomain/imx/ |
| D | Kconfig | 2 menu "i.MX PM Domains"
5 bool "i.MX GPCv2 PM domains"
7 depends on PM
|
| /linux-6.12.1/drivers/pmdomain/amlogic/ |
| D | Kconfig | 2 menu "Amlogic PM Domains"
7 depends on PM && OF
18 depends on PM && OF
|
| /linux-6.12.1/drivers/pmdomain/mediatek/ |
| D | Kconfig | 3 menu "MediaTek PM Domains"
12 select PM_GENERIC_DOMAINS if PM
20 depends on PM
|
| /linux-6.12.1/arch/arm/mach-mmp/ |
| 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-6.12.1/drivers/soc/samsung/ |
| 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-6.12.1/Documentation/driver-api/pm/ |
| D | devices.rst | 18 management (PM) code is also driver-specific. Most drivers will do very
67 the PM core are involved in runtime power management. As in the system
76 synergies exist, so that several drivers using runtime PM might put the system
125 device drivers whose subsystems (PM domains, device types, device classes and
152 its system wakeup mechanism and for notifying the PM core of system wakeup
260 the device is suspending (i.e. has been chosen by the PM core as the next
279 All phases use PM domain, bus, type, class or driver callbacks (that is, methods
282 PM core as mutually exclusive. Moreover, PM domain callbacks always take
287 1. If ``dev->pm_domain`` is present, the PM core will choose the callback
300 This allows PM domains and device types to override callbacks provided by bus
[all …]
|
| /linux-6.12.1/drivers/pmdomain/arm/ |
| D | Kconfig | 6 select PM_GENERIC_DOMAINS if PM
18 select PM_GENERIC_DOMAINS if PM
31 select PM_GENERIC_DOMAINS if PM
|
| /linux-6.12.1/kernel/configs/ |
| D | nopm.config | 7 # Triggers PM on OMAP
13 # ARM/ARM64 architectures that select PM unconditionally
|
| /linux-6.12.1/drivers/soc/renesas/ |
| 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-6.12.1/Documentation/fault-injection/ |
| 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-6.12.1/arch/arm/mach-mxs/ |
| D | Kconfig | 5 select ARM_CPU_SUSPEND if PM
12 select ARM_CPU_SUSPEND if PM
|
| /linux-6.12.1/Documentation/arch/arm/sa1100/ |
| 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.
|