| /linux-5.10/Documentation/devicetree/bindings/soc/rockchip/ |
| D | power_domain.txt | 1 * Rockchip Power Domains
3 Rockchip processors include support for multiple power domains which can be
4 powered up/down by software based on different application scenes to save power.
6 Required properties for power domain controller:
7 - compatible: Should be one of the following.
8 "rockchip,px30-power-controller" - for PX30 SoCs.
9 "rockchip,rk3036-power-controller" - for RK3036 SoCs.
10 "rockchip,rk3066-power-controller" - for RK3066 SoCs.
11 "rockchip,rk3128-power-controller" - for RK3128 SoCs.
12 "rockchip,rk3188-power-controller" - for RK3188 SoCs.
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/power/ |
| D | power-domain.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/power/power-domain.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rafael J. Wysocki <rjw@rjwysocki.net>
11 - Kevin Hilman <khilman@kernel.org>
12 - Ulf Hansson <ulf.hansson@linaro.org>
16 used for power gating of selected IP blocks for power saving by reduced leakage
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
[all …]
|
| D | power_domain.txt | 4 used for power gating of selected IP blocks for power saving by reduced leakage
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
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==
16 See power-domain.yaml.
18 ==PM domain consumers==
21 - power-domains : A list of PM domain specifiers, as defined by bindings of
22 the power controller that is the PM domain provider.
[all …]
|
| D | fsl,imx-gpcv2.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/fsl,imx-gpcv2.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Freescale i.MX General Power Controller v2
10 - Andrey Smirnov <andrew.smirnov@gmail.com>
13 The i.MX7S/D General Power Control (GPC) block contains Power Gating
14 Control (PGC) for various power domains.
16 Power domains contained within GPC node are generic power domain
18 Documentation/devicetree/bindings/power/power-domain.yaml, which are
[all …]
|
| D | renesas,sysc-rmobile.txt | 1 DT bindings for the Renesas R-Mobile System Controller
5 The R-Mobile System Controller provides the following functions:
6 - Boot mode management,
7 - Reset generation,
8 - Power management.
11 - compatible: Should be "renesas,sysc-<soctype>", "renesas,sysc-rmobile" as
14 - "renesas,sysc-r8a73a4" (R-Mobile APE6)
15 - "renesas,sysc-r8a7740" (R-Mobile A1)
16 - "renesas,sysc-sh73a0" (SH-Mobile AG5)
17 - reg: Two address start and address range blocks for the device:
[all …]
|
| D | fsl,imx-gpc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/power/fsl,imx-gpc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Freescale i.MX General Power Controller
10 - Philipp Zabel <p.zabel@pengutronix.de>
13 The i.MX6 General Power Control (GPC) block contains DVFS load tracking
14 counters and Power Gating Control (PGC).
16 The power domains are generic power domain providers as documented in
17 Documentation/devicetree/bindings/power/power-domain.yaml. They are
[all …]
|
| D | pd-samsung.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/power/pd-samsung.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Samsung Exynos SoC Power Domains
10 - Krzysztof Kozlowski <krzk@kernel.org>
13 Exynos processors include support for multiple power domains which are used
14 to gate power to one or more peripherals on the processor.
17 - $ref: power-domain.yaml#
22 - samsung,exynos4210-pd
[all …]
|
| D | amlogic,meson-gx-pwrc.txt | 1 Amlogic Meson Power Controller
4 The Amlogic Meson SoCs embeds an internal Power domain controller.
6 VPU Power Domain
7 ----------------
9 The Video Processing Unit power domain is controlled by this power controller,
10 but the domain requires some external resources to meet the correct power
12 The bindings must respect the power domain bindings as described in the file
13 power-domain.yaml
16 ---------------------
19 - compatible: should be one of the following :
[all …]
|
| D | xlnx,zynqmp-genpd.txt | 1 -----------------------------------------------------------
3 -----------------------------------------------------------
4 The binding for zynqmp-power-controller follow the common
5 generic PM domain binding[1].
7 [1] Documentation/devicetree/bindings/power/power-domain.yaml
9 == Zynq MPSoC Generic PM Domain Node ==
12 - Below property should be in zynqmp-firmware node.
13 - #power-domain-cells: Number of cells in a PM domain specifier. Must be 1.
15 Power domain ID indexes are mentioned in
16 include/dt-bindings/power/xlnx-zynqmp-power.h.
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/soc/mediatek/ |
| D | scpsys.txt | 4 The System Control Processor System (SCPSYS) has several power management
7 The System Power Manager (SPM) inside the SCPSYS is for the MTCMOS power
8 domain control.
10 The driver implements the Generic PM domain bindings described in
11 power/power-domain.yaml. It provides the power domains defined in
12 - include/dt-bindings/power/mt8173-power.h
13 - include/dt-bindings/power/mt6797-power.h
14 - include/dt-bindings/power/mt6765-power.h
15 - include/dt-bindings/power/mt2701-power.h
16 - include/dt-bindings/power/mt2712-power.h
[all …]
|
| /linux-5.10/Documentation/power/regulator/ |
| D | overview.rst | 11 The intention is to allow systems to dynamically control regulator power output
12 in order to save power and prolong battery life. This applies to both voltage
26 - Regulator
27 - Electronic device that supplies power to other devices.
31 Input Voltage -> Regulator -> Output Voltage
34 - PMIC
35 - Power Management IC. An IC that contains numerous
39 - Consumer
40 - Electronic device that is supplied power by a regulator.
41 Consumers can be classified into two types:-
[all …]
|
| /linux-5.10/drivers/base/power/ |
| D | common.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * drivers/base/power/common.c - Common device power management code.
15 #include "power.h"
18 * dev_pm_get_subsys_data - Create or refcount power.subsys_data for device.
21 * If power.subsys_data is NULL, point it to a new object, otherwise increment
31 return -ENOMEM; in dev_pm_get_subsys_data()
33 spin_lock_irq(&dev->power.lock); in dev_pm_get_subsys_data()
35 if (dev->power.subsys_data) { in dev_pm_get_subsys_data()
36 dev->power.subsys_data->refcount++; in dev_pm_get_subsys_data()
38 spin_lock_init(&psd->lock); in dev_pm_get_subsys_data()
[all …]
|
| D | domain.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * drivers/base/power/domain.c - Common code related to device power domains.
25 #include "power.h"
34 __routine = genpd->dev_ops.callback; \
53 mutex_lock(&genpd->mlock); in genpd_lock_mtx()
59 mutex_lock_nested(&genpd->mlock, depth); in genpd_lock_nested_mtx()
64 return mutex_lock_interruptible(&genpd->mlock); in genpd_lock_interruptible_mtx()
69 return mutex_unlock(&genpd->mlock); in genpd_unlock_mtx()
80 __acquires(&genpd->slock) in genpd_lock_spin()
84 spin_lock_irqsave(&genpd->slock, flags); in genpd_lock_spin()
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | psci.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Power State Coordination Interface (PSCI)
10 - Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
14 ARM DEN 0022A ("Power State Coordination Interface System Software on ARM
15 processors") can be used by Linux to initiate various CPU-centric power
25 r0 => 32-bit Function ID / return value
26 {r1 - r3} => Parameters
31 [2] Power State Coordination Interface (PSCI) specification
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/soc/ti/ |
| D | sci-pm-domain.txt | 1 Texas Instruments TI-SCI Generic Power Domain
2 ---------------------------------------------
7 controller happens through a protocol known as TI-SCI [1].
11 PM Domain Node
13 The PM domain node represents the global PM domain managed by the PMMC, which
14 in this case is the implementation as documented by the generic PM domain
15 bindings in Documentation/devicetree/bindings/power/power-domain.yaml. Because
20 --------------------
21 - compatible: should be "ti,sci-pm-domain"
22 - #power-domain-cells: Can be one of the following:
[all …]
|
| /linux-5.10/drivers/gpu/drm/i915/display/ |
| D | intel_display_power.h | 1 /* SPDX-License-Identifier: MIT */
88 * IDs used to look up power wells. Power wells accessed directly bypassing
89 * the power domains framework must be assigned a unique ID. The rest of power
128 * interrupts located on the well). Called after the 0->1 refcount
135 * the 1->0 refcount transition.
151 /* Power well structure for haswell */
156 /* unique identifier for this power well */
159 * Arbitraty data associated with this power well. Platform and power
165 * request/status flag index in the PUNIT power well
176 * request/status flag index in the power well
[all …]
|
| /linux-5.10/include/linux/ |
| D | energy_model.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
14 * em_perf_state - Performance state of a performance domain
16 * @power: The power consumed at this level, in milli-watts (by 1 CPU or
17 by a registered device). It can be a total power: static and
20 * energy calculation. Equal to: power * max_frequency / frequency
24 unsigned long power; member
29 * em_perf_domain - Performance domain
32 * @cpus: Cpumask covering the CPUs of the domain. It's here
37 * In case of CPU device, a "performance domain" represents a group of CPUs
38 * whose performance is scaled together. All CPUs of a performance domain
[all …]
|
| D | cpu_pm.h | 1 /* SPDX-License-Identifier: GPL-2.0-only */
16 * When a CPU goes to a low power state that turns off power to the CPU's
17 * power domain, the contents of some blocks (floating point coprocessors,
18 * interrupt controllers, caches, timers) in the same power domain can
29 * CPU. They are used to save per-cpu context for affected blocks.
31 * CPU cluster notifications apply to all CPUs in a single power domain. They
33 * after all the CPUs in the power domain have been notified of the low power
41 /* A single cpu is entering a low power state */
44 /* A single cpu failed to enter a low power state */
47 /* A single cpu is exiting a low power state */
[all …]
|
| /linux-5.10/drivers/soc/imx/ |
| D | gpc.c | 1 // SPDX-License-Identifier: GPL-2.0+
3 * Copyright 2015-2017 Pengutronix, Lucas Stach <kernel@pengutronix.de>
4 * Copyright 2011-2013 Freescale Semiconductor, Inc.
65 /* Read ISO and ISO2SW power down delays */ in imx6_pm_domain_power_off()
66 regmap_read(pd->regmap, pd->reg_offs + GPC_PGC_PDNSCR_OFFS, &val); in imx6_pm_domain_power_off()
70 /* Gate off domain when powered down */ in imx6_pm_domain_power_off()
71 regmap_update_bits(pd->regmap, pd->reg_offs + GPC_PGC_CTRL_OFFS, in imx6_pm_domain_power_off()
74 /* Request GPC to power down domain */ in imx6_pm_domain_power_off()
75 val = BIT(pd->cntr_pdn_bit); in imx6_pm_domain_power_off()
76 regmap_update_bits(pd->regmap, GPC_CNTR, val, val); in imx6_pm_domain_power_off()
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/clock/ti/davinci/ |
| D | psc.txt | 1 Binding for TI DaVinci Power Sleep Controller (PSC)
3 The PSC provides power management, clock gating and reset functionality. It is
7 - compatible: shall be one of:
8 - "ti,da850-psc0" for PSC0 on DA850/OMAP-L138/AM18XX
9 - "ti,da850-psc1" for PSC1 on DA850/OMAP-L138/AM18XX
10 - reg: physical base address and size of the controller's register area
11 - #clock-cells: from common clock binding; shall be set to 1
12 - #power-domain-cells: from generic power domain binding; shall be set to 1.
13 - clocks: phandles to clocks corresponding to the clock-names property
14 - clock-names: list of parent clock names - depends on compatible value
[all …]
|
| /linux-5.10/include/dt-bindings/power/ |
| D | qcom-rpmpd.h | 1 /* SPDX-License-Identifier: GPL-2.0 */
7 /* SDM845 Power Domain Indexes */
18 /* SM8150 Power Domain Indexes */
31 /* SM8250 Power Domain Indexes */
43 /* SC7180 Power Domain Indexes */
53 /* SDM845 Power Domain performance levels */
67 /* MSM8976 Power Domain Indexes */
75 /* MSM8996 Power Domain Indexes */
84 /* MSM8998 Power Domain Indexes */
96 /* QCS404 Power Domains */
[all …]
|
| /linux-5.10/kernel/ |
| D | cpu_pm.c | 1 // SPDX-License-Identifier: GPL-2.0-only
46 * cpu_pm_register_notifier - register a driver with cpu_pm
50 * CPU and CPU cluster low power entry and exit.
62 * cpu_pm_unregister_notifier - unregister a driver with cpu_pm
77 * cpu_pm_enter - CPU low power entry notifier
79 * Notifies listeners that a single CPU is entering a low power state that may
80 * cause some blocks in the same power domain as the cpu to reset.
85 * co-processor, interrupt controller and its PM extensions, local CPU
98 * cpu_pm_exit - CPU low power exit notifier
100 * Notifies listeners that a single CPU is exiting a low power state that may
[all …]
|
| /linux-5.10/Documentation/devicetree/bindings/soc/bcm/ |
| D | raspberrypi,bcm2835-power.txt | 1 Raspberry Pi power domain driver
5 - compatible: Should be "raspberrypi,bcm2835-power".
6 - firmware: Reference to the RPi firmware device node.
7 - #power-domain-cells: Should be <1>, we providing multiple power domains.
9 The valid defines for power domain are:
37 power: power {
38 compatible = "raspberrypi,bcm2835-power";
40 #power-domain-cells = <1>;
43 Example for using power domain:
46 power-domains = <&power RPI_POWER_DOMAIN_USB>;
|
| /linux-5.10/drivers/soc/bcm/ |
| D | raspberrypi-power.c | 1 // SPDX-License-Identifier: GPL-2.0
13 #include <dt-bindings/power/raspberrypi-power.h>
14 #include <soc/bcm2835/raspberrypi-firmware.h>
17 * Firmware indices for the old power domains interface. Only a few
24 u32 domain; member
43 u32 domain; member
48 * Asks the firmware to enable or disable power on a specific power
49 * domain.
55 packet.domain = rpi_domain->domain; in rpi_firmware_set_power()
57 return rpi_firmware_property(rpi_domain->fw, in rpi_firmware_set_power()
[all …]
|
| /linux-5.10/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==
12 - compatible: Must be "stericsson,ux500-pm-domains".
13 - #power-domain-cells : Number of cells in a power domain specifier, must be 1.
17 compatible = "stericsson,ux500-pm-domains";
18 #power-domain-cells = <1>;
21 ==PM domain consumers==
24 - power-domains: A phandle and PM domain specifier. Below are the list of
[all …]
|