Searched full:power (Results 1 – 25 of 1297) sorted by relevance
12345678910>>...52
| /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:
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.
13 "rockchip,rk3228-power-controller" - for RK3228 SoCs.
[all …]
|
| /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
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
17 - include/dt-bindings/power/mt7622-power.h
30 - #power-domain-cells: Must be 1
[all …]
|
| /Documentation/devicetree/bindings/power/ |
| D | fsl,imx-gpcv2.yaml | 4 $id: http://devicetree.org/schemas/power/fsl,imx-gpcv2.yaml#
7 title: Freescale i.MX General Power Controller v2
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
19 described as subnodes of the power gating controller 'pgc' node.
21 IP cores belonging to a power domain should contain a 'power-domains'
42 description: list of power domains provided by this controller.
45 "power-domain@[0-9]$":
[all …]
|
| D | power-domain.yaml | 4 $id: http://devicetree.org/schemas/power/power-domain.yaml#
16 used for power gating of selected IP blocks for power saving by reduced leakage
24 \#power-domain-cells property in the PM domain provider node.
28 pattern: "^(power-controller|power-domain)([@-].*)?$"
34 power-domain provider. The idle state definitions are compatible with the
46 Phandles to the OPP tables of power domains provided by a power domain
47 provider. If the provider provides a single power domain only or all
48 the power domains provided by the provider have identical OPP tables,
52 "#power-domain-cells":
56 domains (e.g. power controllers), but can be any value as specified
[all …]
|
| D | power_domain.txt | 4 used for power gating of selected IP blocks for power saving by reduced leakage
12 #power-domain-cells property in the PM domain provider node.
16 See power-domain.yaml.
21 - power-domains : A list of PM domain specifiers, as defined by bindings of
22 the power controller that is the PM domain provider.
25 - power-domain-names : A list of power domain name strings sorted in the same
26 order as the power-domains property. Consumers drivers will use
27 power-domain-names to match power domains with power-domains
35 power-domains = <&power 0>;
36 power-domain-names = "io";
[all …]
|
| D | fsl,imx-gpc.yaml | 4 $id: http://devicetree.org/schemas/power/fsl,imx-gpc.yaml#
7 title: Freescale i.MX General Power Controller
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
18 described as subnodes of the power gating controller 'pgc' node of the GPC.
20 IP cores belonging to a power domain should contain a 'power-domains'
21 property that is a phandle pointing to the power domain the device belongs
46 description: list of power domains provided by this controller.
[all …]
|
| D | brcm,bcm63xx-power.yaml | 4 $id: "http://devicetree.org/schemas/power/brcm,bcm63xx-power.yaml#"
7 title: BCM63xx power domain driver
13 BCM6318, BCM6328, BCM6362 and BCM63268 SoCs have a power domain controller
14 to enable/disable certain components in order to save power.
20 - brcm,bcm6318-power-controller
21 - brcm,bcm6328-power-controller
22 - brcm,bcm6362-power-controller
23 - brcm,bcm63268-power-controller
28 "#power-domain-cells":
34 - "#power-domain-cells"
[all …]
|
| D | pd-samsung.yaml | 4 $id: http://devicetree.org/schemas/power/pd-samsung.yaml#
7 title: Samsung Exynos SoC Power Domains
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#
41 "#power-domain-cells":
44 power-domains:
49 - "#power-domain-cells"
56 lcd0_pd: power-domain@10023c80 {
59 #power-domain-cells = <0>;
[all …]
|
| D | renesas,sysc-rmobile.txt | 8 - Power management.
24 match the Power Area Hierarchy in the Power Domain Specifications section of
32 Documentation/devicetree/bindings/power/power-domain.yaml.
34 The nodes should be named by the real power area names, and thus their names
38 - #power-domain-cells: Must be 0.
42 index number for the corresponding power area in the various Power
64 #power-domain-cells = <0>;
70 #power-domain-cells = <0>;
74 #power-domain-cells = <0>;
80 #power-domain-cells = <0>;
[all …]
|
| /Documentation/hwmon/ |
| D | occ.rst | 15 embedded on POWER processors. The OCC is a device that collects and aggregates
17 sensor data as well as perform thermal and power management on the system.
77 power[1-n]_input
78 Latest measured power reading of the component in
80 power[1-n]_average
81 Average power of the component in microwatts.
82 power[1-n]_average_interval
83 The amount of time over which the power average
86 [with power sensor version < 2]
88 power[1-n]_label
[all …]
|
| D | acpi_power_meter.rst | 4 This driver talks to ACPI 4.0 power meters.
19 This driver implements sensor reading support for the power meters exposed in
21 features--a power meter that returns average power use over a configurable
23 sysfs interface conforms with the specification outlined in the "Power" section
29 The `power[1-*]_is_battery` knob indicates if the power supply is a battery.
30 Both `power[1-*]_average_{min,max}` must be set before the trip points will work.
33 `power[1-*]_average` sysfs file.
35 The `power[1-*]_{model_number, serial_number, oem_info}` fields display
39 Some computers have the ability to enforce a power cap in hardware. If this is
40 the case, the `power[1-*]_cap` and related sysfs files will appear. When the
[all …]
|
| D | fam15h_power.rst | 25 1) Processor TDP (Thermal design power)
27 Given a fixed frequency and voltage, the power consumption of a
28 processor varies based on the workload being executed. Derated power
29 is the power consumed when running a specific application. Thermal
30 design power (TDP) is an example of derated power.
32 This driver permits reading of registers providing power information
35 For AMD Family 15h and 16h processors the following power values can
40 Specifies in watts the maximum amount of power
44 Specifies in watts the maximum amount of power
47 Specifies in watts the current amount of power being
[all …]
|
| D | lochnagar.rst | 30 power1_average Measured average power for DBVDD1 (microWatts)
31 power1_average_interval Power averaging time input valid from 1 to 1708mS
37 power2_average Measured average power for 1V8 DSP (microWatts)
38 power2_average_interval Power averaging time input valid from 1 to 1708mS
44 power3_average Measured average power for 1V8 CDC (microWatts)
45 power3_average_interval Power averaging time input valid from 1 to 1708mS
51 power4_average Measured average power for VDDCORE DSP (microWatts)
52 power4_average_interval Power averaging time input valid from 1 to 1708mS
58 power5_average Measured average power for AVDD 1V8 (microWatts)
59 power5_average_interval Power averaging time input valid from 1 to 1708mS
[all …]
|
| /Documentation/power/powercap/ |
| D | powercap.rst | 2 Power Capping Framework
5 The power capping framework provides a consistent interface between the kernel
6 and the user space that allows power capping drivers to expose the settings to
12 The framework exposes power capping devices to user space via sysfs in the
14 'control types', which correspond to different methods of power capping. For
16 Power Limit" (RAPL) technology, whereas the 'idle-injection' control type
17 corresponds to the use of idle injection for controlling power.
19 Power zones represent different parts of the system, which can be controlled and
20 monitored using the power capping method determined by the control type the
21 given zone belongs to. They each contain attributes for monitoring power, as
[all …]
|
| D | dtpm.rst | 4 Dynamic Thermal Power Management framework
12 Another aspect is to sustain the performance for a given power budget,
15 reduce the battery charging because the dissipated power is too high
16 compared with the power consumed by other devices.
19 different devices by limiting their power given an application
22 The Dynamic Thermal Power Management (DTPM) is a technique acting on
23 the device power by limiting and/or balancing a power budget among
27 device power.
34 driver to do the connection with the power manageable device.
36 The DTPM is a tree representation describing the power constraints
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-powercap | 6 The powercap/ class sub directory belongs to the power cap
8 Documentation/power/powercap/powercap.rst for details.
16 Here <control type> determines how the power is going to be
17 controlled. A <control type> can contain multiple power zones.
24 This allows to enable/disable power capping for a "control type".
25 This status affects every power zone using this "control_type.
27 What: /sys/class/powercap/<control type>/<power zone>
32 A power zone is a single or a collection of devices, which can
33 be independently monitored and controlled. A power zone sysfs
37 What: /sys/class/powercap/<control type>/<power zone>/<child power zone>
[all …]
|
| D | sysfs-power | 1 What: /sys/power/
5 The /sys/power directory will contain files that will
6 provide a unified interface to the power management
9 What: /sys/power/state
13 The /sys/power/state file controls system sleep states.
15 labels, which may be "mem" (suspend), "standby" (power-on
24 What: /sys/power/mem_sleep
28 The /sys/power/mem_sleep file controls the operating mode of
32 to suspend the system (by writing "mem" to the /sys/power/state
42 What: /sys/power/disk
[all …]
|
| /Documentation/devicetree/bindings/soc/bcm/ |
| D | raspberrypi,bcm2835-power.txt | 1 Raspberry Pi power domain driver
5 - compatible: Should be "raspberrypi,bcm2835-power".
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>;
|
| D | brcm,bcm2835-pm.txt | 1 BCM2835 PM (Power domains, watchdog)
3 The PM block controls power domains and some reset lines, and includes
19 - #power-domain-cells: Should be 1. This property follows the power domain
25 - system-power-controller: Whether the watchdog is controlling the
26 system power. This node follows the power controller bindings[3].
29 [2] Documentation/devicetree/bindings/power/power-domain.yaml
30 [3] Documentation/devicetree/bindings/power/power-controller.txt
36 #power-domain-cells = <1>;
45 system-power-controller;
|
| /Documentation/devicetree/bindings/mfd/ |
| D | twl4030-power.txt | 1 Texas Instruments TWL family (twl4030) reset and power management module
3 The power management module inside the TWL family provides several facilities
4 to control the power resources, including power scripts. For now, the
9 "ti,twl4030-power"
10 "ti,twl4030-power-reset"
11 "ti,twl4030-power-idle"
12 "ti,twl4030-power-idle-osc-off"
14 The use of ti,twl4030-power-reset is recommended at least on
17 When using ti,twl4030-power-idle, the TI recommended configuration
20 When using ti,twl4030-power-idle-osc-off, the TI recommended
[all …]
|
| D | max77620.txt | 1 MAX77620 Power management IC from Maxim Semiconductor.
21 - system-power-controller: Indicates that this PMIC is controlling the
22 system power, see [1] for more details.
24 [1] Documentation/devicetree/bindings/power/power-controller.txt
29 Flexible power sequence configurations:
31 The Flexible Power Sequencer (FPS) allows each regulator to power up under
32 hardware or software control. Additionally, each regulator can power on
33 independently or among a group of other regulators with an adjustable power-up
34 and power-down delays (sequencing). GPIO1, GPIO2, and GPIO3 can be programmed
46 Each regulator, GPIO1, GPIO2, GPIO3, and 32KHz clock has a flexible power
[all …]
|
| /Documentation/sound/designs/ |
| D | powersave.rst | 2 Notes on Power-Saving Mode
5 AC97 and HD-audio drivers have the automatic power-saving mode.
9 With the automatic power-saving, the driver turns off the codec power
11 the device and/or no analog loopback is set, the power disablement is
12 done fully or partially. It'll save a certain power consumption, thus
15 The time-out for automatic power-off can be specified via ``power_save``
18 power-saving. The default value of timeout is given via
27 automatic power-save mode with 10 seconds, write to
34 Note that you might hear click noise/pop when changing the power
36 power-down to the active state. These are often hardly to fix, so
[all …]
|
| /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
27 - Electronic device that supplies power to other devices.
35 - Power Management IC. An IC that contains numerous
40 - Electronic device that is supplied power by a regulator.
45 power supply. Its supply voltage is set by the hardware,
52 - Power Domain
53 - Electronic circuit that is supplied its input power by the
54 output power of a regulator, switch or by another power
65 That is one regulator and three power domains:
[all …]
|
| /Documentation/driver-api/thermal/ |
| D | cpu-idle-cooling.rst | 13 act on a cooling device to mitigate the dissipated power. When the
20 to the static leakage. The only solution is to power down the
24 Last but not least, the system can ask for a specific power budget but
25 because of the OPP density, we can only choose an OPP with a power
28 with a power less than the requested power budget and the next OPP
29 exceeds the power budget. An intermediate OPP could have been used if
39 power budget.
43 plethora of OPP density, and some have large power gap between OPPs,
45 loss of power in other scenarios.
51 this state). So the sustainable power with idle cycles has a linear
[all …]
|
| D | power_allocator.rst | 2 Power allocator governor tunables
22 The power allocator governor implements a
24 temperature as the control input and power as the controlled output:
48 | S |-----+----->| sum e |----->| X |--->| S |-->| S |-->|power |
60 Sustainable power
63 An estimate of the sustainable dissipatable power (in mW) should be
65 sustained power that can be dissipated at the desired control
66 temperature. This is the maximum sustained power for allocation at
67 the desired maximum temperature. The actual sustained power can vary
72 the thermal ramp. For reference, the sustainable power of a 4" phone
[all …]
|
12345678910>>...52