| /openbmc/openbmc-test-automation/redfish/extended/ |
| H A D | test_power_capping.robot | 2 Documentation Energy scale power capping tests.
6 # PL Power Limit
35 [Documentation] Change active power limit with system power on and
36 ... Power limit active.
39 Set DCMI Power Limit And Verify ${max_power}
41 Redfish Power On stack_mode=skip
67 ${power}= Get DCMI Power Limit
68 Should Be True ${power} == ${max_power}
69 ... msg=DCMI power limit should be ${max_power}.
71 Activate DCMI Power And Verify
[all …]
|
| H A D | test_escale_base.robot | 28 # The power limits are documented in
29 # open-power/witherspoon-xml/master/witherspoon.xml.
36 [Documentation] Run base power tests with DCMI power monitoring off.
39 Deactivate DCMI Power And Verify
40 Verify Power Limits
44 [Documentation] Run base power tests with DCMI power monitoring on.
47 Activate DCMI Power And Verify
48 Verify Power Limits
51 Escale Power Setting Via REST And Verify
52 [Documentation] Set power via REST and check using IPMI.
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/power/ |
| H A D | rockchip,power-controller.yaml | 4 $id: http://devicetree.org/schemas/power/rockchip,power-controller.yaml#
7 title: Rockchip Power Domains
14 Rockchip processors include support for multiple power domains
16 application scenarios to save power.
18 Power domains contained within power-controller node are
19 generic power domain providers documented in
20 Documentation/devicetree/bindings/power/power-domain.yaml.
22 IP cores belonging to a power domain should contain a
23 "power-domains" property that is a phandle for the
24 power domain node representing the domain.
[all …]
|
| H A D | mediatek,power-controller.yaml | 4 $id: http://devicetree.org/schemas/power/mediatek,power-controller.yaml#
7 title: Mediatek Power Domains Controller
14 Mediatek processors include support for multiple power domains which can be
15 powered up/down by software based on different application scenes to save power.
17 IP cores belonging to a power domain should contain a 'power-domains'
22 pattern: '^power-controller(@[0-9a-f]+)?$'
26 - mediatek,mt6795-power-controller
27 - mediatek,mt8167-power-controller
28 - mediatek,mt8173-power-controller
29 - mediatek,mt8183-power-controller
[all …]
|
| H A 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'
46 description: list of power domains provided by this controller.
56 "power-domain@[0-9a-f]+$":
[all …]
|
| H A 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)([@-].*)?$"
36 power-domain provider. The idle state definitions are compatible with the
47 Phandles to the OPP tables of power domains provided by a power domain
48 provider. If the provider provides a single power domain only or all
49 the power domains provided by the provider have identical OPP tables,
53 "#power-domain-cells":
57 domains (e.g. power controllers), but can be any value as specified
[all …]
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/dbus/power-supply-policy/ |
| H A D | power-supply-policy.yaml | 1 # Machine power supply policy for PDM.
3 # Create an error if a power supply is removed while the system is powered on
5 - name: power supply0
9 - meta: POWER SUPPLY
12 - name: power supply1
16 - meta: POWER SUPPLY
19 - name: power supplies
21 'The machine has two power supplies to monitor.'
25 - meta: POWER SUPPLY
27 - meta: POWER SUPPLY
[all …]
|
| /openbmc/linux/arch/arm64/boot/dts/apple/ |
| H A D | t8112-pmgr.dtsi | 3 * PMGR Power domains for the Apple T8112 "M2" SoC
10 ps_sbr: power-controller@100 {
13 #power-domain-cells = <0>;
19 ps_aic: power-controller@108 {
22 #power-domain-cells = <0>;
28 ps_dwi: power-controller@110 {
31 #power-domain-cells = <0>;
37 ps_soc_spmi0: power-controller@118 {
40 #power-domain-cells = <0>;
45 ps_gpio: power-controller@120 {
[all …]
|
| H A D | t8103-pmgr.dtsi | 3 * PMGR Power domains for the Apple T8103 "M1" SoC
10 ps_sbr: power-controller@100 {
13 #power-domain-cells = <0>;
19 ps_aic: power-controller@108 {
22 #power-domain-cells = <0>;
28 ps_dwi: power-controller@110 {
31 #power-domain-cells = <0>;
37 ps_soc_spmi0: power-controller@118 {
40 #power-domain-cells = <0>;
45 ps_soc_spmi1: power-controller@120 {
[all …]
|
| H A D | t600x-pmgr.dtsi | 3 * PMGR Power domains for the Apple T6001 "M1 Max" SoC
9 DIE_NODE(ps_pms_bridge): power-controller@100 {
12 #power-domain-cells = <0>;
18 DIE_NODE(ps_aic): power-controller@108 {
21 #power-domain-cells = <0>;
27 DIE_NODE(ps_dwi): power-controller@110 {
30 #power-domain-cells = <0>;
36 DIE_NODE(ps_pms): power-controller@118 {
39 #power-domain-cells = <0>;
45 DIE_NODE(ps_gpio): power-controller@120 {
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
| H A D | Power_v1.xml | 4 <!--# Redfish Schema: Power v1.7.3 -->
43 <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="Power">
47 <EntityType Name="Power" BaseType="Resource.v1_0_0.Resource" Abstract="true">
48 ….Description" String="The `Power` schema describes power metrics and represents the properties for…
49 …<Annotation Term="OData.LongDescription" String="This resource shall contain the power metrics for…
58 …tring="Any writable properties, such as limits and exceptions, can be updated for power metrics."/>
68 <String>/redfish/v1/Chassis/{ChassisId}/Power</String>
73 <String>/redfish/v1/Chassis/{ChassisId}/Power</String>
88 … <Annotation Term="OData.Description" String="This action resets the targeted power supply."/>
89 …power supply specified by the `MemberId` from the `PowerSupplies` array. A `GracefulRestart` `Res…
[all …]
|
| /openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
| H A D | Power_v1.xml | 4 <!--# Redfish Schema: Power v1.7.3 -->
43 <Schema xmlns="http://docs.oasis-open.org/odata/ns/edm" Namespace="Power">
47 <EntityType Name="Power" BaseType="Resource.v1_0_0.Resource" Abstract="true">
48 ….Description" String="The `Power` schema describes power metrics and represents the properties for…
49 …<Annotation Term="OData.LongDescription" String="This resource shall contain the power metrics for…
58 …tring="Any writable properties, such as limits and exceptions, can be updated for power metrics."/>
68 <String>/redfish/v1/Chassis/{ChassisId}/Power</String>
73 <String>/redfish/v1/Chassis/{ChassisId}/Power</String>
88 … <Annotation Term="OData.Description" String="This action resets the targeted power supply."/>
89 …power supply specified by the `MemberId` from the `PowerSupplies` array. A `GracefulRestart` `Res…
[all …]
|
| /openbmc/docs/designs/ |
| H A D | psu-monitoring.md | 1 # Power Supply Monitoring Application
11 This is a proposal to provide a set of enhancements to the current OpenBMC power
13 may consist of a number of configuration variations including different power
15 different power supplies is needed in order to initialize the power supplies,
23 that contains a power supply monitor application and a power sequencer monitor
24 application. The current power supply application is lacking things desired for
28 a single power supply application that can communicate with one or more
29 [PMBus][2] power supplies and provide the enterprise features currently lacking
31 power supply.
38 1. The power supply application must detect, isolate, and report individual
[all …]
|
| H A D | power-recovery.md | 1 # OpenBMC Server Power Recovery
11 Modern computer systems have a feature, automated power-on recovery, which in
13 power to the system. If the system had a black out (i.e. power was completely
14 cut to the system), should it automatically power the system on? Should it leave
16 at before the power loss.
18 There are also instances where the user may not want automatic power recovery to
22 situations, the user may wish for the system to not automatically power on the
26 run once the power is restored. For example, IBM requires all LED's be toggled
30 A brownout is another scenario that commonly utilizes automated power-on
32 told) that chassis power can no longer be supported, but power to the BMC will
[all …]
|
| /openbmc/linux/drivers/base/power/ |
| H A D | runtime.c | 3 * drivers/base/power/runtime.c - Helper functions for device runtime PM
17 #include "power.h"
55 * update_pm_runtime_accounting - Update the time accounting of power states
58 * In order to be able to have time accounting of the various power states
69 if (dev->power.disable_depth > 0) in update_pm_runtime_accounting()
72 last = dev->power.accounting_timestamp; in update_pm_runtime_accounting()
75 dev->power.accounting_timestamp = now; in update_pm_runtime_accounting()
87 if (dev->power.runtime_status == RPM_SUSPENDED) in update_pm_runtime_accounting()
88 dev->power.suspended_time += delta; in update_pm_runtime_accounting()
90 dev->power.active_time += delta; in update_pm_runtime_accounting()
[all …]
|
| /openbmc/openbmc-test-automation/lib/ |
| H A D | energy_scale_utils.robot | 2 Documentation Utilities for power management tests.
16 Get System Power Cap Limit
17 [Documentation] Get the allowed MAX and MIN power limit of the chassis.
19 # GET request of /redfish/v1/Chassis/chassis/EnvironmentMetrics | grep -A5 Power
32 DCMI Power Get Limits
33 [Documentation] Run dcmi power get_limit and return values as a
36 # This keyword packages the five lines returned by dcmi power get_limit
38 # Current Limit State: No Active Power Limit
39 # Exception actions: Hard Power Off & Log Event to SEL
40 # Power Limit: 500 Watts
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/clock/ |
| H A D | fsl,imx8-acm.yaml | 26 power-domains:
48 - power-domains
62 power-domains:
64 - description: power domain of IMX_SC_R_AUDIO_CLK_0
65 - description: power domain of IMX_SC_R_AUDIO_CLK_1
66 - description: power domain of IMX_SC_R_MCLK_OUT_0
67 - description: power domain of IMX_SC_R_MCLK_OUT_1
68 - description: power domain of IMX_SC_R_AUDIO_PLL_0
69 - description: power domain of IMX_SC_R_AUDIO_PLL_1
70 - description: power domain of IMX_SC_R_ASRC_0
[all …]
|
| /openbmc/linux/Documentation/devicetree/bindings/soc/mediatek/ |
| H A 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 …]
|
| /openbmc/openbmc/meta-facebook/meta-minerva/recipes-phosphor/gpio/phosphor-gpio-monitor/ |
| H A D | minerva-phosphor-multi-gpio-monitor.json | 8 "FALLING": ["power-good-assert@mtia-blade-1.service"],
9 "RISING": ["power-good-deassert@mtia-blade-1.service"]
19 "FALLING": ["power-good-assert@mtia-blade-2.service"],
20 "RISING": ["power-good-deassert@mtia-blade-2.service"]
30 "FALLING": ["power-good-assert@mtia-blade-3.service"],
31 "RISING": ["power-good-deassert@mtia-blade-3.service"]
41 "FALLING": ["power-good-assert@mtia-blade-4.service"],
42 "RISING": ["power-good-deassert@mtia-blade-4.service"]
52 "FALLING": ["power-good-assert@mtia-blade-5.service"],
53 "RISING": ["power-good-deassert@mtia-blade-5.service"]
[all …]
|
| /openbmc/linux/drivers/net/ipa/ |
| H A D | ipa_power.c | 23 * DOC: IPA Power Management
26 * interconnects (buses) it depends on are enabled. Runtime power
38 * enum ipa_power_flag - IPA power flags
43 * @IPA_POWER_FLAG_COUNT: Number of defined power flags
54 * struct ipa_power - IPA power management information
67 spinlock_t spinlock; /* used with STOPPED/STARTED power flags */
74 static int ipa_interconnect_init(struct ipa_power *power, in ipa_interconnect_init() argument
82 interconnect = &power->interconnect[0]; in ipa_interconnect_init()
83 for (i = 0; i < power->interconnect_count; i++) { in ipa_interconnect_init()
92 ret = of_icc_bulk_get(power->dev, power->interconnect_count, in ipa_interconnect_init()
[all …]
|
| /openbmc/u-boot/include/ |
| H A D | power-domain.h | 10 * A power domain is a portion of an SoC or chip that is powered by a
11 * switchable source of power. In many cases, software has control over the
12 * power domain, and can turn the power source on or off. This is typically
13 * done to save power by powering off unused devices, or to enable software
15 * drivers to turn power domains on and off.
17 * A driver that implements UCLASS_POWER_DOMAIN is a power domain controller or
18 * provider. A controller will often implement multiple separate power domains,
20 * power-domain-uclass.h describes the interface which power domain controllers
23 * Depending on the power domain controller hardware, changing the state of a
24 * power domain may require performing related operations on other resources.
[all …]
|
| /openbmc/linux/drivers/staging/nvec/ |
| H A D | nvec_power.c | 3 * nvec_power: power supply driver for a NVIDIA compliant embedded controller
87 struct nvec_power *power = in nvec_power_notifier() local
95 if (power->on != res->plu) { in nvec_power_notifier()
96 power->on = res->plu; in nvec_power_notifier()
109 static void get_bat_mfg_data(struct nvec_power *power) in get_bat_mfg_data() argument
116 nvec_write_async(power->nvec, buf, 2); in get_bat_mfg_data()
123 struct nvec_power *power = in nvec_power_bat_notifier() local
134 if (power->bat_present == 0) { in nvec_power_bat_notifier()
136 get_bat_mfg_data(power); in nvec_power_bat_notifier()
139 power->bat_present = 1; in nvec_power_bat_notifier()
[all …]
|
| /openbmc/linux/drivers/power/supply/ |
| H A D | axp20x_usb_power.c | 3 * AXP20x PMIC USB power supply status driver
26 #define DRVNAME "axp20x-usb-power-supply"
79 static bool axp20x_usb_vbus_needs_polling(struct axp20x_usb_power *power) in axp20x_usb_vbus_needs_polling() argument
86 if (power->axp_data->vbus_needs_polling && !power->online) in axp20x_usb_vbus_needs_polling()
94 struct axp20x_usb_power *power = devid; in axp20x_usb_power_irq() local
96 power_supply_changed(power->supply); in axp20x_usb_power_irq()
98 mod_delayed_work(system_power_efficient_wq, &power->vbus_detect, DEBOUNCE_TIME); in axp20x_usb_power_irq()
105 struct axp20x_usb_power *power = in axp20x_usb_power_poll_vbus() local
110 ret = regmap_read(power->regmap, AXP20X_PWR_INPUT_STATUS, &val); in axp20x_usb_power_poll_vbus()
115 if (val != power->old_status) in axp20x_usb_power_poll_vbus()
[all …]
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | README.md | 1 # phosphor-power-sequencer
5 The phosphor-power-sequencer application powers the chassis on/off and monitors
6 the power sequencer device.
8 If the chassis power good (pgood) status changes to false unexpectedly, the
9 application uses information from the power sequencer device to determine the
20 creates a collection of C++ objects. These objects represent the power sequencer
23 ## Power sequencer device
25 A power sequencer device enables (turns on) the voltage rails in the correct
28 This application currently supports the following power sequencer device types:
39 `org.openbmc.control.Power` D-Bus interface.
[all …]
|
| /openbmc/u-boot/arch/powerpc/dts/ |
| H A D | e6500_power_isa.dtsi | 3 * e6500 Power ISA Device Tree Source (include)
11 power-isa-version = "2.06";
12 power-isa-b; // Base
13 power-isa-e; // Embedded
14 power-isa-atb; // Alternate Time Base
15 power-isa-cs; // Cache Specification
16 power-isa-ds; // Decorated Storage
17 power-isa-e.ed; // Embedded.Enhanced Debug
18 power-isa-e.pd; // Embedded.External PID
19 power-isa-e.hv; // Embedded.Hypervisor
[all …]
|