| /openbmc/docs/designs/ |
| H A D | power-recovery.md | 30 A brownout is another scenario that commonly utilizes automated power-on
31 recovery features. A brownout is a scenario where BMC firmware detects (or is
34 feature to turn chassis power back on as soon as the brownout condition ends.
38 brownout scenario. A UPS has a limited amount of power so it's main purpose is
119 ### Brownout subsection
121 As noted above, a brownout condition is when AC power can not continue to be
128 - Log an error indicating the brownout event has occurred
130 policy if they wish for when the brownout completes
131 - Identify when a brownout condition has completed
132 - Wait for the brownout to complete and implement the one-time power restore
[all …]
|
| /openbmc/phosphor-power/phosphor-power-sequencer/docs/ |
| H A D | power_loss.md | 11 A **brownout** is a partial reduction in voltage to the power supplies. In some
18 In a multiple chassis system, a brownout or blackout might only occur in some of
21 ## System behavior during a brownout
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
|
| H A D | multiple_chassis.md | 43 If a single chassis system that was powered on experiences a brownout, the
46 If a multiple chassis system that was powered on experiences a brownout in one
|
| H A D | chassis_status.md | 180 `Fault`, it means that the chassis is experiencing a blackout or brownout. A
220 - The chassis is experiencing a brownout.
|
| H A D | pgood_faults.md | 54 chassis is experiencing a brownout or blackout. This determines whether this
|
| /openbmc/u-boot/arch/arm/cpu/arm926ejs/mxs/ |
| H A D | spl_power_init.c | 507 * Here we set the 4p2 brownout level to something very close to 4.2V. in mxs_power_init_4p2_regulator()
508 * We then check the brownout status. If the brownout status is false, in mxs_power_init_4p2_regulator()
511 * If the brownout status is true, we need to ramp us the current limit in mxs_power_init_4p2_regulator()
513 * current limit until the brownout status is false or until we've in mxs_power_init_4p2_regulator()
516 debug("SPL: Setting 4P2 brownout level\n"); in mxs_power_init_4p2_regulator()
780 * VDDIO has a brownout, then the VDD5V_GT_VDDIO becomes in mxs_handle_5v_conflict()
783 debug("SPL: VDDIO has a brownout\n"); in mxs_handle_5v_conflict()
845 * mxs_init_batt_bo() - Configure battery brownout threshold
847 * This function configures the battery input brownout threshold. The value
848 * at which the battery brownout happens is configured to 3.0V in the code.
[all …]
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/ |
| H A D | Chassis.interface.yaml | 77 - name: "BrownOut"
79 Chassis power status is in a brownout condition.
|
| /openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/State/Decorator/ |
| H A D | PowerSystemInputs.interface.yaml | 22 normal chassis operation, such as in a Brownout/Blackout
|
| /openbmc/phosphor-power/phosphor-power-supply/ |
| H A D | psu_manager.cpp | 59 // determines the brownout condition and sets the status d-bus property. in PSUManager()
589 // Only perform individual PSU analysis if power is on and a brownout has in analyze()
812 // Only issue brownout failure if chassis pgood has failed, it has not in analyzeBrownout()
819 // Indicate that the system is in a brownout condition by creating an in analyzeBrownout()
833 …"Brownout detected, not present count: {NOT_PRESENT_COUNT}, AC fault count {AC_FAILED_COUNT}, pgoo… in analyzeBrownout()
843 // If a brownout was previously logged but at least one PSU is not in analyzeBrownout()
844 // currently in AC fault, determine if the brownout condition can be in analyzeBrownout()
863 // Indicate that the system is no longer in a brownout in analyzeBrownout()
867 …"Brownout cleared, not present count: {NOT_PRESENT_COUNT}, AC fault count {AC_FAILED_COUNT}, pgood… in analyzeBrownout()
878 lg2::error("Error trying to clear brownout, error: {ERROR}", in analyzeBrownout()
|
| H A D | psu_manager.hpp | 191 * @brief Analyze the set of the power supplies for a brownout failure. Log
192 * error when necessary, clear brownout condition when window has passed.
203 /** @brief True if an error for a brownout has already been logged. */
|
| H A D | chassis.hpp | 171 /** @brief True if an error for a brownout has already been logged. */
319 * @brief Analyze the set of the power supplies for a brownout failure. Log
320 * error when necessary, clear brownout condition when window has passed.
|
| H A D | chassis.cpp | 485 // Only perform individual PSU analysis if power is on and a brownout has in analyze()
712 // Only issue brownout failure if chassis pgood has failed, it has not in analyzeBrownout()
719 // Indicate that the system is in a brownout condition by creating an in analyzeBrownout()
734 …"Brownout detected, not present count: {NOT_PRESENT_COUNT}, AC fault count {AC_FAILED_COUNT}, pgoo… in analyzeBrownout()
744 // If a brownout was previously logged but at least one PSU is not in analyzeBrownout()
745 // currently in AC fault, determine if the brownout condition can be in analyzeBrownout()
|
| H A D | chassis_manager.cpp | 37 // determines the brownout condition and sets the status d-bus property. in ChassisManager()
|
| /openbmc/phosphor-state-manager/ |
| H A D | README.md | 60 `BrownOut` state indicates there is not enough chassis power to fully power on
62 - CurrentPowerState: On, Off, BrownOut, UninterruptiblePowerSupply
|
| H A D | chassis_state_manager.cpp | 386 server::Chassis::currentPowerStatus(PowerStatus::BrownOut); in determineStatusOfPSUPower()
|
| /openbmc/u-boot/arch/x86/cpu/broadwell/ |
| H A D | pch.c | 66 * to prevent possible brownout. This will cause the GPIOs to be set in broadwell_pch_early_init()
|
| /openbmc/phosphor-logging/extensions/openpower-pels/registry/ |
| H A D | message_registry.json | 1165 "CEC hardware. Check for UPS or brownout logs."
|