| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | multiple_chassis.md | 33 powered off.
36 chassis, the system will be powered off and then powered on again without that
43 If a single chassis system that was powered on experiences a brownout, the
44 system will be powered off.
46 If a multiple chassis system that was powered on experiences a brownout in one
47 chassis, the system will be powered off and then powered on again without that
54 If a single chassis system that was powered on experiences a blackout, the
59 If a multiple chassis system that was powered on experiences a blackout in one
60 chassis, that chassis loses all power. The system will be powered off and then
61 powered on again without that chassis.
|
| H A D | chassis_status.md | 17 is being powered [on](powering_on.md) or [off](powering_off.md).
39 When the system is powered off, the `state` and `pgood` properties for both
42 When the system is being powered on, the `state` property of both object paths
43 is set to 1. When the chassis has successfully powered on, the `pgood` property
46 When the system is being powered off, the `state` property of both object paths
47 is set to 0. When the chassis has successfully powered off, the `pgood` property
56 When the system is powered off, the `state` and `pgood` properties for all of
59 When the system is being powered on, the `state` will be changed to 1 for the
60 system and for all chassis that **can** be powered on. It may not be possible to
64 When an individual chassis has successfully powered on, the `pgood` property for
[all …]
|
| H A D | pgood_faults.md | 6 indicates that all of the main (non-standby) voltage rails are powered on.
21 ## Pgood fault after the system was powered on
23 A pgood fault can occur after a system has been powered on. The system may have
41 - Chassis was powered on: pgood signal changes from true to false.
50 - The system will be [powered off](powering_off.md).
53 were powered on are also experiencing a pgood fault. If so, check if any
60 - The system will be powered [off](powering_off.md) and then
62 - Chassis with an `Enabled` value of false will **not** be powered back on.
69 When the pgood error happens **after** the system was powered on, the
95 STATUS_VOUT error bits might be set for a pgood fault after the system powered
|
| H A D | powering_on.md | 5 The system can be powered on by several methods, such as the `obmcutil` tool, a
31 that is being powered on. It will set `state` to 0 for each chassis not being
32 powered on.
47 In each chassis being powered on, the power sequencer device powers on the
52 When all voltage rails have been successfully powered on in a chassis, the power
63 When all chassis that were being powered on have finished,
70 After all chassis have powered on, the rest of the boot process continues. The
78 the rails may fail to power on. Similarly, after the system has powered on, one
|
| H A D | power_loss.md | 12 situations, the standby voltage rails are still powered on but the main voltage
13 rails are powered off. As a result, the BMC may still be running, but the host
23 If the chassis was powered off when the brownout occurred, the
26 If the chassis was powered on when the brownout occurred, the power sequencer
40 When power is restored, if the system was previously powered on, it may be
41 automatically powered on again by the `phosphor-chassis-state-manager`
77 again. The chassis with `Available` set to false will **not** be powered
|
| H A D | powering_off.md | 5 The system can be powered off by several methods, such as the `obmcutil` tool, a
42 In each chassis being powered off, the power sequencer device powers off the
47 When the voltage rails have been powered off in a chassis, the power sequencer
58 When all chassis that were being powered off have finished,
|
| H A D | monitoring_chassis_pgood.md | 6 indicates that all of the main (non-standby) voltage rails are powered on.
51 `Available` or `Enabled` property is false, the chassis will not be powered
57 after the chassis powered on, the application will do the following:
68 property is false, the chassis will not be powered on.
|
| /openbmc/phosphor-state-manager/service_files/ |
| H A D | obmc-powered-off@.service | 12 # obmc-chassis-powered-off@.target, that is started after it is
16 ExecStart=/bin/systemctl start obmc-chassis-powered-off@%i.target
17 SyslogIdentifier=phosphor-powered-off
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/dbus/bios-policy/ |
| H A D | bios-policy.yaml | 10 - name: chassis powered
27 properties: chassis powered
36 properties: chassis powered
|
| /openbmc/phosphor-power/phosphor-regulators/src/ |
| H A D | manager.hpp | 66 * This method should be called when the system is being powered on. It
80 * Regulator monitoring should be enabled when the system is being powered
84 * Regulator monitoring should be disabled when the system is being powered
89 * while the system is powered on. This allows other applications or tools
132 * While the system was powered off, hardware could have been added,
164 * Returns whether the system is currently powered on.
166 * @return true if system is powered on, false otherwise
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/dbus/fan-policy/swift/ |
| H A D | water-cooled.yaml | 62 - name: chassis powered
108 properties: chassis powered
138 properties: chassis powered
253 properties: chassis powered
263 properties: chassis powered
273 properties: chassis powered
|
| H A D | air-cooled.yaml | 62 - name: chassis powered
108 properties: chassis powered
138 properties: chassis powered
253 properties: chassis powered
263 properties: chassis powered
273 properties: chassis powered
|
| H A D | fan-errors.yaml | 8 # The system must be powered on in both of these cases.
97 - name: chassis powered
125 properties: chassis powered
242 properties: chassis powered
255 properties: chassis powered
268 properties: chassis powered
281 properties: chassis powered
294 properties: chassis powered
307 properties: chassis powered
320 properties: chassis powered
[all …]
|
| /openbmc/phosphor-buttons/inc/ |
| H A D | host_then_chassis_poweroff.hpp | 93 * @brief Determines if system (chassis) is powered on.
132 * @brief Sets the time the host will be powered off if the
141 * @brief Sets the time the chassis will be powered off if the
171 * @brief When the host will be powered off.
176 * @brief When the chassis will be powered off.
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/dbus/fan-policy/witherspoon/ |
| H A D | fan-errors.yaml | 8 # The system must be powered on in both of these cases.
98 - name: chassis powered
126 properties: chassis powered
243 properties: chassis powered
256 properties: chassis powered
269 properties: chassis powered
282 properties: chassis powered
295 properties: chassis powered
308 properties: chassis powered
321 properties: chassis powered
[all …]
|
| H A D | water-cooled.yaml | 81 - name: chassis powered
136 properties: chassis powered
166 properties: chassis powered
301 properties: chassis powered
311 properties: chassis powered
321 properties: chassis powered
|
| H A D | air-cooled.yaml | 87 - name: chassis powered
142 properties: chassis powered
172 properties: chassis powered
307 properties: chassis powered
317 properties: chassis powered
327 properties: chassis powered
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/Decorator/ |
| H A D | PowerState.interface.yaml | 17 The state of the object is powered on.
20 The state of the object is powered off.
|
| /openbmc/phosphor-bmc-code-mgmt/bios/ |
| H A D | spi_device.hpp | 89 // - host is powered off
95 // - host is powered off
106 // - host is powered off
118 // - host is powered off
|
| /openbmc/phosphor-fan-presence/control/json/actions/ |
| H A D | pcie_card_floors.hpp | 37 * - Watches for PCIe slots to be powered on (or off).
38 * - Reads four properties off of the PCIeDevice interface on the powered
46 * - If a powered on card has its own temperature sensor, then it doesn't
48 * - Since the slot powered on indications are all sent at once, it has a
94 * when it expires. Done to handle the flood of slot powered
|
| /openbmc/u-boot/include/ |
| H A D | generic-phy.h | 99 * @phy: PHY port to be powered on
101 * During runtime, the PHY may need to be powered on or off several
113 * @phy: PHY port to be powered off
115 * During runtime, the PHY may need to be powered on or off several
154 * @phy: PHY port to be powered on
162 * @phy: PHY port to be powered off
|
| /openbmc/u-boot/drivers/power/domain/ |
| H A D | imx8-power-domain.c | 60 /* Already powered on */ in imx8_power_domain_on()
75 debug("%s is powered on\n", dev->name); in imx8_power_domain_on()
94 /* Already powered off */ in imx8_power_domain_off_node()
125 debug("%s is powered off\n", dev->name); in imx8_power_domain_off_node()
149 /* Already powered off */ in imx8_power_domain_off_parentnodes()
185 debug("%s is powered off\n", parent->name); in imx8_power_domain_off_parentnodes()
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/dbus/power-supply-policy/ |
| H A D | power-supply-policy.yaml | 3 # Create an error if a power supply is removed while the system is powered on
50 - name: chassis powered
76 properties: chassis powered
85 properties: chassis powered
|
| /openbmc/openbmc-test-automation/openpower/ |
| H A D | test_timed_power_on.robot | 47 Test Timed Powered On Via BMC
52 # Make sure the host is powered off.
72 Test Timed Powered On Via Host OS
77 # Make sure the host is powered on and booted to host OS partition.
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/ |
| H A D | Thermal.events.yaml | 39 A event signaling that a device has potentially been powered off
45 and may have been powered off.
|