| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | README.md | 1 # phosphor-power-sequencer
5 The `phosphor-power-sequencer` application powers all the chassis in the system
6 on and off. It also monitors the power good (pgood) state in each chassis.
11 `phosphor-chassis-state-manager` application and the planned new
12 `phosphor-chassis-power` application. This disclaimer will be removed when this
17 `phosphor-power-sequencer` is a single-threaded C++ executable. It is a daemon
21 `phosphor-power-sequencer` is driven by an optional, system-specific JSON
24 chassis, power sequencer devices, voltage rails, GPIOs, and fault checks to
29 ## Power sequencer device
31 A power sequencer device enables (turns on) the voltage rails in the correct
[all …]
|
| H A D | powering_on.md | 3 ## Initiating a power on
6 Redfish command, or a power button on the system enclosure.
9 `org.openbmc.control.Power` D-Bus interface. The D-Bus object path is
13 The `phosphor-power-sequencer` application only supports powering on the entire
14 system. In a multiple chassis system, `phosphor-power-sequencer` does not
17 ## Determining which chassis to power on
19 In a single chassis system, `phosphor-power-sequencer` will always attempt to
20 power on the chassis.
22 In a multiple chassis system, `phosphor-power-sequencer` will only attempt to
23 power on chassis with the proper status:
[all …]
|
| H A D | powering_off.md | 3 ## Initiating a power off
6 Redfish command, or a power button on the system enclosure.
9 `org.openbmc.control.Power` D-Bus interface. The D-Bus object path is
13 The `phosphor-power-sequencer` application only supports powering off the entire
14 system. In a multiple chassis system, `phosphor-power-sequencer` does not
17 ## Determining which chassis to power off
19 In a single chassis system, `phosphor-power-sequencer` will always attempt to
20 power off the chassis.
22 In a multiple chassis system, `phosphor-power-sequencer` will only attempt to
23 power off chassis with the proper status:
[all …]
|
| H A D | power_loss.md | 1 # Power Loss
5 Power distribution in a computer system is complex. It typically flows from a
6 wall outlet to power supplies to voltage regulators to system components. Other
7 devices may exist between the wall outlet and the power supplies, such as an
8 Uninterruptible Power Supply (UPS) or an Enclosure Power Distribution Unit
11 A **brownout** is a partial reduction in voltage to the power supplies. In some
14 processor and other system components have lost power.
16 A **blackout** is a complete loss of power to the power supplies.
24 `phosphor-power-sequencer` application will take no action.
26 If the chassis was powered on when the brownout occurred, the power sequencer
[all …]
|
| H A D | chassis_status.md | 5 There are multiple D-Bus interfaces and properties that describe the chassis
6 status. The `phosphor-power-sequencer` application publishes one of those
8 used as input by `phosphor-power-sequencer.`
12 The `state` and `pgood` properties exist on the `org.openbmc.control.Power`
13 D-Bus interface.
15 `state` has a value of 0 or 1. `state` represents the desired power state for
19 `pgood` has a value of 0 or 1. `pgood` represents the power good (pgood) state
20 of the chassis. 0 means off, and 1 means on. This is the actual, current power
21 state. This property is set based on the chassis power good signal from the
22 power sequencer device.
[all …]
|
| H A D | monitoring_chassis_pgood.md | 1 # Monitoring Chassis Power Good
5 The power sequencer device provides a chassis power good (pgood) signal. This
6 indicates that all of the main (non-standby) voltage rails are powered on.
8 The `phosphor-power-sequencer` application periodically reads (polls) the
16 If the chassis pgood state is false when it should be true, a chassis power good
17 (pgood) fault has occurred. See [Power Good Faults](pgood_faults.md) for more
20 ## Unable to read chassis power good signal
22 `phosphor-power-sequencer` may become unable to read the chassis power good
25 - Hardware communication problems
26 - Unable to read from named GPIO after multiple retries.
[all …]
|
| H A D | pgood_faults.md | 1 # Power Good Faults
5 The power sequencer device provides a chassis power good (pgood) signal. This
6 indicates that all of the main (non-standby) voltage rails are powered on.
8 If the chassis pgood state is false when it should be true, a chassis power good
13 When the power sequencer device is powering on the main voltage rails in order,
14 one of the rails may fail to power on. This is often due to a hardware problem.
16 When a voltage rail fails to power on, the power sequencer device may
18 for the rail to power on. In both cases the chassis pgood signal never changes
26 A voltage rail may suddenly power off or stop providing the expected level of
30 The power sequencer device will detect that the voltage rail has failed. The
[all …]
|
| /openbmc/openbmc/meta-ibm/recipes-phosphor/packagegroups/ |
| H A D | packagegroup-obmc-apps.bbappend | 2 phosphor-power-monitor \
3 phosphor-power-systemd-links-monitor \
4 phosphor-power-sequencer \
5 phosphor-power-systemd-links-sequencer \
6 phosphor-power-utils \
7 phosphor-power \
12 phosphor-power-control \
13 phosphor-power-utils \
14 phosphor-power \
15 phosphor-power-regulators \
[all …]
|
| /openbmc/phosphor-power/ |
| H A D | .clang-tidy-ignore | 1 phosphor-power-supply/chassis.cpp
2 phosphor-power-supply/chassis.hpp
3 phosphor-power-supply/chassis_manager.cpp
4 phosphor-power-supply/chassis_manager.hpp
5 phosphor-power-supply/power_supply.cpp
6 phosphor-power-supply/power_supply.hpp
|
| H A D | README.md | 1 # phosphor-power chapter
6 that deliver power to the system.
8 Actively-maintained applications:
10 - cold-redundancy: Application that makes power supplies work in Cold Redundancy
12 - [phosphor-power-sequencer](phosphor-power-sequencer/README.md): JSON-driven
13 application that powers the chassis on/off and monitors the power sequencer
15 - [phosphor-power-supply](phosphor-power-supply/README.md): Next generation
16 power supply monitoring application.
17 - [phosphor-regulators](phosphor-regulators/README.md): JSON-driven application
19 - tools/power-utils: Power supply utilities.
[all …]
|
| H A D | meson.build | 2 'phosphor-power',
11 license: 'Apache-2.0',
20 add_global_arguments('-Wno-defaulted-function-deleted', language: 'cpp')
26 '-DBOOST_ALL_NO_LIB',
27 '-DBOOST_ASIO_DISABLE_THREADS',
28 '-DBOOST_ASIO_NO_DEPRECATED',
36 if get_option('oe-sdk').allowed()
40 '-c',
52 '-c',
53 'find ' + OECORE_TARGET_SYSROOT + '/lib/ld-*.so | sort -r -n | head -n1',
[all …]
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/chassis/ |
| H A D | phosphor-skeleton-control-power_git.bb | 1 SUMMARY = "org.openbmc.control.Power implementation for OpenBMC"
2 DESCRIPTION = "A power control implementation suitable for OpenBMC systems."
6 inherit skeleton-gdbus
7 inherit obmc-phosphor-dbus-service
12 SKELETON_DIR = "op-pwrctl"
14 DBUS_SERVICE:${PN} += "org.openbmc.control.Power@.service"
15 OBMC_CONTROL_INST = "org.openbmc.control.Power@{0}.service"
16 OBMC_CONTROL_SVC = "org.openbmc.control.Power@.service"
17 OBMC_CONTROL_FMT = "../${OBMC_CONTROL_SVC}:multi-user.target.wants/${OBMC_CONTROL_INST}"
22 phosphor-wait-power-on@.service \
[all …]
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/state/ |
| H A D | phosphor-state-manager_git.bb | 1 SUMMARY = "Phosphor State Management"
2 DESCRIPTION = "Phosphor State Manager provides a set of system state \
5 HOMEPAGE = "https://github.com/openbmc/phosphor-state-manager"
8 LICENSE = "Apache-2.0"
11 include phosphor-state-manager-systemd-links.inc
14 ${PN}-host \
15 ${PN}-chassis \
16 ${PN}-bmc \
17 ${PN}-hypervisor \
18 ${PN}-discover \
[all …]
|
| /openbmc/openbmc/meta-phosphor/recipes-phosphor/power/ |
| H A D | phosphor-power_git.bb | 1 SUMMARY = "Phosphor Power services and utilities"
2 DESCRIPTION = "Configure and monitor power supplies, power sequencers, and \
3 voltage regulators, and analyzes power devices for faults"
17 ${PN}-cold-redundancy \
18 ${PN}-monitor \
19 ${PN}-psu-monitor \
20 ${PN}-regulators \
21 ${PN}-sequencer \
22 ${PN}-control \
24 POWER_UTIL_PACKAGES = "${PN}-utils"
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-harma/recipes-phosphor/images/ |
| H A D | fb-harma-phosphor-image.inc | 3 # Monitor power status, for example, add handling for power good and post-end signals to manage pow…
5 phosphor-gpio-monitor \
10 phosphor-gpio-monitor-presence \
13 # Monitor Chassis power status
15 phosphor-power-control \
23 # Enable obmc-phosphor-buttons which needed by debug card function.
25 obmc-phosphor-buttons-signals \
26 obmc-phosphor-buttons-handler \
|
| /openbmc/openbmc/meta-facebook/meta-santabarbara/recipes-phosphor/images/ |
| H A D | fb-santabarbara-phosphor-image.inc | 3 # Enable obmc-phosphor-buttons which needed by debug card function.
5 obmc-phosphor-buttons-signals \
6 obmc-phosphor-button
[all...] |
| /openbmc/docs/designs/ |
| 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
19 occur. For example, some systems have op-panels, and on these op-panels there
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
[all …]
|
| /openbmc/openbmc/meta-facebook/meta-catalina/recipes-phosphor/gpio/ |
| H A D | phosphor-gpio-monitor_%.bbappend | 3 inherit obmc-phosphor-systemd systemd
6 file://phosphor-multi-gpio-monitor.json \
7 file://phosphor-multi-gpio-presence.json \
8 file://platform-gpio-monitor \
9 file://set-uart-select-led \
10 file://power-rail-assert-log@.service \
11 file://power-rail-deassert-log@.service \
12 file://power-rail-event-logger \
13 file://vr-fault-assert-log@.service \
14 file://vr-fault-deassert-log@.service \
[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
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]
15 - Power and Cooling Management: [Phosphor Fan Control][]
[all …]
|
| /openbmc/phosphor-state-manager/ |
| H A D | README.md | 1 # Phosphor State Manager Documentation
6 phosphor-state-manager (PSM) software is its support for requests to power on
9 This software also enforces any restore policy (i.e. auto power on system after
10 a system power event or bmc reset) and ensures its states are updated correctly
15 basic command line support to query and control phosphor-state-manager
17 OpenBMC system and utilizes D-Bus APIs. These D-Bus APIs are used for
21 phosphor-state-manager are D-Bus interfaces. These interfaces are then used by
27 phosphor-state-manager makes extensive use of systemd. There is a [writeup][1]
30 phosphor-state-manager monitors for systemd targets to complete as a trigger to
31 updating the its corresponding D-Bus property. When using PSM, a user must
[all …]
|
| /openbmc/phosphor-power/phosphor-power-sequencer/test/ |
| H A D | config_file_parser_error_tests.cpp | 8 * http://www.apache.org/licenses/LICENSE-2.0
22 using namespace phosphor::power::sequencer;
27 "/usr/share/phosphor-power-sequencer/foo.json"}; in TEST()
32 "ConfigFileParserError: /usr/share/phosphor-power-sequencer/foo.json: " in TEST()
39 "/usr/share/phosphor-power-sequencer/bar.json"}; in TEST()
47 "/usr/share/phosphor-power-sequencer/bar.json"}; in TEST()
51 "ConfigFileParserError: /usr/share/phosphor-power-sequencer/bar.json: " in TEST()
|
| /openbmc/openbmc/meta-facebook/meta-santabarbara/recipes-phosphor/gpio/ |
| H A D | phosphor-gpio-monitor_%.bbappend | 3 inherit obmc-phosphor-systemd systemd
5 SERVICE_LIST = "assert-post-end.service \
6 assert-power-good-drop.service \
7 assert-rese
[all...] |
| /openbmc/openbmc/meta-facebook/meta-harma/recipes-phosphor/gpio/ |
| H A D | phosphor-gpio-monitor_%.bbappend | 3 inherit obmc-phosphor-systemd systemd
5 SRC_URI += "file://assert-post-end \
6 file://assert-post-end.service \
7 file://assert-power-good \
8 file://assert-power-good.service \
9 file://assert-reset-button \
10 file://assert-reset-button.service \
11 file://auto-power \
12 file://auto-poweroff \
13 file://auto-poweroff@.service \
[all …]
|
| /openbmc/phosphor-power/phosphor-regulators/docs/ |
| H A D | README.md | 1 # phosphor-regulators
5 The `phosphor-regulators` application configures and monitors voltage
9 monitor their Power Good (pgood) status. Those operations are typically
10 performed by power sequencer hardware and the
11 [`phosphor-power-sequencer`](../../phosphor-power-sequencer/docs/README.md)
17 planned new `phosphor-chassis-power` application. This disclaimer will be
22 `phosphor-regulators` is a single-threaded C++ executable. It is a 'daemon'
26 The application is driven by a system-specific JSON configuration file. The JSON
35 `phosphor-regulators` can modify the configuration of voltage regulators, such
42 `phosphor-regulators` supports two types of regulator monitoring:
[all …]
|
| /openbmc/phosphor-state-manager/service_files/ |
| H A D | meson.build | 2 'phosphor-systemd-target-monitor.service',
3 'phosphor-discover-system-state@.service',
4 'obmc-power-start@.service',
5 'obmc-power-stop@.service',
6 'obmc-powered-off@.service',
7 'phosphor-reboot-host@.service',
8 'phosphor-reset-chassis-on@.service',
9 'phosphor-reset-chassis-running@.service',
10 'phosphor-reset-host-reboot-attempts@.service',
11 'phosphor-reset-host-recovery@.service',
[all …]
|