Searched hist:"9 bab9e10798770033621fbcba8046e7e3e058540" (Results 1 – 4 of 4) sorted by relevance
/openbmc/phosphor-power/phosphor-power-supply/configurations/witherspoon/ |
H A D | psu_config.json | diff 9bab9e10798770033621fbcba8046e7e3e058540 Wed Feb 24 15:32:03 CST 2021 Adriana Kobylak <anoo@us.ibm.com> psu-ng: Get max PSU number from entity manager
Read the max number of PSUs supported from entity manager instead of JSON since entity manager would have the value based on system. If the entity manager interface does not exist by the time the psu manager starts, subscribe to interfaces added. The psu manager can take action once the max count property is available on D-Bus.
Tested: On Rainier 2U with debug traces: 1. Restarted phosphor-psu-monitor and verified maxPowerSupplies was 2. 2. Stopped xyz.openbmc_project.Inventory.Manager. Restarted phosphor-psu-monitor and verified maxPowerSupplies was 0. 3. Started xyz.openbmc_project.Inventory.Manager and verified the psu callback was triggered setting maxPowerSupplies to 2. 4. Stopped and started xyz.openbmc_project.Inventory.Manager and verified the psu callback was not called again.
Change-Id: Ieff796ca5c79bfddc1fc6e15e339a0b15eb422d7 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
/openbmc/phosphor-power/phosphor-power-supply/ |
H A D | README.md | diff 9bab9e10798770033621fbcba8046e7e3e058540 Wed Feb 24 15:32:03 CST 2021 Adriana Kobylak <anoo@us.ibm.com> psu-ng: Get max PSU number from entity manager
Read the max number of PSUs supported from entity manager instead of JSON since entity manager would have the value based on system. If the entity manager interface does not exist by the time the psu manager starts, subscribe to interfaces added. The psu manager can take action once the max count property is available on D-Bus.
Tested: On Rainier 2U with debug traces: 1. Restarted phosphor-psu-monitor and verified maxPowerSupplies was 2. 2. Stopped xyz.openbmc_project.Inventory.Manager. Restarted phosphor-psu-monitor and verified maxPowerSupplies was 0. 3. Started xyz.openbmc_project.Inventory.Manager and verified the psu callback was triggered setting maxPowerSupplies to 2. 4. Stopped and started xyz.openbmc_project.Inventory.Manager and verified the psu callback was not called again.
Change-Id: Ieff796ca5c79bfddc1fc6e15e339a0b15eb422d7 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
H A D | psu_manager.hpp | diff 9bab9e10798770033621fbcba8046e7e3e058540 Wed Feb 24 15:32:03 CST 2021 Adriana Kobylak <anoo@us.ibm.com> psu-ng: Get max PSU number from entity manager
Read the max number of PSUs supported from entity manager instead of JSON since entity manager would have the value based on system. If the entity manager interface does not exist by the time the psu manager starts, subscribe to interfaces added. The psu manager can take action once the max count property is available on D-Bus.
Tested: On Rainier 2U with debug traces: 1. Restarted phosphor-psu-monitor and verified maxPowerSupplies was 2. 2. Stopped xyz.openbmc_project.Inventory.Manager. Restarted phosphor-psu-monitor and verified maxPowerSupplies was 0. 3. Started xyz.openbmc_project.Inventory.Manager and verified the psu callback was triggered setting maxPowerSupplies to 2. 4. Stopped and started xyz.openbmc_project.Inventory.Manager and verified the psu callback was not called again.
Change-Id: Ieff796ca5c79bfddc1fc6e15e339a0b15eb422d7 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|
H A D | psu_manager.cpp | diff 9bab9e10798770033621fbcba8046e7e3e058540 Wed Feb 24 15:32:03 CST 2021 Adriana Kobylak <anoo@us.ibm.com> psu-ng: Get max PSU number from entity manager
Read the max number of PSUs supported from entity manager instead of JSON since entity manager would have the value based on system. If the entity manager interface does not exist by the time the psu manager starts, subscribe to interfaces added. The psu manager can take action once the max count property is available on D-Bus.
Tested: On Rainier 2U with debug traces: 1. Restarted phosphor-psu-monitor and verified maxPowerSupplies was 2. 2. Stopped xyz.openbmc_project.Inventory.Manager. Restarted phosphor-psu-monitor and verified maxPowerSupplies was 0. 3. Started xyz.openbmc_project.Inventory.Manager and verified the psu callback was triggered setting maxPowerSupplies to 2. 4. Stopped and started xyz.openbmc_project.Inventory.Manager and verified the psu callback was not called again.
Change-Id: Ieff796ca5c79bfddc1fc6e15e339a0b15eb422d7 Signed-off-by: Adriana Kobylak <anoo@us.ibm.com>
|