Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / openpower-occ-control / f788150656a182cb75c0b72af9f84530531773ef
commitf788150656a182cb75c0b72af9f84530531773ef[log] [tgz]
authorChris Cain <cjcain@us.ibm.com>Wed Apr 16 14:48:30 2025 -0500
committerChris Cain <cjcain@us.ibm.com>Wed Apr 16 15:25:39 2025 -0500
treeeadc5744ee73b46a8a3a13b4dbe2738776113b98
parentc488bac124fbbcb0dbe83e48922c3087a5aaa7bd [diff]
Prevent multiple PM complex resets from being queued

- Clear any prior reset request when notified that OCCs are active
- If OCC state is safe/not valid, prevent immediate request for reset.
Start a safe state delay timer and if it does not recover then request a
reset.
- If unable to read the OCC state after a retry, then request a reset.
(no change to this behavior)

Problem: A system where the OCC went to safe state, and BMC requested
a reset, but HTMT had already requested a reset, so the PM complex got
reset multiple times when not necessary.

Tested on Rainier/Fuji

Change-Id: Id40b00e6d3708358478271bb6d5acef804715d4a
Signed-off-by: Chris Cain <cjcain@us.ibm.com>
3 files changed
tree: eadc5744ee73b46a8a3a13b4dbe2738776113b98
  1. example/
  2. service_files/
  3. subprojects/
  4. test/
  5. .clang-format
  6. .gitignore
  7. app.cpp
  8. file.hpp
  9. i2c_occ.cpp
  10. i2c_occ.hpp
  11. LICENSE
  12. meson.build
  13. meson.options
  14. occ-active.sh
  15. occ_command.cpp
  16. occ_command.hpp
  17. occ_dbus.cpp
  18. occ_dbus.hpp
  19. occ_device.cpp
  20. occ_device.hpp
  21. occ_errors.cpp
  22. occ_errors.hpp
  23. occ_events.hpp
  24. occ_ffdc.cpp
  25. occ_ffdc.hpp
  26. occ_manager.cpp
  27. occ_manager.hpp
  28. occ_pass_through.cpp
  29. occ_pass_through.hpp
  30. occ_presence.cpp
  31. occ_presence.hpp
  32. occ_sensor.mako.hpp
  33. occ_status.cpp
  34. occ_status.hpp
  35. OWNERS
  36. pldm.cpp
  37. pldm.hpp
  38. powercap.cpp
  39. powercap.hpp
  40. powermode.cpp
  41. powermode.hpp
  42. README.md
  43. sensor_gen.py
  44. utils.cpp
  45. utils.hpp
README.md

OpenPOWER OCC Control Service

This service will handle communications to the On-Chip Controller (OCC) on Power processors. The OCC provides processor and memory temperatures, power readings, power cap support, system power mode support, and idle power saver support. OCC Control will be interfacing with the OCC to collect the temperatures and power readings, updating the system power mode, setting power caps, and idle power save parameters.

The service is started automatically when the BMC is started.

Build Project

This project can be built with meson. The typical meson workflow is: meson builddir && ninja -C builddir.

Server

The server will start automatically after BMC is powered on.

Server status: systemctl status org.open_power.OCC.Control.service

To restart the service: systemctl restart org.open_power.OCC.Control.service

Configuration

Service files are located in service_files subdirectory.

References

Power10

IBM EnergyScale for Power10 Processor-Based Systems whitepaper: https://www.ibm.com/downloads/cas/E7RL9N4E

OCC Firmware Interface Spec for Power10: https://github.com/open-power/docs/blob/P10/occ/OCC_P10_FW_Interfaces_v1_17.pdf

OCC Firmware: https://github.com/open-power/occ/tree/master-p10

Power9

IBM EnergyScale for POWER9 Processor-Based Systems: https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?htmlfid=49019149USEN&

OCC Firmware Interface Spec for POWER9: https://github.com/open-power/docs/blob/P9/occ/OCC_P9_FW_Interfaces.pdf