Gitiles
Code Review Sign In
gerrit.openbmc.org / openbmc / pldm / 1507b1d8fb0401e14e9e654768691ba28e4f5536
commit1507b1d8fb0401e14e9e654768691ba28e4f5536[log] [tgz]
authorAditya Kurdunkar <akurdunkar@nvidia.com>Thu Aug 21 13:26:13 2025 +0530
committerAditya Kurdunkar <akurdunkar@nvidia.com>Wed Sep 03 08:08:52 2025 +0530
tree5ebbeccc494175b97e03f91514ae608fcf331fc7
parentc00d5bf65f7ca3df557be8e2f704e5a0ef62321f [diff]
platform-mc: Add support for sensor unit 'Hertz'

Patch [1] adds the frequency sensor namespace.

This patch makes sure that a numeric sensor is added to frequency
namespace when the PLDM sensor unit is 'Hertz' (from DSP0248).

This patch has been tested for Nvidia Grace CPU, which exposes it's
operating clock frequency as a sensor

'''
% busctl tree xyz.openbmc_project.PLDM
.....
    | |- /xyz/openbmc_project/sensors/frequency
    | | |- /xyz/openbmc_project/sensors/frequency/ProcessorModule_0_CPU_0_CpuFreq_0
.....
'''

[1]: https://gerrit.openbmc.org/c/openbmc/phosphor-dbus-interfaces/+/83009

Change-Id: I47a3649fd9c46b19c56d06751b4786873cca71c4
Signed-off-by: Aditya Kurdunkar <akurdunkar@nvidia.com>
1 file changed
tree: 5ebbeccc494175b97e03f91514ae608fcf331fc7
  1. common/
  2. configurations/
  3. docs/
  4. fw-update/
  5. host-bmc/
  6. libpldmresponder/
  7. oem/
  8. platform-mc/
  9. pldmd/
  10. pldmtool/
  11. requester/
  12. softoff/
  13. subprojects/
  14. test/
  15. tools/
  16. utilities/
  17. .clang-format
  18. .clang-tidy
  19. .eslintignore
  20. .gitignore
  21. .linter-ignore
  22. LICENSE
  23. meson.build
  24. meson.options
  25. OWNERS
  26. README.md
README.md

PLDM - Platform Level Data Model

License

Overview

PLDM (Platform Level Data Model) is a key component of the OpenBMC project, providing a standardized data model and message formats for various platform management functionalities. It defines a method to manage, monitor, and control the firmware and hardware of a system.

The OpenBMC PLDM project aims to implement the specifications defined by the Distributed Management Task Force (DMTF), allowing for interoperable management interfaces across different hardware and firmware components.

Features

  • Standardized Messaging: Adheres to the DMTF's PLDM specifications, enabling consistent and interoperable communication between different components.
  • Modularity: Supports multiple PLDM types, including base, FRU,Firmware update, Platform Monitoring and Control, and BIOS Control and Configuration.
  • Extensibility: Easily extendable to support new PLDM types and custom OEM commands.
  • Integration: Seamlessly integrates with other OpenBMC components for comprehensive system management.

Getting Started

Prerequisites

To build and run PLDM, you need the following dependencies:

  • Meson
  • Ninja

Alternatively, source an OpenBMC ARM/x86 SDK.

Building

To build the PLDM project, follow these steps:

meson setup build && meson compile -C build

To run unit tests

The simplest way of running the tests is as described by the meson man page:

meson test -C build

Alternatively, tests can be run in the OpenBMC CI docker container using these steps.

To enable pldm verbosity

pldm daemon accepts a command line argument --verbose or --v or -v to enable the daemon to run in verbose mode. It can be done via adding this option to the environment file that pldm service consumes.

echo 'PLDMD_ARGS="--verbose"' > /etc/default/pldmd
systemctl restart pldmd

To disable pldm verbosity

rm /etc/default/pldmd
systemctl restart pldmd

Documentation

For complete documentation on the functionality and usage of this repository, please refer to the docs folder.