Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / x86-power-control / c6d756565e5e88656ac58d518347d43f1052ed58
commitc6d756565e5e88656ac58d518347d43f1052ed58[log] [tgz]
authorJason M. Bills <jason.m.bills@linux.intel.com>Tue Sep 10 16:54:26 2024 -0700
committerJason Bills <jason.m.bills@linux.intel.com>Tue Sep 24 20:18:40 2024 +0000
tree37c1098d76512909c509a9d88a18bceaa6013b4b
parent3e031a75ae886e0781445f631b0845bd80095a89 [diff]
Update PostComplete polarity

After recent changes adding support for GPIO polarity in the config file
and using only active-high polarity for D-Bus, the PostComplete polarity
was left out of sync in a couple places.

This fixes PostComplete, so the correct polarity is used in all cases.

Tested:
Confirmed in D-Bus mode that PostComplete correctly initializes the OS
State and correctly updates the OS State on PropertiesChanged events.

Change-Id: Iae626de79b5f13292372081f14ca5ca75420a1c2
Signed-off-by: Jason M. Bills <jason.m.bills@linux.intel.com>
1 file changed
tree: 37c1098d76512909c509a9d88a18bceaa6013b4b
  1. config/
  2. service_files/
  3. src/
  4. subprojects/
  5. .clang-format
  6. .gitignore
  7. LICENSE
  8. meson.build
  9. meson.options
  10. OWNERS
  11. 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.