Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / x86-power-control / 3547113a6ff791d7f4d4fe36540ed1079051647f
commit3547113a6ff791d7f4d4fe36540ed1079051647f[log] [tgz]
authorJason M. Bills <jason.m.bills@linux.intel.com>Tue May 06 12:26:10 2025 -0700
committerJason Bills <jason.m.bills@linux.intel.com>Mon Jun 02 19:18:59 2025 +0000
treeb77464ca17ed0a9677c839f355c06da6f5a100aa
parent835528e884ef7c0fb7704ea00a67527cda491abb [diff]
Change name to just power OK

A system power OK signal may not necessarily be tied to the power
supplies, so rename everything to remove reference to the power supply
and keep just "power OK".

Tested:
Confirmed that ipmitool power on, off, and cycle all work as expected
and there is no mention of power supply in the logs.

Change-Id: I62370f2666602525c6b4564ccff8d18b703744f4
Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>
2 files changed
tree: b77464ca17ed0a9677c839f355c06da6f5a100aa
  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.