Searched +full:power +full:- +full:management (Results 1 – 25 of 305) sorted by relevance
12345678910>>...13
| /Documentation/driver-api/ |
| D | dcdbas.rst | 2 Dell Systems Management Base Driver
8 The Dell Systems Management Base Driver provides a sysfs interface for
9 systems management software such as Dell OpenManage to perform system
10 management interrupts and host control actions (system power cycle or
11 power off after OS shutdown) on certain Dell systems.
24 System Management Interrupt
27 On some Dell systems, systems management software must access certain
28 management information via a system management interrupt (SMI). The SMI data
29 buffer must reside in 32-bit address space, and the physical address of the
32 The driver creates the following sysfs entries for systems management
[all …]
|
| /Documentation/admin-guide/pm/ |
| D | strategies.rst | 1 .. SPDX-License-Identifier: GPL-2.0
5 Power Management Strategies
13 The Linux kernel supports two major high-level power management strategies.
15 One of them is based on using global low-power states of the whole system in
17 significantly reduced, referred to as :doc:`sleep states <sleep-states>`. The
23 :doc:`system-wide power management <system-wide>`.
25 The other strategy, referred to as the :doc:`working-state power management
26 <working-state>`, is based on adjusting the power states of individual hardware
30 a metastate covering a range of different power states of the system in which
32 ``inactive`` (idle). If they are active, they have to be in power states
[all …]
|
| /Documentation/power/ |
| D | pci.rst | 2 PCI Power Management
7 An overview of concepts and the Linux kernel's interfaces related to PCI power
8 management. Based on previous work by Patrick Mochel <mochel@transmeta.com>
11 This document only covers the aspects of power management specific to PCI
13 power management refer to Documentation/driver-api/pm/devices.rst and
14 Documentation/power/runtime_pm.rst.
18 1. Hardware and Platform Support for PCI Power Management
19 2. PCI Subsystem and Device Power Management
20 3. PCI Device Drivers and Power Management
24 1. Hardware and Platform Support for PCI Power Management
[all …]
|
| D | apm-acpi.rst | 6 odds are it supports either Advanced Power Management (APM) or
7 Advanced Configuration and Power Interface (ACPI). ACPI is the newer
8 of the two technologies and puts power management in the hands of the
9 operating system, allowing for more intelligent power management than
21 simply cannot mix and match the two. Only one power management
24 User-space Daemons
25 ------------------
26 Both APM and ACPI rely on user-space daemons, apmd and acpid
|
| /Documentation/ABI/testing/ |
| D | sysfs-class-scsi_host | 7 Storage Control Unit embeds up to two 4-port controllers in
34 Contact: linux-ide@vger.kernel.org
37 (interface) power management.
42 least possible power when possible. This may sacrifice some
44 power states.
46 max_performance: Generally, this means no power management.
47 Tell the controller to have performance be a priority over power
48 management.
50 medium_power: Tell the controller to enter a lower power state
51 when possible, but do not enter the lowest power state, thus
[all …]
|
| D | sysfs-devices-real_power_state | 7 power management methods and use ACPI power resources for power
8 management.
11 power state of the given device node as returned by the _PSC
12 control method or inferred from the configuration of power
14 "D3cold", reflect the power state names defined by the ACPI
19 the same device object. If that happens, some shared power
23 This attribute is read-only.
|
| D | sysfs-class-devlink | 7 denoted as ... above, is of the form <supplier>--<consumer>
21 - 'consumer unbind'
22 - 'supplier unbind'
23 - 'never'
46 runtime power management behavior of the consumer and supplier
53 '0' Does not affect runtime power management
54 '1' Affects runtime power management
69 See also: sysfs-devices-state_synced.
73 - 'not tracked'
74 - 'dormant'
[all …]
|
| /Documentation/devicetree/bindings/mfd/ |
| D | twl-family.txt | 3 The TWLs are Integrated Power Management Chips.
10 - compatible : Must be "ti,twl4030";
11 For Integrated power-management/audio CODEC device used in OMAP3
13 - compatible : Must be "ti,twl6030";
14 For Integrated power-management used in OMAP4 based boards
15 - interrupts : This i2c device has an IRQ line connected to the main SoC
16 - interrupt-controller : Since the twl support several interrupts internally,
18 - #interrupt-cells = <1>;
21 - Child nodes contain in the twl. The twl family is made of several variants
28 * Integrated Power Management Chip
[all …]
|
| D | sprd,sc27xx-pmic.txt | 1 Spreadtrum SC27xx Power Management Integrated Circuit (PMIC)
5 mobile handset power management, audio codec, battery management and user
8 - DCDCs to support CPU, memory.
9 - LDOs to support both internal and external requirement.
10 - Battery management system, such as charger, fuel gauge.
11 - Audio codec.
12 - User interface function, such as indicator, flash LED and so on.
13 - IC level interface, such as power on/off control, RTC and typec and so on.
16 - compatible: Should be one of the following:
22 - reg: The address of the device chip select, should be 0.
[all …]
|
| 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
8 - compatible : must be one of the following
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
[all …]
|
| D | rohm,bd71847-pmic.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/mfd/rohm,bd71847-pmic.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: ROHM BD71847 and BD71850 Power Management Integrated Circuit bindings
10 - Matti Vaittinen <matti.vaittinen@fi.rohmeurope.com>
13 BD71847AMWV and BD71850MWV are programmable Power Management ICs for powering
14 single-core, dual-core, and quad-core SoCs such as NXP-i.MX 8M. It is
18 …s://www.rohm.com/products/power-management/power-management-ic-for-system/industrial-consumer-appl…
19 …s://www.rohm.com/products/power-management/power-management-ic-for-system/industrial-consumer-appl…
[all …]
|
| /Documentation/driver-api/pm/ |
| D | devices.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Device Power Management Basics
10 :Copyright: |copy| 2010-2011 Rafael J. Wysocki <rjw@sisk.pl>, Novell Inc.
17 Most of the code in Linux is device drivers, so most of the Linux power
18 management (PM) code is also driver-specific. Most drivers will do very
22 This writeup gives an overview of how drivers interact with system-wide
23 power management goals, emphasizing the models and interfaces that are
25 background for the domain-specific work you'd do with any specific driver.
28 Two Models for Device Power Management
31 Drivers will use one or both of these models to put devices into low-power
[all …]
|
| /Documentation/scsi/ |
| D | link_power_management_policy.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 Link Power Managent Policy
7 This parameter allows the user to set the link (interface) power management.
14 least possible power when possible. This may
16 when coming out of lower power states.
18 max_performance Generally, this means no power management. Tell
20 over power management.
22 medium_power Tell the controller to enter a lower power state
23 when possible, but do not enter the lowest power
|
| /Documentation/devicetree/bindings/arm/marvell/ |
| D | armada-37xx.txt | 2 --------------------------------------------------
7 - compatible: must contain "marvell,armada3710"
12 - compatible: must contain "marvell,armada3720"
16 compatible = "marvell,armada-3720-db", "marvell,armada3720", "marvell,armada3710";
19 Power management
20 ----------------
22 For power management (particularly DVFS and AVS), the North Bridge
23 Power Management component is needed:
26 - compatible : should contain "marvell,armada-3700-nb-pm", "syscon";
27 - reg : the register start and length for the North Bridge
[all …]
|
| /Documentation/networking/device_drivers/wifi/intel/ |
| D | ipw2100.rst | 1 .. SPDX-License-Identifier: GPL-2.0
10 - Intel(R) PRO/Wireless 2100 Network Connection
12 Copyright |copy| 2003-2006, Intel Corporation
16 :Version: git-1.1.5
23 2. Release git-1.1.5 Current Features
28 7. Power Management
51 parameters include, without limitation, RF power, spectrum usage,
64 the warranty and/or issues arising from regulatory non-compliance, and
69 modules, and accordingly, condition system-level regulatory approval
72 non-compliant.
[all …]
|
| /Documentation/driver-api/xilinx/ |
| D | eemi.rst | 6 -------------------------------------
7 The zynqmp-firmware node describes the interface to platform firmware.
10 used by any driver to communicate with PMC(Platform Management Controller).
12 Embedded Energy Management Interface (EEMI)
13 ----------------------------------------------
14 The embedded energy management interface is used to allow software
16 device to communicate with a power management controller (PMC) on a
17 device to issue or respond to power management requests.
23 ------
30 - IOCTL_SET_PLL_FRAC_MODE 8
[all …]
|
| /Documentation/devicetree/bindings/power/supply/ab8500/ |
| D | fg.txt | 3 AB8500 is a mixed signal multimedia and power management
4 device comprising: power and energy-management-module,
5 wall-charger, usb-charger, audio codec, general purpose adc,
6 tvout, clock management and sim card interface.
8 Fuelgauge support is part of energy-management-modules, other
10 main-charger, usb-combo-charger and battery-temperature-monitoring.
15 - compatible = This shall be: "stericsson,ab8500-fg"
16 - battery = Shall be battery specific information
19 compatible = "stericsson,ab8500-fg";
30 thermistor-on-batctrl:
[all …]
|
| /Documentation/devicetree/bindings/spmi/ |
| D | spmi.yaml | 1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: System Power Management Interface (SPMI) Controller
10 - Stephen Boyd <sboyd@kernel.org>
13 The System Power Management (SPMI) controller is a 2-wire bus defined
14 by the MIPI Alliance for power management control to be used on SoC designs.
30 "#address-cells":
33 "#size-cells":
37 "@[0-9a-f]$":
[all …]
|
| /Documentation/driver-api/thermal/ |
| D | nouveau_thermal.rst | 12 -----------
17 Currently, due to the absence of in-kernel API to access HWMON drivers, Nouveau
19 have one of those, temperature and/or fan management through Nouveau's HWMON
23 Temperature management
24 ----------------------
26 Temperature is exposed under as a read-only HWMON attribute temp1_input.
34 The GPU will be downclocked to reduce its power dissipation;
36 The GPU is put on hold to further lower power dissipation;
55 Fan management
56 --------------
[all …]
|
| /Documentation/devicetree/bindings/firmware/ |
| D | nvidia,tegra210-bpmp.txt | 1 NVIDIA Tegra210 Boot and Power Management Processor (BPMP)
3 The Boot and Power Management Processor (BPMP) is a co-processor found
5 process as well as to assisting in entering deep low power state
12 - compatible
15 - "nvidia,tegra210-bpmp"
16 - reg: physical base address and length for HW synchornization primitives
19 - interrupts: specifies the interrupt number for receiving messages ("rx")
23 - #clock-cells : Should be 1 for platforms where DRAM clock control is
29 compatible = "nvidia,tegra210-bpmp";
34 interrupt-names = "tx", "rx";
|
| D | nvidia,tegra186-bpmp.txt | 1 NVIDIA Tegra Boot and Power Management Processor (BPMP)
4 booting process handling and offloading the power management, clock
5 management, and reset control tasks from the CPU. The binding document
11 - compatible
14 - "nvidia,tegra186-bpmp"
15 - mboxes : The phandle of mailbox controller and the mailbox specifier.
16 - shmem : List of the phandle of the TX and RX shared memory area that
18 - #clock-cells : Should be 1.
19 - #power-domain-cells : Should be 1.
20 - #reset-cells : Should be 1.
[all …]
|
| /Documentation/devicetree/bindings/arm/ |
| D | zte,sysctrl.txt | 5 System management required properties:
6 - compatible = "zte,sysctrl"
8 Low power management required properties:
9 - compatible = "zte,zx296702-pcu"
12 - compatible = "zte,zx-bus-matrix"
17 System management required properties:
18 - compatible = "zte,zx296718-aon-sysctrl"
19 - compatible = "zte,zx296718-sysctrl"
22 aon_sysctrl: aon-sysctrl@116000 {
23 compatible = "zte,zx296718-aon-sysctrl", "syscon";
[all …]
|
| /Documentation/devicetree/bindings/power/reset/ |
| D | xlnx,zynqmp-power.txt | 1 --------------------------------------------------------------------
2 Device Tree Bindings for the Xilinx Zynq MPSoC Power Management
3 --------------------------------------------------------------------
4 The zynqmp-power node describes the power management configurations.
8 - compatible: Must contain: "xlnx,zynqmp-power"
9 - interrupts: Interrupt specifier
12 - mbox-names : Name given to channels seen in the 'mboxes' property.
13 "tx" - Mailbox corresponding to transmit path
14 "rx" - Mailbox corresponding to receive path
15 - mboxes : Standard property to specify a Mailbox. Each value of
[all …]
|
| /Documentation/devicetree/bindings/power/ |
| D | renesas,apmu.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: "http://devicetree.org/schemas/power/renesas,apmu.yaml#"
5 $schema: "http://devicetree.org/meta-schemas/core.yaml#"
7 title: Renesas Advanced Power Management Unit
10 - Geert Uytterhoeven <geert+renesas@glider.be>
11 - Magnus Damm <magnus.damm@gmail.com>
14 Renesas R-Car Gen2 and RZ/G1 SoCs utilize one or more APMU hardware units for
15 CPU core power domain control including SMP boot and CPU Hotplug.
20 - enum:
[all …]
|
| /Documentation/devicetree/bindings/arm/hisilicon/controller/ |
| D | hi6220-domain-ctrl.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/arm/hisilicon/controller/hi6220-domain-ctrl.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Wei Xu <xuwei5@hisilicon.com>
14 such as: the power Always On domain controller, the Media domain
15 controller(e.g. codec, G3D ...) and the Power Management domain
19 Power Always ON domain controller --> hisilicon,hi6220-aoctrl
20 Media domain controller --> hisilicon,hi6220-mediactrl
21 Power Management domain controller --> hisilicon,hi6220-pmctrl
[all …]
|
12345678910>>...13