| /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 | 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 | 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 | 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.
|
| H A D | named_gpios.md | 5 The main (non-standby) voltage rails in a chassis are powered on or off by
20 indicating whether all the main (non-standby) rails are 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
|
| H A D | meson.build | 6 'obmc-powered-off@.service',
|
| /openbmc/u-boot/drivers/phy/ |
| H A D | phy-stm32-usbphyc.c | 60 bool powered; member
137 if (usbphyc->phys[i].powered) in stm32_usbphyc_is_powered()
233 usbphyc_phy->powered = true; in stm32_usbphyc_phy_power_on()
245 usbphyc_phy->powered = false; in stm32_usbphyc_phy_power_off()
364 usbphyc_phy->powered = false; in stm32_usbphyc_probe()
|
| /openbmc/phosphor-state-manager/target_files/ |
| H A D | obmc-fan-control-ready@.target | 3 Conflicts=obmc-chassis-powered-off@%i.target
|
| /openbmc/phosphor-fan-presence/control/service_files/yaml/ |
| H A D | phosphor-fan-control@.service | 3 Conflicts=obmc-chassis-powered-off@%i.target
|
| H A D | phosphor-fan-control-init@.service | 5 Conflicts=obmc-chassis-powered-off@%i.target
|
| /openbmc/phosphor-fan-presence/monitor/service_files/yaml/ |
| H A D | phosphor-fan-monitor@.service | 3 Conflicts=obmc-chassis-powered-off@%i.target
|
| H A D | phosphor-fan-monitor-init@.service | 5 Conflicts=obmc-chassis-powered-off@%i.target
|
| /openbmc/openbmc/meta-quanta/meta-gbs/recipes-google/acpi-power-state/acpi-power-state-daemon/ |
| H A D | gbs-host-ready.target | 2 Description=Host is ready to be powered on
|
| /openbmc/openbmc/meta-ampere/meta-jefferson/recipes-phosphor/fans/phosphor-pid-control/ |
| H A D | phosphor-pid-control.service | 4 Conflicts=obmc-chassis-powered-off@0.target
|
| /openbmc/phosphor-fan-presence/presence/service_files/yaml/ |
| H A D | phosphor-fan-presence-tach@.service | 5 Conflicts=obmc-chassis-powered-off@%i.target
|
| /openbmc/openpower-host-ipmi-oem/ |
| H A D | README.md | 35 1. Power the chassis off. The host needs to be powered off because the factory
43 Because the chassis is powered off, the host does not receive a return code when
|
| /openbmc/openbmc/meta-facebook/recipes-phosphor/state/ |
| H A D | phosphor-state-manager_%.bbappend | 20 obmc-chassis-poweroff@{}.target.requires/obmc-powered-off@{}.service \
|
| /openbmc/boost-dbus/ |
| H A D | README.md | 4 This is a simple D-Bus binding powered by Boost.Asio.
|
| /openbmc/u-boot/board/microchip/pic32mzda/ |
| H A D | README | 8 This family is powered by MIPS M14KEC 32bit general purpose core and has
|
| /openbmc/u-boot/doc/device-tree-bindings/usb/ |
| H A D | tegra-usb.txt | 13 activated for the bus to be powered.
|
| /openbmc/phosphor-power/phosphor-regulators/docs/ |
| H A D | internal_design.md | 14 - Represents a physical enclosure that can be powered on and off by the BMC.
|