/openbmc/phosphor-power/phosphor-power-supply/ |
H A D | psu_manager.cpp | 25 "/xyz/openbmc_project/power/power_supplies/chassis0/psus"; 111 // Monitor PSUs anytime state is on in initialize() 154 psus.clear(); in getPSUConfiguration() 176 if (psus.empty()) in getPSUConfiguration() 236 std::find_if(psus.begin(), psus.end(), [&invpath](auto& psu) { in getPSUProperties() 239 if (invMatch != psus.end()) in getPSUProperties() 260 psus.emplace_back(std::move(psu)); in getPSUProperties() 271 if (psus.empty()) in getPSUProperties() 406 if (powerOn && !psus.empty() && !supportedConfigs.empty()) in entityManagerIfaceAdded() 578 for (auto& psu : psus) in syncHistory() [all …]
|
H A D | psu_manager.hpp | 118 for (auto& psu : psus) in onOffConfig() 133 for (auto& psu : psus) in clearFaults() 258 for (auto& psu : psus) in updateInventory() 292 * @brief Check that all PSUs have the same model name and that the system 293 * has the required number of PSUs present as specified in the Supported 298 * @return true if all the required PSUs are present, false otherwise. 303 * @brief Returns the number of PSUs that are required to be present. 305 * @return required number of PSUs, or 0 if the number could not be 319 * @brief Helper function to validate that all PSUs have the same model name 324 * @return true if all the PSUs have the same model name, false otherwise. [all …]
|
/openbmc/openbmc/meta-hpe/meta-rl300-g11/recipes-hpe/power-supplies-monitoring/files/ |
H A D | startMonitoring2.sh | 6 psus-manager 2 up 8 psus-manager 2 down
|
H A D | startMonitoring1.sh | 6 psus-manager 1 up 8 psus-manager 1 down
|
H A D | psu1down.service | 5 ExecStart=/usr/bin/psus-manager.sh 1 down
|
H A D | psu2up.service | 5 ExecStart=/usr/bin/psus-manager.sh 2 up
|
/openbmc/openbmc/meta-hpe/meta-dl385-g11/recipes-hpe/power-supplies-monitoring/files/ |
H A D | startMonitoring1.sh | 6 psus-manager 1 up 8 psus-manager 1 down
|
H A D | startMonitoring2.sh | 7 psus-manager 2 up 9 psus-manager 2 down
|
H A D | psu2down.service | 5 ExecStart=/usr/bin/psus-manager.sh 2 down
|
H A D | psu1up.service | 5 ExecStart=/usr/bin/psus-manager.sh 1 up
|
H A D | psu1down.service | 5 ExecStart=/usr/bin/psus-manager.sh 1 down
|
/openbmc/openbmc/meta-hpe/meta-dl360-g11/recipes-hpe/power-supplies-monitoring/files/ |
H A D | startMonitoring1.sh | 6 psus-manager 1 up 8 psus-manager 1 down
|
H A D | startMonitoring2.sh | 7 psus-manager 2 up 9 psus-manager 2 down
|
H A D | psu2up.service | 5 ExecStart=/usr/bin/psus-manager.sh 2 up
|
H A D | psu1down.service | 5 ExecStart=/usr/bin/psus-manager.sh 1 down
|
H A D | psu1up.service | 5 ExecStart=/usr/bin/psus-manager.sh 1 up
|
H A D | psu2down.service | 5 ExecStart=/usr/bin/psus-manager.sh 2 down
|
/openbmc/docs/designs/ |
H A D | psu-firmware-update.md | 11 There is no support in OpenBMC to update the firmware for PSUs. 46 5. There are cases that a system could use different models of PSUs, and thus 49 For some PSUs, it is risky to do PSU code update while the host is running to 59 2. If the redundant PSUs are all connected; 60 3. If the AC input and DC standby output is OK on all the PSUs; 199 - Verify the PSU code update is done on all PSUs successfully;
|
/openbmc/openbmc/meta-hpe/meta-rl300-g11/recipes-hpe/power-supplies-monitoring/ |
H A D | power-supplies-monitoring.bb | 5 SRC_URI:append = " file://psu2-monitoring.service file://psu1-monitoring.service file://psus-manage… 27 install -m 0755 ${UNPACKDIR}/psus-manager.sh ${D}/usr/bin/psus-manager.sh
|
/openbmc/openbmc/meta-hpe/meta-dl360-g11/recipes-hpe/power-supplies-monitoring/ |
H A D | power-supplies-monitoring.bb | 5 SRC_URI:append = " file://psu2-monitoring.service file://psu1-monitoring.service file://psus-manage… 27 install -m 0755 ${UNPACKDIR}/psus-manager.sh ${D}/usr/bin/psus-manager.sh
|
/openbmc/openbmc/meta-hpe/meta-dl385-g11/recipes-hpe/power-supplies-monitoring/ |
H A D | power-supplies-monitoring.bb | 5 SRC_URI:append = " file://psu2-monitoring.service file://psu1-monitoring.service file://psus-manage… 27 install -m 0755 ${UNPACKDIR}/psus-manager.sh ${D}/usr/bin/psus-manager.sh
|
/openbmc/phosphor-psu-code-mgmt/ |
H A D | README.md | 75 inventory path. If multiple PSUs are using the same version, multiple PSU 80 - Example of system with two PSUs that have different versions: 115 - Example of system with two PSUs that have the same version: 161 PSUs. If there is any PSU that has older firmware, it will be updated to the
|
/openbmc/phosphor-power/cold-redundancy/ |
H A D | cold_redundancy.hpp | 49 * @brief Indicates the count of PSUs 51 * @details Indicates how many PSUs are there on the system. 59 * different PSUs calling createPSU function for
|
/openbmc/phosphor-dbus-interfaces/yaml/xyz/openbmc_project/Control/ |
H A D | PowerSupplyRedundancy.interface.yaml | 37 Number of PSUs are currently on system. 41 The min number of PSUs in the system required to obtain redundancy
|
/openbmc/phosphor-psu-code-mgmt/src/ |
H A D | item_updater.cpp | 523 // This is a version that is different than the running PSUs in scanDirectory() 539 // running on one or more PSUs. Set Path and ExtendedVersion properties. in scanDirectory() 541 // running on a PSU. The properties are needed to update other PSUs. in scanDirectory() 565 // Get the model name of the PSUs that have been found. Note that we in findModelDirectory() 654 // image, run the activation so that all PSUs are running the same in syncToLatestImage() 660 lg2::info("Automatically update PSUs to versionId {VERSION_ID}", in syncToLatestImage()
|