| /openbmc/linux/drivers/mfd/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
32 power supply alarms (hwmon).
45 tristate "Active-semi ACT8945A"
50 Support for the ACT8945A PMIC from Active-semi. This device
51 features three step-down DC/DC converters and four low-dropout
67 sun4i-gpadc-iio and the hwmon driver iio_hwmon.
70 called sun4i-gpadc.
94 tristate "ams AS3722 Power Management IC"
101 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
110 Multifunction Power Management IC. This includes
[all …]
|
| /openbmc/linux/drivers/net/wwan/iosm/ |
| H A D | iosm_ipc_pm.h | 1 /* SPDX-License-Identifier: GPL-2.0-only
3 * Copyright (C) 2020-21 Intel Corporation.
18 * union ipc_pm_cond - Conditions for D3 and the sleep message to CP.
35 * enum ipc_mem_host_pm_state - Possible states of the HOST SLEEP finite state
59 * enum ipc_mem_dev_pm_state - Possible states of the DEVICE SLEEP finite state
62 * power management state.
65 * and DOORBELL-IRQ-HPDA(data) values.
68 * @IPC_MEM_DEV_PM_WAKEUP: DOORBELL-IRQ-DEVICE_WAKE(data).
69 * @IPC_MEM_DEV_PM_HOST_SLEEP: DOORBELL-IRQ-HOST_SLEEP(data).
71 * @IPC_MEM_DEV_PM_FORCE_SLEEP: DOORBELL-IRQ-FORCE_SLEEP.
[all …]
|
| /openbmc/linux/drivers/soc/xilinx/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
5 bool "Enable Xilinx Zynq MPSoC Power Management driver"
11 Say yes to enable power management support for ZyqnMP SoC.
12 This driver uses firmware driver as an interface for power
13 management request to firmware. It registers isr to handle
14 power management callbacks from firmware. It registers mailbox client
15 to handle power management callbacks from firmware.
25 Say yes to enable device power management through PM domains
29 bool "Enable Xilinx Event Management Driver"
33 Say yes to enable event management support for Xilinx.
[all …]
|
| /openbmc/linux/Documentation/power/ |
| H A 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 …]
|
| H A 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
|
| /openbmc/linux/Documentation/driver-api/ |
| H A 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 …]
|
| /openbmc/docs/ |
| H A D | features.md | 5 - [BMCWeb][] HTTP/Web server
6 - [WebUI Vue][] web application
7 - REST Management: [BMCWeb Redfish][], [Phosphor REST APIs][] includes [Host
8 management REST APIs][]
9 - [D-Bus interfaces][] describes internal interfaces
10 - [D-Bus Object Mapper][]
11 - [Remote KVM][]
12 - [IPMI in band][] and [IPMI out of band][]
13 - Full IPMI 2.0 Compliance with DCMI
14 - SSH based SOL: [How to use][sol how to use]
[all …]
|
| /openbmc/linux/Documentation/driver-api/pm/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/admin-guide/pm/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/ABI/testing/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/networking/device_drivers/wifi/intel/ |
| H A 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 …]
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/apple/ |
| H A D | apple,pmgr.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Apple SoC Power Manager (PMGR)
10 - Hector Martin <marcan@marcan.st>
13 Apple SoCs include PMGR blocks responsible for power management,
14 which can control various clocks, resets, power states, and
16 with sub-nodes representing individual features.
20 pattern: "^power-management@[0-9a-f]+$"
24 - enum:
[all …]
|
| /openbmc/linux/drivers/base/power/ |
| H A D | clock_ops.c | 1 // SPDX-License-Identifier: GPL-2.0
3 * drivers/base/power/clock_ops.c - Generic clock manipulation PM callbacks
40 * pm_clk_list_lock - ensure exclusive access for modifying the PM clock
53 __acquires(&psd->lock) in pm_clk_list_lock()
55 mutex_lock(&psd->clock_mutex); in pm_clk_list_lock()
56 spin_lock_irq(&psd->lock); in pm_clk_list_lock()
60 * pm_clk_list_unlock - counterpart to pm_clk_list_lock().
65 __releases(&psd->lock) in pm_clk_list_unlock()
67 spin_unlock_irq(&psd->lock); in pm_clk_list_unlock()
68 mutex_unlock(&psd->clock_mutex); in pm_clk_list_unlock()
[all …]
|
| H A 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 …]
|
| /openbmc/linux/drivers/firmware/arm_scmi/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "ARM System Control and Management Interface Protocol"
5 tristate "ARM System Control and Management Interface (SCMI) Message Protocol"
8 ARM System Control and Management Interface (SCMI) protocol is a
9 set of operating system-independent software interfaces that are
10 used in system management. SCMI is extensible and currently provides
11 interfaces for: Discovery and self-description of the interfaces
12 it supports, Power domain management which is the ability to place
13 a given device or domain into the various power-saving states that
14 it supports, Performance management which is the ability to control
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/arm/marvell/ |
| H A D | armada-37xx.txt | 1 Power management
2 ----------------
4 For power management (particularly DVFS and AVS), the North Bridge
5 Power Management component is needed:
8 - compatible : should contain "marvell,armada-3700-nb-pm", "syscon";
9 - reg : the register start and length for the North Bridge
10 Power Management
15 compatible = "marvell,armada-3700-nb-pm", "syscon";
20 ---
25 - compatible : should contain "marvell,armada-3700-avs", "syscon";
[all …]
|
| /openbmc/linux/drivers/soc/fsl/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
15 The global utilities block controls power management, I/O device
16 enabling, power-onreset(POR) configuration monitoring, alternate
31 buffer management facilities for software to interact with
43 which can be used to dump the Management Complex and AIOP
51 (Run Control and Power Management), which performs all device-level
52 tasks associated with power management, such as wakeup source control.
|
| /openbmc/linux/Documentation/devicetree/bindings/regulator/ |
| H A D | renesas,raa215300.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Renesas RAA215300 Power Management Integrated Circuit (PMIC)
10 - Biju Das <biju.das.jz@bp.renesas.com>
13 The RAA215300 is a high-performance, low-cost 9-channel PMIC designed for
14 32-bit and 64-bit MCU and MPU applications. It supports DDR3, DDR3L, DDR4,
15 and LPDDR4 memory power requirements. The internally compensated regulators,
16 built-in Real-Time Clock (RTC), 32kHz crystal oscillator, and coin cell
17 battery charger provide a highly integrated, small footprint power solution
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/mfd/ |
| H A 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
10 - Matti Vaittinen <mazziesaccount@gmail.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 …]
|
| H A 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 …]
|
| /openbmc/openbmc/meta-facebook/meta-yosemite4/recipes-phosphor/state/phosphor-state-manager/ |
| H A D | chassis-powercycle | 6 # shellcheck source=meta-facebook/meta-yosemite4/recipes-phosphor/state/phosphor-state-manager/powe…
7 source /usr/libexec/phosphor-state-manager/power-cmd
8 # shellcheck source=meta-facebook/meta-yosemite4/recipes-yosemite4/plat-tool/files/yosemite4-common…
9 source /usr/libexec/yosemite4-common-functions
11 #IO 0:7 input port for showing slot 1:8 power status
12 #IO 8:16 output port for controlling slot 1:8 power status
14 IO_EXP_SLOT_PWR_STATUS=$((CHASSIS_ID - 1))
21 if [ -z "$MANAGEMENT_BOARD_VERSION" ]; then
22 echo "Failed to check management board fru info, sled cycle keep default setting"
25 GPIOCHIP_IO_EXP_SLOT_PWR_CTRL=$(basename "/sys/bus/i2c/devices/$SPIDER_BOARD_IO_EXP_BUS_NUM-00$IO_E…
[all …]
|
| /openbmc/linux/kernel/power/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
9 suspend-to-RAM state (e.g. the ACPI S3 state).
30 user-space before invoking suspend. There's a run-time switch
31 at '/sys/power/sync_on_suspend' to configure this behaviour.
32 This setting changes the default for the run-tim switch. Say Y
50 You can suspend your machine with 'echo disk > /sys/power/state'
60 for suspend states like suspend-to-RAM (STR) often don't work very
72 <file:Documentation/power/swsusp-and-swap-files.rst>).
81 For more information take a look at <file:Documentation/power/swsusp.rst>.
100 The default resume partition is the partition that the suspend-
[all …]
|
| /openbmc/linux/Documentation/scsi/ |
| H A 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
|
| /openbmc/linux/arch/m68k/ |
| H A D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
76 bool "MMU-based Paged Memory Management Support"
79 Select if you want MMU-based virtualised addressing space
80 support by paged memory management. If unsure, say 'Y'.
117 menu "Power management options"
120 bool "Power Management support"
122 Support processor power management modes
|
| /openbmc/linux/Documentation/devicetree/bindings/firmware/xilinx/ |
| H A D | xlnx,zynqmp-firmware.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/firmware/xilinx/xlnx,zynqmp-firmware.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Nava kishore Manne <nava.kishore.manne@amd.com>
12 description: The zynqmp-firmware node describes the interface to platform
15 can be used by any driver to communicate to PMUFW(Platform Management Unit).
16 These requests include clock management, pin control, device control,
17 power management service, FPGA service and other platform management
23 - description: For implementations complying for Zynq Ultrascale+ MPSoC.
[all …]
|