Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / x86-power-control / 857c558e8f4c86ac1209de1b87de3089bcd98b83
commit857c558e8f4c86ac1209de1b87de3089bcd98b83[log] [tgz]
authorJayanth Othayoth <ojayanth@gmail.com>Thu Jun 12 11:17:51 2025 -0500
committerJayanth Othayoth <ojayanth@gmail.com>Thu Jun 12 11:17:51 2025 -0500
tree79262b793cd3d8c37178fdaba9b1f477a672cd18
parent3547113a6ff791d7f4d4fe36540ed1079051647f [diff]
Fix host monitoring for multi-host support

The existing host state monitoring logic used a static D-Bus object
path, which caused incorrect behavior in systems with multiple hosts.
The monitor was not correctly listening to the state changes of the
intended host instance, leading to missed or misrouted state updates.

This change dynamically constructs the D-Bus object path using the
host node number, ensuring that the signal match is registered for
the correct host instance. Additional logging has been added to aid
in debugging and to confirm that the correct node is being monitored.

Change-Id: I462450820a60389056bfbad9fb03db61c0548395
Signed-off-by: Jayanth Othayoth <ojayanth@gmail.com>
1 file changed
tree: 79262b793cd3d8c37178fdaba9b1f477a672cd18
  1. config/
  2. service_files/
  3. src/
  4. subprojects/
  5. .clang-format
  6. .clang-tidy
  7. .gitignore
  8. LICENSE
  9. meson.build
  10. meson.options
  11. OWNERS
  12. README.md
README.md

X86 power control

This repository contains an OpenBMC compliant implementation of power control for x86 servers. It relies on a number of features to do its job. It has several intentional design goals.

  1. The BMC should maintain the Host state machine internally, and be able to track state changes.
  2. The implementation should either give the requested power control result, or should log an error on the failure it detected.
  3. The BMC should support all the common operations, hard power on/off/cycle, soft power on/off/cycle.

This daemon has been successfully used on a variety of server platforms; it should be able to support platforms with power control GPIOs similar to those in its config file.

x86-power-control uses default json file (power-config-host0.json) for GPIO configuration. However this can be customized by producing your own power-config-host0.json file.

Signal Definitions

Definitions can be configured by two type: GPIO and DBUS

GPIO

For the platform having direct GPIO access can use the type GPIO and define like below.

{
  "Name": "PostComplete",
  "LineName": "POST_COMPLETE",
  "Type": "GPIO"
}

DBUS

For the platform not having direct GPIO access can use dbus based event monitor by using the type DBUS.

{
  "Name": "PowerButton",
  "DbusName": "xyz.openbmc_project.Chassis.Event",
  "Path": "/xyz/openbmc_project/Chassis/Event",
  "Interface": "xyz.openbmc_project.Chassis.Event",
  "Property": "PowerButton_Host1",
  "Type": "DBUS"
}

x86-power-control will monitor the property change from the given DbusName and take appropriate action. *define Property as a bool variable.

Caveats: This implementation does not currently implement the common targets that other implementations do. There were several attempts to, but all ended in timing issues and boot inconsistencies during stress operations.

Build Options

chassis-system-reset

Enable chassis system power reset to allow removing power and restoring back.

use-plt-rst

The POST Complete GPIO is usually held asserted by BIOS after POST complete and de-asserts on reset. This de-assert behavior is currently used to detect warm resets.

Some systems are adding support for a PLT_RST eSPI signal that can be used to more accurately detect warm resets. When this option is enabled, x86-power-control will use PLT_RST to detect warm resets instead of POST Complete.

See https://github.com/Intel-BMC/host-misc-comm-manager for implementation example.