Home
last modified time | relevance | path

Searched +full:power +full:- +full:domain +full:- (Results 1 – 25 of 1046) sorted by relevance

12345678910>>...42

/kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/rockchip/
Dpower_domain.txt1 * 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 …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/power/
Dpower_domain.txt4 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==
17 - #power-domain-cells : Number of cells in a PM domain specifier;
18 Typically 0 for nodes representing a single PM domain and 1 for nodes
19 providing multiple PM domains (e.g. power controllers), but can be any value
23 - power-domains : A phandle and PM domain specifier as defined by bindings of
[all …]
Drenesas,sysc-rmobile.txt1 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 …]
Dpd-samsung.txt1 * Samsung Exynos Power Domains
3 Exynos processors include support for multiple power domains which are used
4 to gate power to one or more peripherals on the processor.
7 - compatible: should be one of the following.
8 * samsung,exynos4210-pd - for exynos4210 type power domain.
9 * samsung,exynos5433-pd - for exynos5433 type power domain.
10 - reg: physical base address of the controller and length of memory mapped
12 - #power-domain-cells: number of cells in power domain specifier;
16 - label: Human readable string with domain name. Will be visible in userspace
18 - power-domains: phandle pointing to the parent power domain, for more details
[all …]
Dfsl,imx-gpc.txt1 Freescale i.MX General Power Controller
4 The i.MX6 General Power Control (GPC) block contains DVFS load tracking
5 counters and Power Gating Control (PGC).
8 - compatible: Should be one of the following:
9 - fsl,imx6q-gpc
10 - fsl,imx6qp-gpc
11 - fsl,imx6sl-gpc
12 - fsl,imx6sx-gpc
13 - reg: should be register base and length as documented in the
15 - interrupts: Should contain one interrupt specifier for the GPC interrupt
[all …]
Dfsl,imx-gpcv2.txt1 Freescale i.MX General Power Controller v2
4 The i.MX7S/D General Power Control (GPC) block contains Power Gating
5 Control (PGC) for various power domains.
9 - compatible: Should be "fsl,imx7d-gpc"
11 - reg: should be register base and length as documented in the
14 - interrupts: Should contain GPC interrupt request 1
16 Power domains contained within GPC node are generic power domain
18 Documentation/devicetree/bindings/power/power_domain.txt, which are
19 described as subnodes of the power gating controller 'pgc' node,
24 - reg: Power domain index. Valid values are defined in
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/power/
Dpower-domain.yaml1 # 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 …]
Dpower_domain.txt4 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 …]
Dfsl,imx-gpcv2.yaml1 # 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 …]
Drenesas,sysc-rmobile.txt1 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 …]
Dfsl,imx-gpc.yaml1 # 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 …]
Dpd-samsung.yaml1 # 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 …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/soc/rockchip/
Dpower_domain.txt1 * 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,rk3128-power-controller" - for RK3128 SoCs.
11 "rockchip,rk3228-power-controller" - for RK3228 SoCs.
12 "rockchip,rk3288-power-controller" - for RK3288 SoCs.
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/soc/mediatek/
Dscpsys.txt4 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.txt. 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/mt2701-power.h
15 - include/dt-bindings/power/mt2712-power.h
16 - include/dt-bindings/power/mt7622-power.h
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/mediatek/
Dscpsys.txt4 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 …]
/kernel/linux/linux-4.19/Documentation/power/regulator/
Doverview.txt10 The intention is to allow systems to dynamically control regulator power output
11 in order to save power and prolong battery life. This applies to both voltage
22 Some terms used in this document:-
24 o Regulator - Electronic device that supplies power to other devices.
28 Input Voltage -> Regulator -> Output Voltage
31 o PMIC - Power Management IC. An IC that contains numerous regulators
35 o Consumer - Electronic device that is supplied power by a regulator.
36 Consumers can be classified into two types:-
40 power supply. Its supply voltage is set by the hardware,
47 o Power Domain - Electronic circuit that is supplied its input power by the
[all …]
/kernel/linux/linux-5.10/Documentation/power/regulator/
Doverview.rst11 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 …]
/kernel/linux/linux-5.10/drivers/base/power/
Dcommon.c1 // 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 …]
Ddomain.c1 // 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 …]
/kernel/linux/linux-4.19/drivers/base/power/
Dcommon.c2 * drivers/base/power/common.c - Common device power management code.
17 #include "power.h"
20 * dev_pm_get_subsys_data - Create or refcount power.subsys_data for device.
23 * If power.subsys_data is NULL, point it to a new object, otherwise increment
33 return -ENOMEM; in dev_pm_get_subsys_data()
35 spin_lock_irq(&dev->power.lock); in dev_pm_get_subsys_data()
37 if (dev->power.subsys_data) { in dev_pm_get_subsys_data()
38 dev->power.subsys_data->refcount++; in dev_pm_get_subsys_data()
40 spin_lock_init(&psd->lock); in dev_pm_get_subsys_data()
41 psd->refcount = 1; in dev_pm_get_subsys_data()
[all …]
Ddomain.c2 * drivers/base/power/domain.c - Common code related to device power domains.
24 #include "power.h"
33 __routine = genpd->dev_ops.callback; \
52 mutex_lock(&genpd->mlock); in genpd_lock_mtx()
58 mutex_lock_nested(&genpd->mlock, depth); in genpd_lock_nested_mtx()
63 return mutex_lock_interruptible(&genpd->mlock); in genpd_lock_interruptible_mtx()
68 return mutex_unlock(&genpd->mlock); in genpd_unlock_mtx()
79 __acquires(&genpd->slock) in genpd_lock_spin()
83 spin_lock_irqsave(&genpd->slock, flags); in genpd_lock_spin()
84 genpd->lock_flags = flags; in genpd_lock_spin()
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/
Dpsci.yaml1 # 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 …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/soc/ti/
Dsci-pm-domain.txt1 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 …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/soc/ti/
Dsci-pm-domain.txt1 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.txt. Because
20 --------------------
21 - compatible: should be "ti,sci-pm-domain"
22 - #power-domain-cells: Must be 1 so that an id can be provided in each
[all …]
/kernel/linux/linux-5.10/drivers/gpu/drm/i915/display/
Dintel_display_power.h1 /* 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 …]

12345678910>>...42